Cumulative Update for Windows 10 Version 1903 KB4517211 (Causing HP Printer Spooler to Stop)

Yeah, same. Print spooler would immediately crash each time I tried to restart the service.

Thank you GBorn.  I am the one who started the post on this subject on the AskWoody website.  I'm glad it is getting attention.

Hi Jay119.

Perhaps you should also report this problem in the HP support community forums and get HP's attention since the problem does not seem to be reported there yet.

I don't know if the printing problem with the KB4517211 update is limited to just certain HP brand printers or if it occurs on other name brand printers.

I posted the following in HP Support Community Forums (under InkJet Printers)

Microsoft Cumulative Update for Windows 10 Version 1903 KB4517211 and Printer Spooler Service

‎09-30-2019 10:42 AM

Product: HP Officejet Pro 8210

Operating System: Microsoft Windows 10 (64-bit)

The Microsoft Cumulative Update for Windows 10 Version 1903 KB4517211 is causing the printer spooler service to stop and the installed printer is no longer recognized.  It is an HP Officejet Pro 8210 printer though there are reports  that it is affecting other HP printers too.  It was suggested in the Microsoft Community forum that I post the issue here to gain the attention of HP personnel so they are aware of the matter.  

When I go into services.msc I can start the spooler and my printer then reappears but as soon as I try to print the spooler service stops.  If I uninstall update KB4517211, my printer again works.   

Considerations:

• Ran troubleshooter (printerdiagostic10) while update was installed and no issues were found.
• Tried to stop the update from downloading using Microsoft utility (wushowhide).  It said the update was being hidden yet it still installed.
• Posted issue in Microsoft COMMUNITY.
• Chatted with a representative at Microsoft ADVISORS who referred to me Microsoft ADVOCATE.
• ADVOCATE performed an In-place Upgrade with Windows 10.  This did not solve the printer spooler issue so I first did a system restore (successful) and then uninstalled KB4517211 (successful).  Printer again is working.

Obviously, this is an issue with update KB4517211 but, as mentioned above, HP personnel should be made aware of the problem and hopefully, in conjunction with Microsoft, a fix can be developed and made available.      

thanks for posting there in the HP forums, Jay119.  I read your post there and so far Hewlett-Packard (HP) has not even responded nor replied to it yet (I mean, what's up with HP?)

so it looks like a Microsoft only problem with the recent updates causing these printing issues on some of these HP printers and uninstalling any of these updates seem to make the printing problems go away.

I do IT with the State Government here in Alaska, and this is impacting our network printers as well as local printers. Seems confined to HP's currently. The only fix we have found is to remove the printer and drivers, then load just the HP Printer universal driver. I have fixed a coupe in my office that way, and our NS has fixed one of our network printers that way. Might be a viable work around until a better fix comes along.

To erpmanila3w:

Yes it is a Microsoft issue. 

Here is GBorn's post from earlier today (10/01/2019):

Just for affected users an information. My escalation here (probably) resulted in a confirmation from Microsoft - see Windows 10 status page - the issue affects probably only a couple of users - but it's spread to users of all Windows 10, Windows 8.1, Windows 7 SP1 clients and also affects Windows Servers. 

Microsoft blames the out-of-band Internet Explorer security update KB4522016 as a root cause.

Blogs: http://www.borncity.com/blog /(Ger) - and - http://borncity.com/win/ (EN)

Addendum (Sept. 30, 2019): As the previous poster wrote - Microsoft confirmed the bug - see  Windows 10 V1903 status page - but I don't agree with Microsoft's explanation to blame KB4522016 - see also my blog post Windows: Printer issues after Sept. 2019 Update confirmed - I got feedback from users, who are affected and had never installed KB4522016.