New
#11
Before doing a repair install, and since this is USB related, you could try going through the steps in USB Driver - General Fix for Problems and see if you are able to reclaim your USB drivers for the drives. :)
Before doing a repair install, and since this is USB related, you could try going through the steps in USB Driver - General Fix for Problems and see if you are able to reclaim your USB drivers for the drives. :)
Thats a good suggestion. But if there are registry entries that insert Acronis control over the drivers it will rewrite on a boot and you are back to the same problem. That is what was wrong with my system and hard drive drivers. Once I eliminated the driver files the registry started giving me the code 39. My hard drives were functioning because it was loading the correct drives as well as attempting to load the Acronis drivers
Yeah, I've read these problems with Acronis in the past. That is why I will not touch the program even if it came "free" on one of my external drives. I have tried to research methods to remove such Acronis entries from the registry, but I have not yet found a solution. I will post back if I do.
I found this site very informative: Leftover Drivers? | Knowledge Base
Also: 24545: Acronis True Image Home 2012 Cleanup Utility
I definitely agree with your thinking. As a software engineer myself... Nevermind, I will not go there... I am just trying to find a viable solution for the OP. There do not seem to be too many out there.
Question for you HammerHead: Did you do everything in the "correct" order as outlined in that first post? I am curious whether that post is as helpful as it seems to be.
I must admit I did not. The excuse might be lame but here it is.
I fought the problem for a day and a half before I found the thread. I had really dug into my system. The two .sys files were already gone when I found the thread. So that puts me out of sequence. What I was fighting was not my usb. My drives all had extra drivers after the delete. I was loading the two MS drivers and I had entries in device manager for two more which I had deleted and hence I was getting the error 39. Every time I tried to delete the registry keys in the procedure I got a Bsod on boot and had to put in a restore point. Although I work on the resistry I would not call myself well versed in it. Here is a link to the thread I was working with. It shows the extra drivers that was the problem.
Disk Driver Problem
Some of this may help the poster. It was a total disaster for me. But you have to remember User + Software + Hardware when all summed together creates unlimited solutions. Some work for one person and not for the other.
That sounds good. The ones I deleted were from Acronis because I checked the properties before deletion. But your suggestion sounds good and logical. I would try that But I have a new system now so no problem. The poster should try writing over that file (files, two to be exact). I do not know what that would do about the attempt at loading them during a boot. When in fact they do not belong in the listing in device manager normally. This poster has a usb problem but it is related I feel to some Acronis leftovers.
I take back what I had written... confused an Acronis file with a system file that had a similar name, but they are not exactly the same. It sounds like if those directions in the previous post are followed in the correct order, it may be useful to the OP. If not, there are other ways around the registry issues. I may have to play around with Acronis myself to figure them out, but I'm sure it can be done. I have a system image right now that I can revert to if Acronis royally messes up my system, so I am not too worried about it.