Critical update for Windows 7 / Server 2008 R2 users

Microsoft has announced that all Windows 7 / Server 2008 R2 Updates will require an update in order to continue to get Windows Updates [the same will go if WSUS 3.2/3.0 SP2 is used]. This is for SHA-2 code signing.

After August 13, 2019, Windows 7 / Server 2008 R2 Updates will not receive any updates.

As the update was just release this past Tuesday, you would of figured that the update would be included in this week’s updates, but so far I haven’t seen any.

For further information click here. Click here for the deadlines.


How to read the Windows Update log in Windows 10

With Windows 10 came a change in the WindowsUpdate.log file. It is still located in C:\Windows, however when you open the file C:\Windows\WindowsUpdate.log you won’t see the text you are use to but a message saying that the log is basically unreadable.

In order to read WindowsUpdate.log in Windows 10, you will need to use Windows PowerShell cmdlet to re-create the WindowsUpdate.log the way we normally view it

In Windows 10, open PowerShell with administrative rights (can use PowerShell ISE if you wish).

Run the command:

ps c:\windows\system32> Get-WindowsUpdateLog

This will take a moment or two to finish. Once done, you will see on the desktop the resulting new WindowsUpdate.log file.

Note that the log on the desktop will be static and will contain the information that was in the original log at the time you converted it. So you would need to run the command above if you need to get newer information.

For more information on using the Get-WindowsUpdate.log cmdlet, please go here.

Different ways of updating Windows 10

During the first day of Microsoft Ignite, the company’s “festival” for IT professionals, Microsoft executives introduced the concept of Windows Update for Business. This is a new addition to Microsoft’s family of updating and servicing mechanisms that will be included with Windows 10.

Consumers who use Windows 10 will regularly receive all the new features, security updates and the various fixes to the operating system for free for the supported lifetime of their devices. [Microsoft still hasn’t stated what this “lifetime of their devices” period will be defined as.] Consumers users won’t have a choice as to which updates they get or don’t as they will get them all using Windows Update. This group of Windows 10 customers will be on the Current Branch.

Windows 10 Enterprise customers will have the option to receive security updates only with no new features as part of the Windows 10 Long Term Servicing branch. Enterprises [or large companies if you will] will be able to control the pace at which their Windows 10 users get these security updates using existing updating mechanisms like Windows Server Update Services [WSUS], System Center Configuration Manager [SCCM], and others.

But there’s is a new class of Windows 10 customers: These are users at work who aren’t running mission-critical devices and applications. These users will be able to get new features, security updates and the various other fixes to Windows 10 Pro and Windows 10 Enterprise devices for free, but at a more measured pace using the new Windows Update for Business service.

Windows Update for Business will give IT professionals more control over how and when these updates are roll out to their users and they can decide which machines get updates first and which get them at one point later. Peer-to-peer delivery will be used to deliver patches to sites with limited bandwidth [not too common now]. The standard corporate tools such as WSUS or SCCM can be used to deliver the updates.

Microsoft executives didn’t explain as yet how long they’ll be providing new features, security updates and fixes for Windows 10.