Print Management Console Script error?

Anonymous
2019-10-03T13:40:53+00:00

For the last couple of days I get this error when accessing printer properties or just selecting a printer in the print management console:

Anyone else having this issue?  Selecting yes or no has the same effect, i.e., none that I can tell.

I manage several print servers from the management console so looking in my workstation devices and printers isn't the answer. (seemed to be the answer of choice from a similar thread I saw and isn't applicable)

Windows for home | Windows 10 | Devices and drivers

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
Answer accepted by question author
Anonymous
2020-01-29T13:28:52+00:00

This update fixes the issue for current versions of Windows 10 (1903, 1909).

https://support.microsoft.com/en-us/help/4532695/windows-10-update-kb4532695

I just applied this and the Print Mgmt. Console is working again.

Was this answer helpful?

8 people found this answer helpful.
0 comments

69 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-10-16T00:26:44+00:00

    We can confirm the same issue, two separate fully patched windows 10 machines.  Either see:

    when we first open the console, ![](https://learn-attachment.microsoft.com/api/attachments/271c089a-c4f4-483b-b717-27370d80ea00?platform=QnAor subsequent errors..

    only when extended view is on, which we use all the time to manage toner levels... we have 40 plus printers... neeed this console!!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-10-17T19:05:23+00:00

    We are seeing this as well. It's very disruptive to our workforce trying to support 500-600 printers. Please advise.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-10-17T19:12:36+00:00

    The latest Windows Update did not fix the issue.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-10-18T13:53:36+00:00

    You mean I'm not alone?! This is infuriating. Verified the same error on two separate and fully patched Windows 10 Pro 1809 workstations connecting to the print server that's Server 2012 R2. And if I remote directly into the server, the Print Management snap in works perfectly fine.

    EDIT: The print server is also fully patched, and it's the only role it performs.

    Was this answer helpful?

    0 comments