I have just disabled "Print Spooler" in Services for both of my machines. I usually don't print that much. Will temporarily enable them if need be until MS finds a way out of this nightmare.
Last edited by IronZorg89; 17 Aug 2021 at 14:01.
I'm pretty sure it said 21H1 when i upgraded (from 1909, so I skipped 2009/20H2 anyway) back in June. Either an update or some other mysterious thing has since changed the version number. I don't remember doing anything out of the ordinary, and all the updates since June have gone smoothly. Also sfc reports no problems.
So, I had a heck of a time with this update for some reason. It threw an error twice and once just hung at downloading 100%. So I cleaned things in the download folder, ran Dism and SFC, and went on a hunt to find some info. I found an article about Bits service. Sure enough my Bits service was turning itself off .When windows update got to 100% downloaded the next time, I let it sit for around 5 minutes then started the bits service which had shut off and immediatly it installed. Ran Dism and SFC and this time all was well. I have set the Bits service to auto start but read that it may go back to manual. Anyway big sigh of relief. Been trying since yesterday with this update. Also I have disabled the print spooler service after reading about the new exploit.
Hi,
@babyblue:
If you're familiar with using the registry editor you can fix this by editing the following hive key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
Do a search for CurrentVersion and check if the displayed version of Windows corresponds to what you see when calling Winver.
It should be identical.
BuildLab should show as : 19041.vb_release.191206-1406
BuildLabEX as : 19041.1.amd64fre.vb_release.191206-1406 (In my case as I run the 64 bit AMD version)
The above two lines are for the correct version as shown when you type "ver" in the elevated command prompt window.
Hope this helps,
Quote
