This menu glitch has been happening through even the newest versions. I have to go through the control pane and then devices and printers to make changes to the printer properties. Print management for dealing with bad drivers and other issues. The basic settings menus need a lot of work and I believe that .net framework needs to not be considered a feature and a separate install. The whole thing is buggy. Support will be done for Win7 and having these little things makes a big difference in the IT world. Please fix it.
Windows 10 1903 can't manage a printer
I have a few Windows 10 Pro x64 1903 (with 2019-05 or 06 cumulative update) having an issue where when you use the modern Settings app > Devices > Printers & Scanners, when you click on an existing printer, the printer below it does not drop down making space for the the "Open queue" and "Manage" buttons, instead the buttons overlay the lower printer, but won't allow you to click on the buttons, therefore you can't manage the printer.
Windows for home | Windows 10 | Settings
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.
99 answers
Sort by: Oldest
-
Anonymous
2020-01-09T19:44:42+00:00 -
Anonymous
2020-01-18T06:17:49+00:00 I found that I could just use the Control Panel > Devices and Printers to do everything I wanted. The stupid "modern" interface failed miserably.
-
Anonymous
2020-01-29T10:38:04+00:00 We have the same issue here, doing it the old school way works but you would like it to work as before in WIN10.
Control Panel > Devices and Printers
-
Anonymous
2020-01-29T15:51:44+00:00 And I would like the whole OS to work such that i didn't have to go to online forums for workarounds and fixes.
-
Anonymous
2020-02-04T16:12:01+00:00 Is there a solution to this issue yet. I have the same issue. I have no issue with it as an admin, and I don't mind doing it the old fashioned way (Control Panel), but for my end users, that is an issue.
We are currently using Win 10 1909 and the issue continues (for standard users)
Thanks.
Terry