Windows update. Printers not working AGAIN

[Loose rivets]

I see there's a new warning for very recent updates. I also see my PC has been updated with the offending cumulative item. Un-installing seems to be the only option.

https://www.bleepingcomputer.com/news/microsoft/windows-10-printing-breaks-due-to-microsoft-june-2020-updates/

[esscee]

Here we go again. Don't they properly test these updates before releasing them? Who needs computer viruses when Microsoft pay their own people to bugger up their customers' PC's. Tossers!

[stevef]

I spent most of yesterday trying to fix my printer problem and finally found out that it was that @*&%$~+ update to blame. It took some finding but the fix was to do a system restore, which gave me the printer back then go to services.msc and disable Windows Update on the General Tab. Then go to the Recovery Tab and set all the 'Failures' to Take No Action. Then reset the Fail count to zero. That'll stop the Automatic Updates from downloading the same problem.
Apparently this fix gets over-ridden after a certain amount of time by the Windows Update Medic Services (just below the above entry) so you'll need to download Windows Update Blocker, which will prevent that happening. Really simple to use. I'll revert to normal once Microsoft issue a fix.
I wish they'd let us manually uninstall updates as easily as previous Windows versions. There was no option for that on my computer. Give me W7 over 10 any day.

[esscee]

I keep changing the date of Auto update "Pause", postponing long enough for the idiots at Microsoft to get a grip and get a working update of the original failing update. If you see what I mean.

[WB627]

I had this problem last year and it took me until March this year to find a fix that did not involve rolling back to the previous 1803 version of windows .

I started a thread on it in December …….. https://www.pprune.org/computer-internet-issues-troubleshooting/627856-windows-10-nov-update-wipes-out-printers.html?highlight=Windows+update#post10635185

It's rather long but it may help you. In the end the primary problem seemed to be a corrupted version 1809 update file which tried to keep installing itself. In the end I moved all the update files in C \Windows\SoftwareDistribution\Download into a new folder called Backup Downloads, so the folder was empty and it could not use a previously downloaded file and had to download a fresh copy.

It didn't solve all the problems but it was a big step in the right direction and it didn't take me long to get it all sorted out. I've had several updates since then (minor not full blown new versions) and they seem to have installed without any issues. I have stuck with 1809 but I don't think the Microsoft Collective will leave me alone for much longer :uhoh: and will make me go to 1903, 1909 or even 2003 :eek:.

stevef - Do you know which version it updated you to?

[stevef]

WB:
I've checked my Belarc Advisor profile and it is/was 1909. I imagine the build update must have been 2004.
Apparently the print spooler problem introduced by KB4560960 has been rectified by KB4567512:

From Microsoft:
Print spooler might error or close unexpectedly when attempting to print
After installing KB4560960 (https://support.microsoft.com/help/4560960), certain printers may be unable to print. Print spooler may error or close unexpectedly when attempting to print and no output will come from affected printer. You might also encounter issues with the apps you are attempting to print from. You might receive an error from the app or the app may close unexpectedly. Note This issue might also affect software-based printers, for example printing to PDF.

Affected platforms:

Client: Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
Server: Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2012 R2; Windows Server 2012

Resolution: This issue was resolved in the out-of-band update KB4567512 (https://support.microsoft.com/help/4567512). It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB4567512 (https://support.microsoft.com/help/4567512), search for it in the Microsoft Update Catalog (http://www.catalog.update.microsoft.com/home.aspx). You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog (https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/manage/wsus-and-the-catalog-site#the-microsoft-update-catalog-site) for instructions. Note KB4567512 (https://support.microsoft.com/help/4567512) is not available from Windows Update and will not install automatically.

I'll make another restore point and install it.

[WB627]

Why do they ALWAYS get this wrong when they roll out a new version of Windows 10?

Oh yes I forgot, it took out Cute PDF writer as well!!

[stevef]

KB4567512 did the trick. The printer works fine and all updates were installed after resetting the Services tabs. The build number is still 1909 though.

[WB627]

OK so with time running out on 1809, I bit the bullet yesterday and let the Collective infest my PC with 1903. So far all seems ok, printers are running ok and no other obvious problems. I have 1903 or possibly 1909 running on some pf my laptop so I was hopeful it would install ok on my PC.

I also installed the new Edge and will post on the Edge thread about this.