This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
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.
I got this page because experiencing a similar problem. My client complaining they suddenly could not print from another computer (share). I uninstalled the update. But, it was automatically downloaded and installed, and I must remove it again. Hopefully, the patch solve the issue.
I just tried to perform all of the most recent updates and that unfortunately did not work for me.
It is just not right that we have to then go into the registry and attempt to perform an edit to fix this issue.
This is just unacceptable!
The print nightmare debacle continues!
M$ - please get on this and offer a correct fix!
I reluctantly applied to the registry via an edit [after backing-up the registry] using regedit.
It worked; however, that really should not have to be the solution; and for some it may still not work.
Here's an article that may help others:
Windows PrintNightmare: Status, issues and workarounds (Sept. 22, 2021) https://borncity.com/win/2021/09/22/windows-printnightmare-patch-stand-und-workarounds-22-sept-2021/
Good luck!
I just tried to perform all of the most recent updates and that unfortunately did not work for me.
It is just not right that we have to then go into the registry and attempt to perform an edit to fix this issue.
This is just unacceptable!
The print nightmare debacle continues!
M$ - please get on this and offer a correct fix!
Microsoft is an absolute nightmare! But install the latest update and I found it fixed the issue.
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
