Why is there no "troubleshoot hardware & devices" in 1809 update?

Anonymous
2019-01-01T10:13:30+00:00

I have looked everywhere in settings & control panel, & there is no longer a troubleshooter for hardware & devices. All of the other troubleshoot options are still listed , & there is no "view all." In 1803 I could access it in " update & security" then chose "troubleshoot" & it was the 4th one listed under "find & fix other problems" where "keyboard" is now. Unless Microsoft will come up with a fix, I guess the only solution is to go back to 1803?

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
Answer accepted by question author
Anonymous
2019-01-02T05:27:14+00:00

Hi,

Thank you for writing to Microsoft Community Forums.

Please note that Hardware and Device troubleshooter was removed from Windows 10 starting from the build version 1809. The Hardware & Devices troubleshooter had the lowest daily usage was usually run in tandem with other troubleshooters, therefore it was determined it was no longer needed and specific troubleshooters should be used instead (i.e. Bluetooth, audio, etc.).

Hope it helps.

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments

64 additional answers

Sort by: Most helpful
  1. Anonymous
    2019-08-12T18:22:07+00:00

    Guys this is utterly ridiculous. You can't justify removing an app because it was the least used out of that family of apps. Especially when it was the general troubleshooting program. Now what do we use to troubleshoot a general, unknown issue? Also which included troubleshooter are we supposed to use to troubleshoot storage devices? That is why I found this Question page. I have error 38 for a device, I can reboot to fix the error, but it keeps occurring so I need a proper fix. I have tried uninstalling the device but that didn't even work. I was directed to the hardware and devices troubleshooter, but now it is missing.

    As per usual, no useful help has actually been imparted by any Microsoft employee here, and they have gone silent at the mention of disappointment in one of their many terrible decisions.

    This, people, is what happens when a multinational corporation create a strangehold monopoly over a global technology.

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-06-25T21:41:52+00:00

    That is a great summation of the problem. I go back to the DOS days of personal computing. MS had the technical side of the tiger by the tail, but they wanted to be user friendly like Apple. Now they try to hide everything technical, but they are hiding too much for the "dumbed down" audience they wanted to create. If they aren't going to give us a totally useful GUI, then quit messing with the command line side, and let us fix it ourselves. By making it easier for the newbies, they make it harder for experienced users to find what they need. The end result is that they are making fewer people happy all the time. I'm about to go to a Linux OS that doesn't need to be fixed every month.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-06-07T01:28:18+00:00

    Interesting, so if I have an SD Card Reader issue, not being recognized and I don't have a new SD Card Reader Troubleshoot tab showing up, how can I trouble shoot without the Hardware and Device Troubleshooter? Sigh!

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-05-13T10:34:59+00:00

    I am getting a "Hardware Error", with little detail.  Many sites point me to this Hardware and Device troubleshooter.

    I am with others in that I am dumbfounded by the decision to remove this in 1809, especially ironic since this patch caused so many hardware issues (including for me, with much pain).

    Please consider adding it back.  After all, there is MUCH documented online which references this tool.  The lack of it is very frustrating.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments