![]() ![]() Its been weeks, and so far no official fix or acknowledgment from Bitdefender. ![]() UPDATE: TEMPORARY FIX!!! FOR ANYONE STILL HAVING THIS ISSUE: Which all seems to line up with Bitdefender free causing this issue, my question is given the free version is on its last few months will Bitdefender bother to do anything about this? Are they even aware of it? Is there someone on this subreddit who is connected with them that can offer some insight?Įither way, I'm hoping for a fix, if anyone else has had this issue and has any idea on a solution other than completely removing Bitdefender free I'd be happy to know :)įWIW a restart does fix it but seemingly only for the first plug in/until its slept and then it happens again, so not ideal. Then it dawned on me that Bitdefender free updated last night, and I had only slept my computer and not shut it down, so it got me to thinking and I asked them when it updated the program for them and sure enough it lined up.Īnyway had a small search and found this thread. ![]() Tried many things, nothing would work, then just today mine started doing the same thing. (Code 38) The driver could not be loaded because a previous version of the driver is still in memory." in device manager as the ! error. So yesterday my mate was telling me about a problem he was having with his USB drives not being recognised in Windows after sleep and showing "Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. ![]()
0 Comments
Leave a Reply. |