Solved Shell Hardware Detection Issues

Self-built / N/A
April 10, 2017 at 22:26:52
Specs: Windows 10 Home 1607, Intel i5-4460 3.20GHz
I just did a re-install of Win 10 on a new SSD. Afterwards, I noticed that certain things like renaming and deleting files caused hangs, i.e., deleting a file caused a green progress bar to display that hung at 99% for several seconds, and renaming a file or folder would cause the white text box to stay open for an extended length of time before closing and showing the new name. After a lengthy process of elimination, I discovered that disabling the Shell Hardware Detection Service at startup would resolve these issues. These problems did not occur before I re-installed the OS. Does anyone know why this might be happening and how I can resolve it permanently without disabling the SHDS? Thanks.

See More: Shell Hardware Detection Issues

Report •

#1
April 11, 2017 at 00:06:35
✔ Best Answer
After reinstalling Windows did you install all the drivers for your hardware from the relevant manufacturers website? if not then you will need to do this. Determine what hardware you have, motherboard, GPU, wireless adaptors etc and download the drivers for them.

it may also be worth installing the Intel Rapid Storage Technology driver

https://downloadcenter.intel.com/pr...


Report •

#2
April 11, 2017 at 09:26:10
Always-

Thank you for your response. Yes, almost the very first thing I did after installing the OS was to start updating drivers. It is always possible that I missed something, so I will double check.

I believe the Rapid Storage comes as part of the motherboard download package, as I know it is installed on my machine even though I did not specifically install it myself.

I appreciate your advice, and I will report back if and when I come to a final solution. Thank you.


Report •

#3
April 11, 2017 at 19:29:17
UPDATE-

My issue seems to be resolved. As I posted previously, after re-installing Win 10, I ran my driver updater app to update all my hardware drivers. Ironically, I neglected to update the UPDATER, so it missed some things. I updated the driver updater and reran it. Now I'm confident everything is caught up, and my computer no longer exhibits the problems I posted about earlier.


Report •

Related Solutions

#4
April 12, 2017 at 00:20:36
Hi flon_klar,

Glad all is working well now, just out of curiosity what updater are you using? it is usually recommended that you download the drivers directly from the manufacturer of each piece of hardware. This way you can be use it is the latest and GENUINE driver. However if in your case all is working I wouldn't worry too much about it, but I am still curious what updater you use.

Thanks for coming back with results.


Report •

#5
April 12, 2017 at 04:38:29
I'm using Driver Booster 4. Thanks.

message edited by flon_klar


Report •

#6
April 13, 2017 at 11:45:21
Well, it worked for a day, but the problem has returned. However, now it is only affecting folders; I don't seem to have a problem with files. I will again try to isolate a service or application, but it is definitely NOT the same Shell Hardware Detection issue from before; I still have that service disabled. All drivers have been updated. I have no disk errors. I may try a system restore back to when it WAS working.

message edited by flon_klar


Report •

#7
April 14, 2017 at 10:12:42
So after screwing with it for another 6 hours last night, trying many possible solutions, I found a thread on the Microsoft Tech Net forum with the following procedure:

"Run "regedit."
Navigate to
HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions.
From here there are 5 items that you need to delete or rename. In my case I just
renamed the folders with "-BAD" after the original folder name. If you want
you can also search for these strings so you don't have to manually look.
The names are:

{2112AB0A-C86A-4ffe-A368-0DE96E47012E}
{491E922F-5643-4af4-A7EB-4E7A138D8174}
{7b0db17d-9cd2-4a93-9733-46cc89022e7c}
{A302545D-DEFF-464b-ABE8-61C8648D939B}
{A990AE9F-A03B-4e80-94BC-9912D7504104}

After the rename of these folders the issue was instantly resolved."

I followed the procedure, and the issue was again resolved. I'm not sure yet if this is a permanent fix, or if there will be other side effects, but I hope this helps anyone experiencing the same issues.


Report •

Ask Question