KB5005565 - Issue accessing Shared Printer

Anonymous
2021-09-16T06:10:47+00:00

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.

0 comments

73 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-12-23T13:24:12+00:00

    Can U or Your team help us to resolve this long pending printing issue due to win 10 update.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-12-23T13:48:28+00:00

    After weeks of our customers disatisfaction, and after the latest windows updates, our team managed to find a working solution to the problem:

    1. On the computer that shares the printer (call it server), activate the administrator account, and secure it with a password.
    2. On the client computers, add the credentials of the server's administrator account.
    3. Restart everything
    4. Map the shared printers on the client computers.

    Hope this helps, was september, now its cristmass...

    Was this answer helpful?

    0 comments
  3. 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