KB5000736 Featured update Windows 10 version 21H1 enablement package Win Update

EdTittel said:

Not showing up in WU for all of my up-to-date 20H2 PCs, but on those where it is, the install is blazing fast. Under 2 minutes on the Lenovo X1 Extreme (Coffee Lake/8th generation) and ditto on the Dell Optiplex 7080 Micro (Comet Lake/10th generation) PC. Pondering the manual install on the other machines using the self-installing (.MSU) update file. Love to hear from others who've taken that route in this thread, if possible. Anybody?
Thanks,
--Ed--

Never showed up in WU for my rig on up-to-date 20H2. Took 1 second to download the 64-bit MSU from the link in the first post and, I'm not kidding, 1-2 seconds to install. Restart was blazing fast and everything working okay.

Restarted with Windows update blank but services running. Also it showed "install and restart" in the shutdown selection listing. Waited about 10 minutes and its all back to normal.

Just installed from the msu file and NO issue with Mr. Please Wait!

Six days now!

EdTittel said:

Not showing up in WU for all of my up-to-date 20H2 PCs, but on those where it is, the install is Pondering the manual install on the other machines using the self-installing (.MSU) update file. Love to hear from others who've taken that route in this thread, if possible. Anybody?
--Ed--

update was available in WU for an older Laptop (Lenovo T450S) but not in main desktop. Laptop had followup sfc /scannow applied successfully. Desktop has not had sfc /apply successfully in the past two updates. Used this .msu to install 21h1 and it did not pass the sfc /scannow. There has been no issues with operation in these files not able to be corrected. The 21h1 install is displaying in the history list of WU. I was hoping the sfc scan would be error free but not so. The log errors reference hash mismatch so I'm not sure an inplace repair install will remedy anything.

Apparently I am the only person in the world that this update caused a bug in the storage.

I can't find a similar case anywhere. I have uninstalled the update and everything is back to normal.


21H1


20H2

So does this update modify any system files or is it more just a registry switch for people who are currently up to date.

An easy way to tell if system files got changed is to go into your "C:\Windows\System32" folder and sort files by "Date modified" and see if any files match the time when you ran the update and it did the whole download/patching/install/reboot thing, they should all be at the top since you sorted them that way. you'll know things got changed, so if.

Checking "Date modified" times is a great way to see what these patches actually do because their patch notes are so garbage, just to please reddit users I guess. But for people know do know what these files do, seeing that "C:\Windows\explorer.exe" was modified, you'll have an idea that something was changed with that, for good or bad.

Had dreadful problems updating. Crashed, stuck at 20%, stuck at 73% etc.

Tried all tricks on this forum eg stopping update, deleting softwaredistribution folder, rebooting etc.

After about 8 attempts, it finally worked but took over 20 mins. Last time I used an enablement update, it took about 6 minutes.