Thanks smartcooky. Keep us posted.
I did see that fix in my research, but haven't had time to try it. It's good to know it works (at least temporarily).
These workarounds are great, but I am continuing my search for a permanent fix - one that wont get wiped out on some future update (like 6670).
Update: Ok, so I've just tried it, and I get the same result on the client.*
Client fully updated with KB5005565 and KB5006670, and with RpcAuthnLevelPrivacyEnabled set to 0
Printing stalls with no errors
I overwrote win32spl.dll with the older version, restarted client, and it prints fine.
*NOTE: when the host failed to print, the print dialog status column remained blank, but when the client failed to print, the status column showed "printing", but it just didn't print.
Yes, that's the behavior I got too.
I'll need to grab win32spl.dll from one of the client PCs, as the host is already on 6670. Should be the same file.
Just confirming that the behaviour is the same for my other two client computers
• KB5006670 stops network printing
• Replacing the new win32spl.dll with the previous version restores network printing
Confirming that KB5006670 have same behaviour at my pc.
uninstaling and creating NoAutoUpdate kay for win updates working for now.
just hope that kay will work for a while!
Bleepingcomputer.com article on the subject from October 15th:
New Windows 10 KB5006670 update breaks network printing
That is a good summary of what we know to date.
They key part of that article:
"What makes these printing issues so frustrating is Microsoft's lackof clear guidance and the numerous changes that happen each month to the Windows printing feature.
As these changes all resolve different vulnerable aspects of the Windows Print Spooler, they create a mess of individual fixes that Windows admins need to figure out whether they will fix their printing problems.
BleepingComputer has reached out to Microsoft for official guidance on resolving all of these issues but has not heard back at this time."
Quote