Win7 unable to start after installing build 2160
So, finally I've been bitten by the program too:
System: Win7 64bit, DD 10.0 (I read the forum and know about the incompatibility _now_)
no multiboot features installed
Problem: After installing build 2160 the system is unable to boot anymore. After finishing, the Win7 startup repair function is unable to fix things. Even bootrec /FixMbr etc. (installed version or from Win7 DVD doesn't matter) don't do anything indicating any real progress. My system has this infamous hidden 100MB partition (but no active bitlocker), so it seems to be fully Win7 specific. At least, I was able to make a TrueImage 2010 backup from the broken system.
Question is, how to proceed? I have another backup for the 100MB partition, taken immediately after installing Win7 (2 months ago). Does it make sense to replace the current one with this backup? Am I able to boot the system than, perhaps? Afterwards, I could try to de-install the poor thing (new hassle to expect, I noted during reading the postings here).
I have to admit, I'm a bit worried now about the possibility that even the TI image isn't perfect and I have no way back after applying the restore function for the hidden partition.
Michael
Sigh... read my posting again. I simply would like nothing more, to get rid of the damn thing and have back an usable system. I simply didn't expect any problems by installing the program - particularly because I don't use any OSS features. My mistake, certainly. But I have to find out a way. So...
No need to read it again. What exactly did you expect?
> What exactly did you expect?
Software, not messing up my system?
BTW, I wasn't TOO careless - my first attempt was installation of a newer version of DD 10. And this version didn't told me about Win7 incompatibility, but was griping about (completely baseless) license issues. So I continued with the older 2160 version.
But I won't prefer a discussion, who has to be blamed here - I simply look for a solution out of this mess. Replacing the hidden partition isn't it, BTW. I would be interested in what the DD installer touches during his operation. This is quite specific, but maybe someone has the expertise to help me in fixing the system manually.
Michael
Michael:
I can't think of a reason why the DD installer would have produced this outcome. As far as I know it does not touch anything related to booting the PC unless you have also activated Acronis OS Selector.
Do you have only Windows 7 on your disk? How many partitions?
Going on the assumption that you have only the 100 MB Windows 7 boot partition and the Windows 7 partition itself (and perhaps a data partition or two), then I would proceed as follows. If you have good TI images then restore the following, in this order:
1. The 100 MB boot partition. Be sure to restore this partition as "Active".
2. The MBR and Track 0. This restoration takes only a few seconds and can be done as a second step.
Do both of the above while booted from your TI recovery CD. Then reboot the PC. Depending on which version of TI is in use and whether this is the first time you restored the disk with TI you MAY see a boot manager error message about a missing boot device. If you do, then use the Windows 7 automatic repair from the DVD.
@Mark:
I did as you said multiple times to no avail. My partition scheme is as simple as it could be: 100MB hidden and one additional partition for the remaining hard drive. I think there must be something fundamental on the main partition that has been changed. I mean, the boot problem appeared during the required reboot after installation of DD for the first time.
Attached the Win7 "Startup Repair" problem signature:
Problem event name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21200932
Problem Signature 05: AutoFailover
Problem Signature 06: 13
Problem Signature 07: CorruptFile
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
I'll do my own googling - particularly for PS 03-07 - but would like provide the only information I'm having so far. I'll also try some logged booting for the OS. I did so yet for "Safe Mode" etc., it did not change the outcome but at least it started and hopefully I can produce some more interesting information.
Michael
Michael:
If the problem is on the Windows 7 partition have you tried booting from the Win 7 DVD and rolling back to a restore point that preceded your installation of DD 10?
Alternatively, do you have an image of the partition that you could restore?
I'm a TI user for a long time. Consequently, Windows Restore Points are turned off :). The last image is a bit old (2 months), but it will do in the end. My efforts lead into nothing, so I will install this image, enhanced with the extracted data from the other one containing the (recent) broken state.
Michael:
At least you have a method to recover.
A big advantage of the newer operating systems (Windows 7 and Vista) is that Microsoft has provided the means to run System Restore from the repair CD; therefore I would never recommend turning off System Restore even if you're a TI user. With System Restore, restore points are created for you automatically whenever software is installed whereas with TI you have to be proactive and remember to create images before making changes that might create problems. Too bad, System Restore would have been an easy way out for solving this particular issue.
Wish I knew what went wrong with your installation of DD10; this is still a mystery.
Finally, the hard way solved the problem, I simply made some guesses from names I stumbled in again and again, browsing the net:
- start Knoppix or similar, perhaps the command prompt from Win7 Recovery would work too
- rename/remove snapman.sys & tdrpm251.sys
- restart Win7 (works now)
- deinstall DD (no problem)
- re-install/repair TI
Michael
edit: Mark, I always followed another philosophy - Windows Restore Points are never the whole picture, so its better to get that with TI or similar. Has to be done of course :-)
Michael
Michael:
The two files are the low-level snapshot managment driver and the Try and Decide driver from True Image 2010. I still don't understand how DD would have anything to do with them, other than they are both from Acronis. But I'm glad that you have things working again.
> I still don't understand how DD would have anything to do with them
I became suspicious, noting a "Last modified" time stamp for snapman.sys around the installation time of DD. Could it be, they are some common component, updated accidently from DD installation?
Anyway - thank you for the help!
Michael
DD uses the snapman.sys driver. It's part of the reason DD 10 had to be updated after Acronis made the driver changes in TI 2009 and TI 2010.
Hello Michael-DD10,ver 2160 is incompatible with ver 2160. You need DD 11 to install/run from the hard drive. However,you can use DD10,ver 2160 with Win 7 by booting to Acronis which means do not boot to Windows. You will get the options at the main option window. It might list DD 10 as an option. However, you will be able to perform all disk changes without encountering Win 7. I performed disk changes using this method throughout my miserable two year experience with vISTA hOME pREMIUM.
I have enormous problems with OSS and need help to get rid of it.
My PC consists of (i) CPU: Intel Core i5 760, (ii) Mainboard: Asus P7P55D-E, (iii) 4 GB DDR3 Corsair TW3X4G1333C9A, (iv) GPU: Asus ENGTX460 (1 GB GDDR5, 675 MHz, CUDA), (v) HD: 2x Western Digital Caviar Black, 1 TB, SATA3, (vi) Win7 (64) prof., and (vii) Acronis DD11 incl. OSS.
After its first installation OSS could not be restarted. Following the propositions of Acronis–Support I first de-installed OSS via “All-Programs” – “Acronis” – “DiskDirector” – “Acronis OS” – “de-install”. Then I de- and re-installed DD11 following special procedures proposed by Acronis and re-installed OSS in the usual way. Doing the latter was the beginning of a series of crashes, because after re-installing OSS, this program “could not be ended in a correct way” and “the Win7 Explorer stopped working correctly”. Using the various procedures proposed by Windows it is possible from time to time to boot Win7. Most time however the Restore Points or other tricks don’t work. Sometimes it happens that Win7 starts and seems stable, but always one or the other of the installed programs refuse to work and/or provoke a breakdown leaving behind them lots of error messages. Even re-installation of Win7 is impossible. And the worse: I cant get rid of OSS
Hello all!
Thank you for your comments and valuable help!
Enry, welcome to our Forum, we're glad to greet you here! I will be glad to help you.
In order to get rid of OS Selector, you can manually deactivate it. Please follow these instructions, and let us know in case you need any assistance, we will be glad to help!
Thank you!