Remove vsflt58.sys
Hi,
I installed and then uninstalled ATHI2012
I ran the 2012 cleannup tool.
My system still uses Acronis vsflt58.sys as a driver on all disks.
I have searched this forum and google without success.
I need a straight answer to this question...
How can I get vsflt58.sys off my Win7Pro system (without breaking iit?)
Thanks, Ed
- Anmelden, um Kommentare verfassen zu können
Hi Richard,
Thank you for the quick and direct response.
So would the sequence be....
1) Delete the registry entry.
2) Delete the vsflt58.sys file itself.
3) Reboot
Ed.
- Anmelden, um Kommentare verfassen zu können
Yes except that, in addition to getting rid of the vidsflt58 service itself, you'll also need to search for any and all related registry entries (for example, where that service is used as an upper or lower filter) in order to end up with a complete cleanout.
I've only looked at my own WinXP registry where that set-up includes the LowerFilters=vidsflt58 entry for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}. There might possibly be others under other operating systems, which is why I'm always a bit shy about passing along any more specific regedit instructions to anyone.
- Anmelden, um Kommentare verfassen zu können
I've tried to remove it from the registry but could only find one entry for it. Removing that one entry made Windows generate a BSOD on boot. i'm sure it has to exist in other places, but I haven't been able to find it. i finally went back to a previous backup of my C drive and did a restore.
- Anmelden, um Kommentare verfassen zu können
Any attempt at manual removal of the "required for boot" (start=0x00000000) drivers and filters added by the Acronis application installer (or any other for that matter) is bound to be a hazardous undertaking due to various linkages and interdependencies. For that reason, one simply can't rely on a straightforward "one-at-a-time" approach and hoping for the best. For example, the "Acronis Virtual Disk Storage Filter" service is closely related to the "Acronis Virtual Disk Driver" service in that same critical boot category.
It therefore really requires a "clean sweep" of all such critically related service items on the first try and prior to rebooting, which is what the Acronis "cleanup" utility should do in theory at least, but apparently doesn't always succeed in accomplishing. While its "leftovers" can be annoying and may possibly slow system start-ups to some extent, it's probably best and certainly safest just to leave them alone and try to live with them remaining in place -- unless, of course, you can restore a pre-installation backup which is definitely the best solution.
- Anmelden, um Kommentare verfassen zu können