Windows 10 1903 can't manage a printer

Anonymous
2019-06-18T19:32:28+00:00

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.

0 comments No comments

99 answers

Sort by: Newest
  1. Anonymous
    2020-04-03T11:05:38+00:00

    Interesting - I'm fine with the belief that it's a permission issue, but not sure why that folder would affect the display settings. 

    Just a reminder - all functionality is there if you use tab to get to the buttons and then ENTER to activate the button, the issue is completely around display.

    This is a viable workaround. You can move with TAB to cycle to the desired button until it gets highlighted and then hit ENTER, as you said.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-03-19T15:00:47+00:00

    For what it's worth, the option to set a default printer in Windows settings in v. 1909 isn't there. In the Control Panel, however, you can set the default. But when you do, a warning message pops up saying Windows will no longer be able to manage printers. I guess Microsoft has taken it on itself to do that for us.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-03-09T23:27:04+00:00

    Issue fixed with CU KB4535996 update (Feb 27th, 2020) (1903&1909)

    It works now! All good.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-03-09T17:53:06+00:00

    I have the same issue as the user described, I copy pasted the command into powershell as an administrator and it did not fix my issue.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-03-05T12:55:35+00:00

    YAY!!!!!!!!!!

    only 8 months :)

    Was this answer helpful?

    0 comments No comments