Windows Shell Common Dll is not responding

[pedrovay2003]

Ever since updating Windows 10 to the Creators Update, I've been getting this error every time I try to use my Bluetooth headset on my desktop. Wired headsets all seem to work perfectly fine, but if I switch tabs in the Sound settings window, or if I just talk on Skype for too long, my headset and the Sound settings stop working until I restart the machine.

I manually updated to the Creators Update on the machine that's having issues, and on a different machine in the house, it automatically updated, and I have absolutely no problems on that one. I've tried disabling audio enhancements, doing a system file check, uninstalling and reinstalling Bluetooth drivers, and allowing Windows to accept certificates, but I can't stop the issue from happening. I'm at my wit's end, and I really don't want to completely reinstall Windows just to get my Bluetooth headset working again.

 

[Sedivy]

Have you tried uninstalling and reinstalling audio drivers for your headset? If that didn't work I'd probably try to run a repair on my system if you've still got the disk for your win 10, hoping that would fix whatever got borked in the update.

 

[pedrovay2003]

Have you tried uninstalling and reinstalling audio drivers for your headset? If that didn't work I'd probably try to run a repair on my system if you've still got the disk for your win 10, hoping that would fix whatever got borked in the update.

Yeah, I tried getting rid of the Bluetooth adapter's drivers and the headset's drivers (it's a Jabra Classic, for what it's worth), but it never seems to fix it (I've tried more than one Bluetooth audio device, and they all have issues; anything else Bluetooth, like a game controller or my phone, works fine). I don't have an original Windows 10 disc, since it was an upgrade from Windows 7 --> 8 --> 8.1 --> 10, but I do have the official Microsoft ISO, so maybe I can do it from there. Is there a specific way I should do it, or just the standard repair procedure by booting from the DVD/USB?

 

[Sedivy]

Yeah an official microsoft iso and a bootable usb should do it. Your system will have your key stored still and should recognize it without prompting you for it. Assuming you create a bootable usb win10 correctly, and are able to boot, standard repair option it gives you when you boot from it should be sufficient. It helped me once or twice when I corrupted a few files myself. If you don't feel like doing all that, you could also try a system file check and then replace whatever corrupted files with individual files copied off of your other win 10 machine.
https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files
I still prefer the boot option but that's cause I've done it before. Whatever you're more comfortable with.

 

[pedrovay2003]

Awesome, thanks for the tips. I'll try that later today and post the results.

 

[pedrovay2003]

Okay, so, I did a repair install from a Windows 10 flash drive, and while it fixed a really annoying problem with my desktop icons moving whenever I added a new icon (which also only started after the Creators Update), it still hasn't fixed this particular message, and my audio stuff still freezes if I use a Bluetooth headset. I'm pretty stumped.

Would uploading a DxDiag.txt help at all, or am I pretty much screwed unless I start over? I've tried multiple times to reinstall my Bluetooth drivers, but I can't remember if I tried to reinstall the audio drivers, so I'll try that next.

 

[Sedivy]

I can read a dxdiag for only a very few specific things I've run into myself and I don't remember audio ever being one of those times so personally unlikely to help you with that, but someone could come along and read it, it won't hurt to post it (just do it in a spoiler so it doesn't make the thread 5 pages long) and yes it might help.

And yes try reinstalling audio drivers, if you need tips how here's a link, follow method 3:
https://answers.microsoft.com/en-us/windows/forum/windows_7-pictures/windows-shell-common-dll-not-responding-message/11bc6f72-9277-4caa-beb7-4ab363abd8f1

 

[pedrovay2003]

Okay, I uploaded the DxDiag to my Google Drive online; for some reason, posting it in a spoiler tag here results in a completely blank post. Here's the file.

I reinstalled the Realtek High Definition Audio drivers, and it doesn't seem to have fixed anything. I really appreciate all the help you've been trying to give me with this.

 

[Sedivy]

Heh I just wish it was helping. At this point I'd bug microsoft directly. They still are most likely to have useful answers on how to tackle this. That and I'd also post on the support site for whoever is the headset's manufacturer. If this is something limited to that particular headset or its drivers, likely they would have heard about it before and know what to do.

 

[pedrovay2003]

Okay, so, I seem to have accidentally discovered something: When I try to use the headset in a different Windows user profile, I don't think there are any problems. I noticed that some other unrelated issues are also nonexistent in other profiles, and those other issues also came about after the Creators Update was installed. I'm going to spend a bit of time using the headset in a new profile, and I'll report back.

 

[pedrovay2003]

So, even after playing with it in a brand new profile, it's still throwing up that same error. I honestly have no idea what to even test anymore at this point, but yeah, I think it might be time to see what Microsoft says.