KB5004945 Windows 10 2004 19041.1083, 20H2 19042.1083, 21H1 19043.1083 Win Update

Personally I am surprised that there aren't more issues with updates considering all the different system configurations there are out there. When a new update pops up I like to see just what other users are encountering with the install/operation.
I'm imagining that's why MS has the insider's testing the new OS, and updates, but they still can't catch everything.

I notice that if users are having issues with a particular update some will decide to just wait it out a little to see if things clear up.
So there is value for them.

Now if I was responsible for maintaining a number of systems I can well imagine the frustration trying to sort everything out !

Done on two machines and no issues so far. Before installing this out-of-band update, I reenabled "Print Spooler" in services.msc because it was disabled. Didn't want to take a chance not knowing what kind of errors could have come up keeping it disabled while installing this update. Now, I am keeping it enabled on "Automatic" and hoping that I am not incurring any risk after this update.

Currently been stuck on 21% for ten minutes. For installation. After being stuck on 100% for ten minutes. This is taking an extremely long time to install.

Either I haven't been paying attention, but now I see a negative sign in front of the 21%. Unless that's always been there in every update.

Not sure what has been going on with updates lately. Half of my computers get an error the other half install just fine. It has been this way for two months.

IronZorg89 said:

Done on two machines and no issues so far. Before installing this out-of-band update, I reenabled "Print Spooler" in services.msc because it was disabled. Didn't want to take a chance not knowing what kind of errors could have come up keeping it disabled while installing this update. Now, I am keeping it enabled on "Automatic" and hoping that I am not incurring any risk after this update.

I don't think that is a good idea. It doesn't sound like this hotfix has solved all of the problem.
Microsoft’s emergency patch fails to fix critical “PrintNightmare” vulnerability | Ars Technica

Mc Ruff said:

I don't think that is a good idea. It doesn't sound like this hotfix has solved all of the problem.
Microsoft’s emergency patch fails to fix critical “PrintNightmare” vulnerability | Ars Technica

Oh boy. Thanks for letting us know.

Mc Ruff said:

I don't think that is a good idea. It doesn't sound like this hotfix has solved all of the problem.
Microsoft’s emergency patch fails to fix critical “PrintNightmare” vulnerability | Ars Technica

Big thank you for the reference and the advice. I will (am going to) disable the "Print Spooler" in services, meaning put it as it was before.

IronZorg89 said:

Big thank you for the reference and the advice. I will (am going to) disable the "Print Spooler" in services, meaning put it as it was before.

Doesn't that mean you will not be able print at all ?