Windows 10: Frustrating AutoPlay behavior

Thanks for this reply! I'll give it a try and see what happens. Thanks for posting this on an older thread because I'm still having the problem.

 

Oddly, alas, the registry fix worked after applying it several times, but then didn't. My PC was, however, noticeably slow to recognise removal of a disk and update explorer.

I'm back to my little script which is reliable and effective.
;
; Poll DVD-RW drive for autoplay to detect drives
; and explorer to update
;
Loop {
Sleep, 900
DriveSpaceFree, Space, z:\
}

In another thread this issue is said to be acknowledged by MS....

 

Dalchina, I sincerely appreciate the effort you made, but to have to add a 3rd party app and create a script that requires a keystroke for a service that should run automatically is not a proper solution. Just saying.

MS needs to step up its game.

 

Agreed! What I don't understand though is why it only affects certain machines? I have several running windows 10 and this is the only one with this issue.

 

I'm beginning to wonder:
1) If it is due to folks having a SSD boot drive (C: )and a regular HD for files (D: ) - I do
2) Or, the type of motherboard

It is not an issue with the registry, it's a problem with timing and DLLs that kick off the read DVD service.

 

You misunderstand the script and what Autohotkey can do. I launch the script from Startup, and do nothing - all automatic. You can create entire programs with Autohotkey, not just hotkeys.

Quite agree, but I've more important issues than investigating autoplay (which I'm not bothered about) and if I've a workaround that makes explorer respond well without spending lots of time hoping for a fix, that's great and life can move on. (I use Autohotkey anyway, so no overheads there for me!)

Meanwhile let's give lots of feedback to MS (Windows key + ?) on this.

 

Hi all
I had purchased a brand new HP laptop last week. It came with WinX 1024 and I eventually managed to get it updated to the latest 1511 version.
Last thing I checked (before delivery to the intended user) was whether the optical drive worked. I was dumbfounded to find that it wouldn't read a disc. When I tried to open the drive the disc was ejected. Any disc I put it the drive just ground away continually and wouldn't open - and no sign of Autoplay.

I spend hours - literally hours - trolling the internet for a fix.
I tried setting different Autoplay settings with mixed and intermittent results.
I found the registry edits but was loathe to use them because the behavior I was seeing didn't really seem to fit :

• I could see the optical drive but discs wouldn't open when inserted
• I could add an external optical drive and I could see it as a new drive but discs wouldn't open when inserted
• I fiddled with the Autoplay settings - once or twice this worked but most times it didn't
• I could add a USB stick - it was recognized by Autoplay
• Strangely I could burn a blank disc
• The device manager seemed to have all the right drivers and no errors (I did a re-install at one stage)
• I checked the WinX registry against a Win 8.1 registry - it was missing NoDriveTypeAutoRun in HKCU but other posts on the internet suggested this wasn't really an issue.

Then I decided to turn off Autoplay in the Control Panel, Save and restart the laptop.
Voila ... I could see the discs mounted on the optical drive and I could right mouse click to open them.

So then I turned Autoplay back on , saved and restarted the laptop.
Autoplay started working as expected ......... what the ?????

I'm not going to look a gift horse in the mouth at this point and I'm hoping the fix 'sticks'.

I am also hoping that this simple fix works for someone else.