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.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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)
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.
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.
Hello,
I have a Windows Server 2019 Print Server. I was experiencing the same issue with the script error. In my case I uninstalled KB4534273. After a reboot, the seemed to resolved. I will talk to our Security Officers to see if there is an upcoming cumulative patch that will correct this.
I hope this helps.
Hello,
I have a Windows Server 2019 Print Server. I was experiencing the same issue with the script error. In my case, I uninstalled KB4534273. After a reboot, the seemed to resolved. I will talk to our Security Officers to see if there is an upcoming cumulative patch that will correct this.
I hope this helps.
Hello,
I have a Windows Server 2019 Print Server. I was experiencing the same issue with the script error. In my case I uninstalled KB4534273. After a reboot, the seemed to resolved. I will talk to our Security Officers to see if there is an upcoming cumulative patch that will correct this.
I hope this helps.
are this KB include in some other Update, because I do not have installed it alone.