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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2019-12-10T21:01:36+00:00

    This issue is scheduled to be fixed on Windows Server 2019 in updates releasing around the 3rd Tuesday of January 2020 and on 1903 a week later. 

    Look for KBs with release note text similar to "Fixes an issue where the Print Management console may display script errors when enabled the Extended View option."

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-12-10T19:07:31+00:00

    I uninstalled it, restarted, enabled extended view...and got the same error.  Didn't fix it.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-12-10T18:37:02+00:00

    I uninstalled KB4524570 and the script error went away........................Problem solved.

    Same here! and to the point about security update from Brian Freeman, the security hole "may" be a problem...some day, but the script error is now and real. I'll gladly take the risk. 

    Vince

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-12-10T16:20:31+00:00

    it's almost interesting how KB4524570 was released Nov 12 and yet the issue started well before I posted question in October.  It had been happening for a while before that.

    Was this answer helpful?

    0 comments