Can’t see optional updates on Server 2022

Topic

New Reply

I’m working on a Server 2022 21H2 virtual machine. I know there is an optional update waiting from running a PowerShell script. For example, this one-liner

(New-Object -ComObject Microsoft.Update.Session).CreateupdateSearcher().Search("IsHidden=0 and IsInstalled=0").Updates | Select-Object Title

shows that this update is pending:

SQL Server 2019 RTM Cumulative Update (CU) 25 KB5033688

A little more digging on KB5033688 shows that its BrowseOnly flag is True, i.e. optional.

However when I go to the Windows Update UI, I do not see the “View optional updates” hyperlink, so I can’t find and install that update.

The machine is managed by Windows Update for Business. There is a new policy Enable optional updates but it requires Windows 11 22H2, so doesn’t help here. I did try temporarily renaming the WindowsUpdate registry key, which should disable WUFB, but I still don’t see the optional update.

I don’t think it’s relevant, but the machine still has the BitLocker fix from January pending (KB5034439). It keeps trying and failing to install that.

I know I could download and install this manually, but I’d like to get the optional updates working.

Is there some trick to make the optional update link appear on Server 2022?

Reply | Quote

Replies

You might check your WUFB configurations…

https://learn.microsoft.com/en-us/windows/deployment/update/waas-configure-wufb

Reply | Quote

Thanks. Yes, that’s where I found the Enable optional updates GPO, but as mentioned, that only applies to Windows 11, version 22H2.

I’m trying to figure out how to see/apply optional updates on Server 2022 21H2.

Reply | Quote

mcbsys wrote:

that only applies to Windows 11, version 22H2.

Actually, I have that option in Windows 10 22H2…

I’d run the Windows Update Troubleshooter.

Failing that, I’d image the drive, and reset and re-register the Windows Update components.

 

Reply | Quote

Tried posting  a long reply but I wasn’t logged in so it’s gone.

Update Troubleshooter is a good idea but didn’t help. Other updates work fine so I don’t think WU is broken.

If I have time, I may dig into the logs.

Reply | Quote

Are you behind WSUS or have any WUFB settings?

There is a group policy that is similar to the “don’t look for MU instead look at WSUS” that makes the system not look to MU for optional updates.  I can’t remember what it is off the top of my head but if you dig into the local group policy settings on the server, see if one rings a bell?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Susan Bradley wrote:

There is a group policy that is similar to the “don’t look for MU instead look at WSUS” that makes the system not look to MU for optional updates.

It’s “Specify source service for specific classes of Windows Updates” in Computer Configuration > Administrative Templates > Windows Components > Windows Update.

When enabled, the dropdown selections for “Other Updates”  is WSUS or WU.

 

Reply | Quote

This network has never had WSUS. That setting is not enabled.

I used Get-WindowsUpdateLog and tried deciphering the log. I do see KB5033688 in the log, identified by its ID 18dcf1b0-cee8-47b0-84cd-ef567064ecf1. I can’t figure out why it’s not getting installed.

I used ResetWuEng 10.5.4.1 to reset the Windows Update components. (Oops, I see now that that there are later versions at https://wureset.com/.) That didn’t help.

Maybe WU just won’t show optional updates until the “required” updates are done? I guess I can work on my partitions so the blasted BitLocker patch KB5034439 will install.

Reply | Quote

Well, I got KB5034439 installed but still can’t see the optional update.

Reply | Quote

Still puzzling over this. I’ve created a blog post with screen shots to document the issue:

https://www.mcbsys.com/blog/2024/04/server-2022-doesnt-offer-optional-updates/

Reply | Quote