Both of the below hotfixes can cause the issue. Users will either be in one or the other.
KB5006670
KB5005565
removing them should sort it out.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Both of the below hotfixes can cause the issue. Users will either be in one or the other.
KB5006670
KB5005565
removing them should sort it out.
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!
Shared Workgroup printers have stopped working as well. Removing this update (KB5005565) corrects the problem. Is there a way to hide this update or is there a fix in the works?
I am also having same situation at my office we also uninstalled that update now it's working fine but next day again that update installed so facing same issue
Microsoft
Please findout permanant solution
Did you try changing the regkey as per the article I shared from September 24? (RpcAuthnLevelPrivacyEnabled)
Cannot find the way to make it work with this update.
=(