Win 10 cum update - where?

[PerranOak]

I haven't had an automatic cumulative update to Windows 10 this year.
I thought I saw the Feb one ready to install but it didn't and it didn't show as failed.
Check for updates gives nothing.

About system gives:
Edition   Windows 10 Pro
Version   20H2
Installed on   ‎13/‎07/‎2020
OS build   19042.804
Experience   Windows Feature Experience Pack 120.2212.551.0

Any ideas please, I'm lost.

Cheers.

[Halcyon]

Check your event viewer and find out why an update failed to install.

[Ian.M]

https://wccftech.com/microsoft-pauses-optional-windows-10-updates-due-to-coronavirus/

[PerranOak]

Halcyon: there is so much in there I tell what to look for.

Ian.M: is that still the case this year?

[Ian.M]

Many countries are in the middle of the Coronavirus second wave, at case levels comparable to spring 2020 so the situation that caused Microsoft to make that decision hasn't changed much.

This Win10 x64 20H2 box hasn't had any feature updates since I updated to 20H2 mid-November which would lead me to suspect the feature update freeze is still in place.  I've had two cumulative updates for Win10 20H2 this year in the 'Quality Updates' section, KB4598242 and KB4601319.

[PerranOak]

Ah yes, it’s those two that I’m not seeing.

[gmb42]

The attached PowerShell script (please rename to WindowsUpdates.ps1 first) returns the results from the Windows Update User Agent (WUA):

Code: [Select]

>. path\to\WindowsUpdates.ps1
>$h = Get-WUAHistory
>$h - Out-GridView # or whatever else you want to do with the history
Some of the history results are a bit odd (I see "In Progress" for a few of the cumulative updates but they have installed).

There is also Get-WindowsUpdateLog which produces voluminous output.

[PerranOak]

Hi,

I put the ps1 file into C:|temp and ran the first line. It errored (also the "path\to" one errored similarly):

PS C:\temp> $h = Get-WUAHistory
Get-WUAHistory : The term 'Get-WUAHistory' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:6
+ $h = Get-WUAHistory
+      ~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-WUAHistory:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

What did I do wrong?

Cheers.

[gmb42]

Hi,

I put the ps1 file into C:|temp and ran the first line. It errored (also the "path\to" one errored similarly):

Replace "path\to\" with the actual path to the file, so in your case:

Code: [Select]

. c:\temp\WindowsUpdates.ps1
Note the leading ".", this tells PowerShell to "source" the specified file, i.e. read it in and add any defined functions (temporarily) to the current scope in the shell instance you run it in.

As you didn't "source" the file, the subsequent command you attempted to run (Get-WUAHistory) wasn't found.

[PerranOak]

Ah right, thanks. I thought "path\to! was a function that changed the directory to the right one(!) 

So, KB4601319 (Feb update) is showing as installed even though it doesn't show at all in "Settings / View Update History". However, KB4598242 (the Jan one) doesn't show up at all anywhere.

Does this matter if the Feb one is there?

[gmb42]

The cumulative updates are ... cumulative, i.e. you only "need" the latest one.  A machine that has been around a while will have a history of installing the updates as they are released, but skipping one isn't an issue.

See https://docs.microsoft.com/en-us/windows/deployment/update/servicing-stack-updates#:~:text=Both%20Windows%2010%20and%20Windows,fixes%20from%20all%20previous%20updates.

[PerranOak]

Just wanted to be sure, thank you.