BSOD (snapman.sys) during install of build 11639 on Windows 7 (64 bit)
After an unsuccesful upgrade attempt of build 11345 (service refused to start due to logon error), I completely removed B&R before installing build 11639.
During the installation, Windows crashed with Blue Screen Of Death (mentioning "snapman.sys").
I am slowly beginning to lose my patience with this product. Is the Acronis QA team constantly understaffed?

- Log in to post comments

Thank you very much, Anton, for your assistance.
I uninstalled build 11345 using none of the methods you describe, but with the menu choice for uninstalling in the "Acronis Backup & Restore" folder in the Start menu. If that uninstall procedure told me to reboot, I did. If not, I probably didn't. I don't remember.
When trying the ABR10 clean-up utility, it first wrote "Disabling ASZ Shell Extension...Ok" then it crashed (a Windows popup said "Acronis Backup And Recovery Tool has stopped working"). Why am I not surprised?
Then I tried "abr_cleanup.exe --clean --keep-snapapi", but that also caused a crash.
I made both these attempts in a command prompt opened as Administrator.
I will now try the manual unistallation, as described by http://kb.acronis.com/sites/default/files/content/2009/07/2975/win_2008… (assuming it's the recommended procedure for Windows 7 as well). Please stay tuned...
- Log in to post comments

One hour later, after having uninstalled manually...
Once again, I tried to install build 11639 (yes: I did reboot). And once again, I got BSOD (mentioning snapman.sys) during installation. And even worse this time: I got the same BSOD shortly after boot, everytime I start the computer.
So I had to start Windows in safe mode, and change these three local services from Automatic to Manual startup:
- Acronis Managed Machine Service
- Acronis Remote Agent Service
- Acronis Scheduler2 Service
Are other 64 bit Windows 7 users not having the same problem?!
- Log in to post comments

The chat support guy sent me SnapAPI build 526, which is supposed to solve the BSOD problem. But since the installation of Backup & Recovery build 11639 (which contains build 523 of snapapi.dll) crashes before installation is complete, this doesn't solve the problem.
So please, Acronis, we urgently need a new build of Backup & Recovery, including SnapAPI build 526.
- Log in to post comments

Hello Karl,
Thank you very much for your reply.
As a workaroundб it is possible to install the latest version of our Snap Api drivers first, reboot and then install the program itself. This updates the drivers and the software uses the latest updated drivers when it is installed.
If this still fails, please ask the support engineer working on your case to get this case escalated to our Expert team. I am confident, that we will be able to resolve this issue.
Please let me know if you have any other questions or any other issues.
Thank you.
- Log in to post comments

Once again, I've manually un-installed ABR10 (http://kb.acronis.com/sites/default/files/content/2009/07/2975/win_2008…), and (after restarting Windows) re-installed SnapAPI build 526 (and verified in control panel: SnapAPI 3.8.526).
After restarting Windows I tried to run AcronisReport, which caused Blue Screen Of Death (mentioning snapman.sys). Also AcronisInfo caused BSOD (shortly after "xcopy" had been run). Needless to say, neither of these utilities produced a report file.
Then I made a *third* attempt to install ABR10 11639. And, a *third time* the installation caused BSOD (mentioning snapman.sys). This happened during installation of "Agent", shortly after "Removing duplicate files...".
FOOD FOR THOUGHT:
When starting Windows again, "Windows Startup Repair" told me that the "Root cause" for the crash was a corrupt file "e:\windows\system32\drivers\timntr.sys", and that the repair action failed. (This is an Acronis file, eh? hint hint nudge nudge). The next repair action, System Restore, completed succesfully.
So. I guess I should now open a formal support case? I'm not sure I will, though. My confidence is below zero, life is so short, and there are so many other backup products...
- Log in to post comments

Hello Karl,
Thank you very much for getting back to us and I really appreciate your patience.
The additional information you have provided is most helpful. It appears, that there is a conflict with our SnapApi drivers. More specifically, traces of the older version are conflicting with the newer one. I can suggest the following fix, and if it does not help, you have an open case already with us, we can get it escalated to our Expert team who will resolve the issue for you.
Please run the Acronis Backup and Recovery 10 Clean up utility. After that, to make sure that the clean up was successful, please check for Timounter and SnapApi traces in your system.
1. Removing Acronis Backup Archive Explorer (Timounter)
2. Removing Acronis SnapAPI Drivers
I am confident, that after performing the above steps, you will have no issues. Just in case, if you will continue to get BSODs, please generate a Windows Mini-Dump file and kindly send it to your existing support case. Ask for our support engineers to get it escalated to our Expert team and we will be able to resolve this for you. If you will experience any delays with your open case, please let me know and we shall take care of it.
Let me know if you have any other questions.
Thank you.
- Log in to post comments

Anton, thanks for caring!
I opened a support case yesterday after all, and to my surprise I got an answer within a few hours. Although your QA department seems understaffed/underqualified, your support seems to be in order (or have you pulled some strings?).
From support I got the same advice as from you: "Acronis Backup & Recovery 10 Clean Up Utility". Like earlier on, it crashed short after writing "Disabling ASZ Shell Extension...Ok" (a Windows popup said "Acronis Backup And Recovery Tool has stopped working").
However, despite the crash the utility had obviously done something good: When I tried to install build 11639, lo and behold, the installation worked fine. Almost: A pop-up window told me "Acronis Managed Machine Service has stopped working".
(The clean up utility does something that the instruction for manual uninstall http://kb.acronis.com/sites/default/files/content/2009/07/2975/win_2008… does not specify? In this case, please amend this document!)
After a reboot, everything seems to work fine and I could even validate my old backups.
- I find it surprising, to say the least, that your QA department has not discovered this "conflict with our SnapApi drivers". My desktop has no complex setup what so ever, just two internal SATA drives and a typical Windows 7 installation. Even more surprising is, that all the support tools I've used (ABR10 clean-up utility, AcronisReport, AcronisInfo) also crash or cause BSOD.
To me, it seems that Acronis urgently needs a new Release Engineer. Or a new software configuration management system. Or whatver...
All in all, I have now spent half almost a day with this seemingly simple update. I trusted the release notes that told me "it is recommended to install the update build without uninstalling the previous build.". During the next update, I will not be so naïve.
- Log in to post comments