Is Here any Microsoft support agent who can support us to resolve this issue?
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-12-23T13:23:00+00:00 -
Anonymous
2021-12-23T12:43:31+00:00 I am also facing this network shared printer not accessing @ multiple locations, Dont understand why Microsoft gives solutions for their users. Tried with KB5007253 this update also but issue not resolve. Called multiple times to Microsoft but they also could not give a firm solution and told me to reset PC. Dont u think its really failure of microsoft to give the firm solution fast.
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2021-12-06T07:14:34+00:00 just updating my own post, nope it doesnt work once the printer host updated again
-
Anonymous
2021-12-03T00:14:18+00:00 just want to update you guys that the latest updates, which ever it is, solve the issue.
I just update it from time to time thats why I dont know which one fixed it.