Well I don't want to tempt fate but this mornings Windows Update (November 22, 2021—KB5007253) appears to have fixed my printing problems.
KB5005565 - Issue accessing Shared Printer
One of the systems(Windows 10 Pro - 21H1) in domain had a shared printer (Epson LX-350) which was inaccessible over the network, print works locally without an Issue.
Print was fired from the network system but ends without an error, one of the error logs in administrative Events suggested error 372 and so followed every step as suggested for “PrintNightmare” but unfortunate nothing worked positive. Tried removing the printer from the network desktop and tried to add the shared printer. Now it wass understood that the issue is something restricting the shared printer to be accessed thru any version of Operating System (Tried with another Win 10 & Win 7 Sp1).
Uninstalled KB505565 and was accessible, What is the technical reason and any work around?
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
73 answers
Sort by: Most helpful
-
Anonymous
2021-11-23T16:24:38+00:00 -
Anonymous
2021-10-07T19:21:02+00:00 It's been 3 weeks and this problem has still not been resolved. Local printers of any brand are still NOT shared with other stations on our network because of KB5005565. I turned ON updates and KB5005565 was (once again) re-installed....and (once again) the printer sharing issue returned. Had to (once again) un-install the update and the printers work fine. We need a long-term solution for this issue. PLEASE!
-
Anonymous
2021-10-06T14:33:09+00:00 Just had a recent update from Microsoft: KB4023057: Update for Windows 10 Update Service components.
This seems to have resolved the issue. All our network printers are now working again.
-
Anonymous
2021-10-05T10:11:53+00:00 uninstall the update is only solution right now
-
Anonymous
2021-10-05T10:05:53+00:00 only chatting research done else who has time to resolve and fix update issue