Ok... So what is the fix? .. I really don't want to uninstall Acronis on a whim.

I checked and it is already back to 0. Must have been reset as part of the return to "Last Good..."

I'll see if everything runs normally for awhile. Then I may uninstall Acronis to give your product a test. I'm a little reluctant to do that because Acronis is working OK. But your product seems like it would be simpler and more reliable.

Should I uninstall Acronis TI 11 via Add & Remove programs? Will that remove all of it or is there something else I will need to do before testing your product?

 

Only one of this kind of scheduled-imaging program can be installed at any one time. This isn't anyone's fault except maybe Microsoft's. I've experimented with ShadowProtect, Acronis, Paragon Drive Backup, etc. - only one can be installed at a time. You simply can't have two installed at one time. If you want to find out if one is better than another, then the ONLY way to unistall the one you aren't testing.

You could have uninstalled Acronis and then reinstalled it (if you wanted to) in much less time than you spent in trying to make these partial fixes.

In summary: if you want to test ShadowProtect you MUST uninstall Acronis TrueImage. End of story.

 How is deleting other drivers kernel objects (info by Nate) the fault of StorageCraft's driver? To conjure a car analogy, StorageCraft is a careful BMW X5 driver while Acronis drives a rusting russian forty ton truck with after market turbo chargers and a careless "step on it tomorrow we might be dead anyway" driving style. And before anyone asks, that is my personal perception, your mileage may vary. ;-)

We have switched everything in our company to SP and haven't looked back.

>How is deleting other drivers kernel objects (info by Nate) the fault of StorageCraft's driver?

As far as I can see, no one has even suggested that StorageCraft's driver is at fault. Perhaps you misread an earlier message?

 I think I misread your last post. Not being a native speaker I think the service in my head for understanding English language was not fully booted yet.

Did EvolutionXGsr ever receive a clear answer on how to safely remove snapman.sys from his/her system?  If not, here are helpful details:

When you attempt to remove Acronis True Image's snapman.sys driver, it's not enough to simply delete snapman.sys. In fact if that's all you do then you're sure to experience blue screens. You have to un-register snapman.sys as both a service and a filter before you delete snapman.sys.

This is something that's always kind of bothered me. If you delete a driver's .sys file but leave its service key (under HKLM\System\CurrentControlSet\Services) intact, and if that driver's Start value is 0, the system will fail to boot (as you discovered) the next time you boot. Another issue that will cause boot failure is if you have a driver which fails to load and that driver is registered as an upper or lower filter on any of the devices in the storage stack. In the case of snapman.sys, this driver is an upper volume class filter driver, and may (although I'd have to double check this) be registered in the volume class UpperFilters value. So there are two reasons that you will fail to boot if you just delete snapman.sys. To manually uninstall such a driver, you have to remove its name from any REG_MULTI_SZ UpperFilters and LowerFilters values under the class keys in HKLM\System\CurrentControlSet\Control\Class. Look for the GUID that start with 7 - that the volume class GUID and it wouldn't surprise me if you find snapman in that GUID's UpperFilters value. Next, set the HKLM\System\CurrentControlSet\Services\snapman\Start REG_DWORD value to 4 (disabled) and then reboot. After reboot, that driver won't be loaded, and you can then safely delete the snapman.sys file as well as delete the HKLM\System\CurrentcontrolSet\Services\snapman registy key and all of its subkeys and values.

A nice user spelled out the keys under which UpperFilters values exist from which you must remove "snapman":

2. Navigate to HKLM\System\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}. Remove the snapman entry from the "UpperFilters" values.

3. Navigate to HKLM\System\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}. Remove the snapman entry from the "UpperFilters" values.

hello there,

I've got another situation in windows vista, causing a bluescreen. while I've been searching around for a resolution, I found this topic. maybe it has somethin with my problem in common.

 

look at following topic: http://www.wirtuell.net/post/bluescreen-in-windows-vista-when-executing-program-from-mapped-network-drive.aspx

I think the problem is the access of windows vista on the mapped network drive. Installation SP1 didn't help.

best regards

The only Blue Screen we are currently aware of is the Aronis Snapman interop issue as stated in this thread.  The post you have sited talks about running applications from mapped network drives.  I'm not sure how it relates. 

What application are you runnig from a mapped network drive?  Can you explain the context a bit more?  Acronis has never been installed on this computer, correct?

STC

as i posted above, it has something to do with starting an application with a mapped network drive - it doesn't matter which application!

it occurs on starting a .net application in the same way as another win 32 application.
 

This problem seems to have nothing to do with ShadowProtect Desktop. Perhaps you will get better answers from one of the many forums on other sites that specialize in questions about Vista.