Win Update KB5017321 Cumulative Update for Windows 11 Build 22621.521 (22H2) - Sept. 20

FrancoDT · Sep 23, 2022

johnlgalt said:
Your screenshot shows things that I don't normally see in the extended context menu:

System Restore

Control Panel

Create Restore Point

Restart Explorer

Safe Mode

Are you sure you've not either modified the context menu, or else used an app (like WinAero Tweaker, etc.) to modify something?

John I have added those items to the context menu but that was after I did the upgrade. The menus were already distorted before adding any of those items.

johnlgalt · Sep 23, 2022

FrancoDT said:
John I have added those items to the context menu but that was after I did the upgrade. The menus were already distorted before adding any of those items.

Cool. Just making sure. That menu actually looks like the WDM is failing for some reason. Out of curiosity, have you tried reinstalling (and even cleanly installing) your GPU drivers?

FrancoDT · Sep 23, 2022

johnlgalt said:
Cool. Just making sure. That menu actually looks like the WDM is failing for some reason. Out of curiosity, have you tried reinstalling (and even cleanly installing) your GPU drivers?

The update installed an older intel GPU driver which the intel driver and support assistant promptly had me update again to the latest version. That's the only GPU on that particular little laptop. The update didn't change things however. I guess it's kinda of a moot point now as I already reverted back to the 22000.1042 build so can't troubleshoot it anymore. I figured I'd wait till WU offers the build and try it again.

fg2001gf11F · Sep 23, 2022

sgage said:
Yikes! That sounds worrisome. I have very rarely used resetbase, and when I do, it's always been after running several dism commands in sequence, so I don't seem to have ever been 'bitten'. I of course have a MR image to fall back on if necessary.

But I sure hope I haven't caused any hassles for folks with this recommendation - I only tried it because I hadn't seen the other mitigations yet, and it was more or less out of desperation. I deeply apologize if my suggestion causes anyone any grief...

I tried your method to get over error 0x800f0806 today and it worked.
I used the 2 commands in sequence one after the other after I read the warnings.

DISM /ONLINE /CLEANUP-IMAGE /STARTCOMPONENTCLEANUP

DISM /ONLINE /CLEANUP-IMAGE /STARTCOMPONENTCLEANUP /RESETBASE

You may want to take a look at this, to see how MS changed things again from Sept 21st to Sept 23rd.
Upgrade that worked fine on Sept 21st was no longer working on Sept 23rd. If you want to see weird behavior, check the link below:

Redirecting

Bree · Sep 24, 2022

Things have changed today, looks like MS have changed something at their end. The KB5017321 CU for 22621.521 that would consistently fail with an 0x800f0806 download error now installs successfully.

fg2001gf11F · Sep 24, 2022

Bree said:
Things have changed today, looks like MS have changed something at their end. The KB5017321 CU for 22621.521 that would consistently fail with an 0x800f0806 download error now installs successfully.

Confirmed on this box.

Bree · Sep 24, 2022

fg2001gf11F said:
Confirmed on this box.

Thank you for that confirmation. The fix from MS appears to involve a reinstall of KB5016632 (22621.382) which doesn't need a restart, after which KB501327 can be successfully downloaded and installed.

fg2001gf11F · Sep 24, 2022

Bree said:
Thank you for that confirmation. The fix from MS appears to involve a reinstall of KB5016632 (22621.382) which doesn't need a restart, after which KB501327 can be successfully downloaded and installed.

Yes, looks like they are reinstalling KB5016632 which is 22621.382, even if it was installed previously with the upgrade done with ISO.

Microsoft Windows [Version 10.0.22621.382]
(c) Microsoft Corporation. All rights reserved.

cereberus · Sep 24, 2022

I had to do a repair upgrade with RTM 22621.521 as I found Windows Security was broken, and it behaved differently - instead of installing 22621.382 as I expected, and then followed up with a WU update to 22621.521 as normal, it installed as 22621.521 in one go. I had selected option to check for updates but that never seems to check for latest CU. This time, it must have included the cumulative update and installed direct as 22621.251.

With all the hassle not being able to leave RP Channel despite being unenrolled, I am now going to keep Host OS as official release (i.e, Non Insider), and will only install optional Cumulative Preview Updates as I see fit.

fg2001gf11F · Sep 24, 2022

cereberus said:
I had to do a repair upgrade with RTM 22621.521 as I found Windows Security was broken, and it behaved differently - instead of installing 22621.382 as I expected, and then followed up with a WU update to 22621.521 as normal, it installed as 22621.521 in one go. I had selected option to check for updates but that never seems to check for latest CU. This time, it must have included the cumulative update and installed direct as 22621.251.

With all the hassle not being able to leave RP Channel despite being unenrolled, I am now going to keep Host OS as official release (i.e, Non Insider), and will only install optional Cumulative Preview Updates as I see fit.

Yes, that was already the case on Sept 21st. I saw that behavior on 3 machines.

Bree · Sep 24, 2022

cereberus said:
I had selected option to check for updates but that never seems to check for latest CU. This time, it must have included the cumulative update and installed direct as 22621.251.

fg2001gf11F said:
Yes, that was already the case on Sept 21st. I saw that behavior on 3 machines.

I had one suported machine that was offered 22H2 in Windows Update. I upgraded through Windows Update and that too went straight to 22621.521.

fg2001gf11F · Sep 24, 2022

Bree said:
I had one supported machine that was offered 22H2 in Windows Update. I upgraded through Windows Update and that too went straight to 22621.521.

Yes, that was the same case on my first machine (non-insider) on Sep 20, W.U. offered 22H2 and the upgrade had no issues at all, went directly to 22621.521 with no problems.
The bugs started when I tried the upgrades with MS ISO 22621.382 on other machines the same day.
Then everything worked fine on Sept 21st, even using the ISO 22621.382 it was going directly to 22621.521 downloading and installing KB5017321 during the upgrade process.

On the ones that were getting the error 0x800f0806 on Sept 20, I just worked around the bug either by downloading the update from the MS catalog or using the Dism commands to clean up the mess.

Today, to test the same situation I just did the upgrade with ISO offline so that it went up to 22621.382 only, then W.U. downloaded and installed KB5017321 as a second step, this way I could see that they actually fixed the 0x800f0806 bug they had originally.
Problem solved.

fg2001gf11F · Sep 24, 2022

cereberus said:
With all the hassle not being able to leave RP Channel despite being unenrolled, I am now going to keep Host OS as official release (i.e, Non Insider), and will only install optional Cumulative Preview Updates as I see fit.

About leaving R.P. channel, maybe you can try this.
Looks like I managed to do it even if I'm already at 22621.607.
I was queued for unenrollment, but even after multiple restarts it would not leave the insider channel.
Perhaps because I'm already at higher build number than current public build? Not sure if that makes any difference.

So, I just deleted WindowsSelfHost and rebooted.
Windows recreated a new key for non-insider.
I'll enroll in R.P. again on this system, since I already have other non-insider systems anyway. I was just curious to see if this worked.

HuntyFtw · Sep 25, 2022

I used Windows 11 Installation Assistant and it directly installed 22621.521.

cereberus · Sep 25, 2022

fg2001gf11F said:
About leaving R.P. channel, maybe you can try this.
Looks like I managed to do it even if I'm already at 22621.607.
I was queued for unenrollment, but even after multiple restarts it would not leave the insider channel.
Perhaps because I'm already at higher build number than current public build? Not sure if that makes any difference.
So, I just deleted WindowsSelfHost and rebooted.
Windows recreated a new key for non-insider.
I'll enroll in R.P. again on this system, since I already have other non-insider systems anyway. I was just curious to see if this worked.

View attachment 40243

View attachment 40240

View attachment 40238

I sorted my issues as I had the previous RTM build backed up a few weeks ago, so apart from some app updates needed, it was pretty much up to date.

I still have my RP Hotel California version (I cloned Host OS to a vhd), so I will try this - would have save me some hassle if it works.

Edit: this sort of works but is not a complete solution.

As per your screenshots, I have kind of left Insider, but one setting still remains i.e pause frequency option. It does not have a pull down menu to select more than one week.

I bet there is a registry key somewhere that sorts this..........

cereberus · Sep 25, 2022

cereberus said:
I sorted my issues as I had the previous RTM build backed up a few weeks ago, so apart from some app updates needed, it was pretty much up to date.

I still have my RP Hotel California version (I cloned Host OS to a vhd), so I will try this - would have save me some hassle if it works.

Edit: this sort of works but is not a complete solution.

As per your screenshots, I have kind of left Insider, but one setting still remains i.e pause frequency option. It does not have a pull down menu to select more than one week.

I bet there is a registry key somewhere that sorts this..........

View attachment 40292

@fg2001gf11F

Sorted it - need to delete this Dword and now pull down menu is back for up to 5 weeks.

@Brink - may be a basis for a mini tutorial how to unenroll from Insider (#73 and #76 regedit changes). Obviously this needs to be tested - if we get next normal update to 22621.521, I would say we have cracked it.

Brink · Sep 25, 2022

cereberus said:
@Brink - may be a basis for a mini tutorial how to unenroll from Insider (#73 and #76 regedit changes). Obviously this needs to be tested - if we get next normal update to 22621.521, I would say we have cracked it.

Hey mate,

I did some testing on the FlightSettingsMaxPauseDays DWORD value.

It is indeed only available in Insider builds to limit the maximum days to pause Windows Updates to 7 days by default.

You can change the FlightSettingsMaxPauseDays DWORD value to how many days in increments of 7 days you want instead.

Deleting FlightSettingsMaxPauseDays DWORD value will restore the default 35 days max like in public releases.

The bad news is that anytime you "Check for updates" or resume updates after being paused, the FlightSettingsMaxPauseDays DWORD value will automatically get reset back to the default 7 days for Insider builds.

I'm still going to create a tutorial for this since it can still be useful. Just want to do some more testing first.

EDIT:

Change Maximum Days to Pause Windows Update in Windows 11 Tutorial

This tutorial will show you how to change the maximum days you can pause Windows Update for in Windows 11. Windows Update keeps Windows 11 updated by automatically downloading and installing the latest updates, drivers, and hotfixes released by Microsoft. If you have a Windows Insider build of...

www.elevenforum.com

fg2001gf11F · Sep 25, 2022

cereberus said:
@fg2001gf11F

Sorted it - need to delete this Dword and now pull down menu is back for up to 5 weeks.

View attachment 40294

@Brink - may be a basis for a mini tutorial how to unenroll from Insider (#73 and #76 regedit changes). Obviously this needs to be tested - if we get next normal update to 22621.521, I would say we have cracked it.

One more thing I forgot to mention.
You may want to use BCDEDIT to turn off FlightSigning. It probably does not hurt if it stays on, but just to be safe.

flightsigning Yes

C:\Windows\System32>bcdedit /set {current} flightsigning off

flightsigning No

fg2001gf11F · Sep 25, 2022

Brink said:
Hey mate,

I did some testing on the FlightSettingsMaxPauseDays DWORD value.

It is indeed only available in Insider builds to limit the maximum days to pause Windows Updates to 7 days by default.

You can change the FlightSettingsMaxPauseDays DWORD value to how many days in increments of 7 days you want instead.

Deleting FlightSettingsMaxPauseDays DWORD value will restore the default 35 days max like in public releases.

The bad news is that anytime you "Check for updates" or resume updates after being paused, the FlightSettingsMaxPauseDays DWORD value will automatically get reset back to the default 7 days for Insider builds.

I'm still going to create a tutorial for this since it can still be useful. Just want to do some more testing first.

EDIT:

Change Maximum Days to Pause Windows Update in Windows 11 Tutorial

This tutorial will show you how to change the maximum days you can pause Windows Update for in Windows 11. Windows Update keeps Windows 11 updated by automatically downloading and installing the latest updates, drivers, and hotfixes released by Microsoft. If you have a Windows Insider build of...

www.elevenforum.com

Hi Brink,
I just tried checking for update and the value remained as the default.
In this case, I'm no longer on the R.P. insider channel because I previously deleted WindowsSelfHost

cereberus · Sep 25, 2022

fg2001gf11F said:
One more thing I forgot to mention.
You may want to use BCDEDIT to turn off FlightSigning. It probably does not hurt if it stays on, but just to be safe.

flightsigning Yes

C:\Windows\System32>bcdedit /set {current} flightsigning off

flightsigning No

Yeah - I think mine is off how anyway.