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-18T19:55:09+00:00

    Microsoft!

    Come in, Microsoft!

    Anyone home?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-10-18T20:20:36+00:00

    When you removed KB4517389, did KB4515384 appear? I installed 1903 V1 and did updates until KB4517389 installed, which is when print management broke on me. I never installed KB4515384, and after I uninstalled KB4517389 print management worked again. So if you can uninstall both KB4517389 AND KB4515384, it may work again.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-11-05T20:59:52+00:00

    Has anyone figured this thing out still getting the script error in Printer Management when clicking on any of the printers. On Microsofts "Latest" build OS: 18362.449 and do not have the updates specified installed on my VM for removal.

    This is pretty Annoying!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-11-05T21:12:03+00:00

    So far, the 'fix' seems to be to stop using extended view.   <sigh>

    Was this answer helpful?

    0 comments