Green456 ✭

Just got the update and the problem is resolved! Good job! PS: Can you re-enable the bug for the 24st of December? To have some christmas lightning effect??

12 hours ago, hpw said: Hi again, well I had the key already at this position.... Also, started the latest Procmon even in admin mode and no events given. On my system 1809, 0.1% Disk activity seen on Taskmanager on Registry & System process. Added them by PID and showed no traces. May somethings is broken ... and…

3 hours ago, hpw said: OK, New boot new behavior as using 1809 1. The USB stick is pure NTFS 2.Applied the DWORD value again and reboot 3. Did the test again and the USB gets recognized 4. BUT the DISK READING was still present 5. applied the WMI pause what helped me on my single SSD Disk Cheers Hp Hi HP, This is my bad.…

3 hours ago, hpw said: OK, New boot new behavior as using 1809 1. The USB stick is pure NTFS 2.Applied the DWORD value again and reboot 3. Did the test again and the USB gets recognized 4. BUT the DISK READING was still present 5. applied the WMI pause what helped me on my single SSD Disk Cheers Hp Can you try to run…

3 hours ago, hpw said: Well, tested this on my Labtop with HKLM\Software\Microsoft\Policies\Microsoft\FVE\RDVConfigureBDE to (REG_DWORD) 0 ... Any plug-in of USB Sticks gets ignored... ... removed the DWORD key and rebooted and now USB gets recognized again .. IMHO opinion, it's may a MS issue where the WMI gets into a…

OK, now I took some more time and tested ProcMon.Exe on a system without BitDefender installed and if creating a new key with regedit the same "New Key #1" thing is shown. So this is a procmon problem with the way it resolves handles into paths and how regedit creates new keys, just wasn't fully aware of it.

This behavior could be normal due to the way regedit creates keys. At first the key is created as "New Key #1" and then renamed to the desired name. Could be some caching issue in either bd or procmon or maybe procmon is not tracking the API call that renames it, leading to the invalid path in the procmon log. The default…

Update 2: OK, all that New Key #1 stuff is not really needed. One can directly set HKLM\Software\Microsoft\Policies\Microsoft\FVE\RDVConfigureBDE to (REG_DWORD) 0. 1. At first there was no FVE key on my system as below: 2. Found a key not found error with procmon: 3. Created the FVE key that was not found before: 4. Now…

On 10/31/2018 at 11:54 AM, BDAlexS said: The feedback I'm getting is that the issue is BD with bitlocker enabled if people can confirm. Hi Alex, You was asking before regarding Process Monitor. Sorry for showing up so late. But anyways the problem is still here. Today I took some time to make screen shots and I could not…

12 hours ago, BDAlexS said: I can confirm USB card eject is fixed. However the USB card flashes all the time, it's difficult to nail down if this is BD or not (it's not the search indexer btw, I'm using a SD card I formatted with zero files). With the USB card out there is still a heck of a lot of I/O going on, see…

I found an easier "workaround". Instead of stopping/starting the service (and all the dependent services), we can instead pause and resume the management service like this: @echo off net pause Winmgmt net continue Winmgmt This method does not depend on if you have IA storage or some other controller. I hope a fix will get…