Bit Defender Total Security (BDTS) and Windows AutoPlay

I installed BDTS on 28th January 2025 and, up until about 2 weeks ago, a File Explorer window would launch whenever I inserted a USB stick or external USB drive. I remember seeing a BDTS alert regarding AutoPlay stating that it was protecting my device by disabling AutoPlay and since then FE no longer launches when USB devices are plugged in. I can understand the security logic and it easy enough to launch FE myself to view and manage files on the devices.
My question relates to how does BDTS stop FE launching? I ask this because AutoPlay is still enabled in Settings and should ‘Open folder to view files (file explorer) but it doesn’t.
Also, BDTS scans USB connected devices every time they are plugged in so AutoPlay launching FE to view files should not be a problem. It seems that blocking AutoPlay from launching FE is an unnecessary inconvenience.
Does anyone know how I could change it back for AutoPlay to launch FE if I wanted to. Maybe it is a registry hack?

@wiganken


There should be a 24/7 phone number you can call (Bitdefender tech support).
We have one in the US, so I'd imagine you do in the UK as well.

If you open the Bitdefender control panel, under protections there is likely a setting to disable that. Making an assumption here as I don't have their product

I have checked inside BD control panel and I can't find anything regarding disabling AutoPLay. I suspect BD did something to the registry that might stop AutoPlay working but that's just a guess.
@Ghot - I don't want to get involved in complex phone calls but there is a Bit Defender community that I may try. Thanks for the idea though.

Can you check to see if this value exists in the registry? You can do a search from regedit.
NoDriveTypeAutoRun

@neemobeer - Yes that name exists with a value of 0

Okay, I fixed it. In case it helps others who want AutoRun 'On' for all external USB devices: -
I got the fix from Simple Steps to Disable AutoRun/AutoPlay

Simply delete the DWORD NoDriveTypeAutoRun from two locations in the Registry.





Because the issue on my devices only began nearly 3 weeks ago I suspect that BDTS created the DWORD. I know I didn't do it.

Bit Defender are currently looking into the issue and checking for a possible bug in their Immunizer function. See: -