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 No 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 No comments

69 additional answers

Sort by: Newest
  1. Anonymous
    2019-12-10T16:14:15+00:00

    KB4524570 is a security update.  Trading one problem for another.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-12-10T16:05:05+00:00

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

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-11-06T03:30:50+00:00

    I've posted this topic in Spiceworks as well. There are a number of IT Pros working on this to find the solution. Haven't heard from Microsoft yet. 

    Link us?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-11-05T21:25:33+00:00

    I've posted this topic in Spiceworks as well. There are a number of IT Pros working on this to find the solution. Haven't heard from Microsoft yet.

    Was this answer helpful?

    0 comments No comments