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: Most helpful
  1. Anonymous
    2019-10-15T17:22:59+00:00

    OS Name    Microsoft Windows 10 Pro

    Version    10.0.18362 Build 18362

    I'll check for updates.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-10-15T17:20:59+00:00

    Yes, only when using extended view.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-10-15T17:01:12+00:00

    what version of Windows are you guys using?

    the print management console error might be caused by the out-of-band updates Microsoft released between Monday Sept. 23 and Friday Oct. 4.

    the problem might be fixed by installing any of the recent security updates released on Tuesday October 8.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-10-15T00:21:23+00:00

    we have the same issue only when we have extended view showing.

    Was this answer helpful?

    0 comments No comments