KB4571756 Cumulative Update Windows 10 v2004 build 19041.508 - Sept. 8 Win Update

Kbird said:

On a 2nd older system here , 508 had trouble restarting, but has eventually got there , but is running slow as molasses on a winter's morning....... and much to my surprise the 2nd User Profile is gone , no trace whatsoever , it used to stop at boot until one of them signed in with their pin , now there is only one User, which I suspect is the one the Update started under.

KB.

I now think this was the cause of a reboot loop last Tues, which ended up with me Clean Installing 2004 on my Main rig, which is still acting a bit weird , even after I removed what Updates it would let me and then 24 hours later let then reinstall again.

On the other PC in the House which updated last Tues as well all was well, till I noticed it acting weird on Sat. ,so checked the Version number and somewhere along the line it had rolled itself back to 1909.1016 (?) , so I checked UPdates and it updated to 2004.508 again.....

All very weird and wish i stayed on 1909 now with 3 computers all showing issues , only one not showing issues is my brand new Laptop I got for work 2 weeks ago .....it has it own issues

KB.

This problem does no affect AMD systems.

Not Myself said:

Yesterday's strange "update", quotes intentional: Having not updated Version 1909 for at least a few weeks, I decided to bypass the delay setting and see if there were any files to update. There were three, NET Framework, Malicious Software, and a KB Feature Update. I did not expect that latter file, but as Windows Update presented it, the three proceeded to download and install. When that was done, I restarted the computer, which I found shortly afterwards was already at the log-on screen. I said to myself that was too fast, and something must have failed. I returned to Update History in Settings, and found out what had failed to install and why it had failed: It was indeed the Feature Update, which was for Windows 10 2004! Rather strange that Windows Update presented and tried to install that on a computer using Windows 10 1909.

Not so strange, as the Feature Update was 2004 itself and WU tends to try to railroad people into updating. It got me last month, I was comfy as heck on 1903 and WU decided that needed to change. Now I'm on 2004 and this recently started happening. Apparently it's a fun little bug related to the update, from what I've been able to find.

M$ gets 2/3 on fixing trim/defrag bug. I still get ERRORS in Event Viewer due to HDD trim attempts:

"The storage optimizer couldn't complete retrim on Data(D:) because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)"

Yes, I'm aware its a cosmetic issue and won't break my HDD.

RaveBlack said:

Not so strange, as the Feature Update was 2004 itself and WU tends to try to railroad people into updating. It got me last month, I was comfy as heck on 1903 and WU decided that needed to change. Now I'm on 2004 and this recently started happening. Apparently it's a fun little bug related to the update, from what I've been able to find.

Perhaps, and thanks for the reply, as I had been wondering why no one commented on my report. When I do let Windows look for updates, it now always shows version 2004 as an available one rather than one that will be automatically downloaded. Given that, any efforts by MS to force the install of 2004 nicely failed.

I too was presented with this update today even though it was installed Sept 8th. Odd thing is Installed Updates in Control Panel shows installed Sept 8th but Update History in Settings shows today (yeah, chose install before I noticed what it was). Does anyone know why this might be?

OldGuyFromCdn said:

I too was presented with this update today even though it was installed Sept 8th. Odd thing is Installed Updates in Control Panel shows installed Sept 8th but Update History in Settings shows today (yeah, chose install before I noticed what it was). Does anyone know why this might be?

The update was released on the 8th, you upgraded on the 26th.