Cannot boot in Windows after install ATIH 2009

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Beiträge: 7
Kommentare: 1

I was using ATIH11, then upgraded to ATIH2009.

After I upgrade the product, I cannot boot in Windows.

I booted from Windows , and try to start try&decide.
but I got the message “Failed to start try& decide”
(I recreated the Acronis Secure Zone, but it didn't help.)

I rebooted the machine, then press F11.
After “Starting Acronis Loader...”message,
I got the another message below:
“No commands for booting operating system. Press to reboot_”

this message showed up on and on, and all I can do was turn off the machine.

I installed the latest build of ATIH2009 after I uninstalled ATIH11 and delete Acronis secure zone.
Then,I created Acronis secure zone and reboot the machine, but
the result was the same as above.

I have created bootable media in ATIH11.
so I booted from it and restore my C drive,
finally I could boot in Windows.

I also disabled antivirus software temporarily , but it didn't help.
I reinstall ATIH2009 after I tried Acronis Cleanup Utility , but the issue still persists.

Finally I recoverd OS from Windows recovery CD.
I install ATIH2009 after I ran Acronis Cleanup Utility,
but I still couldn't boot in windows.

I'm using Windows Vista (SP2)
C;70 G
D;14 G (I tried to create Acronis Secure Zone in D;)
E;80 G

Is there anything that I can try to resolve this issue?

Do, 11/05/2009 - 03:37
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Frequent Poster
Beiträge: 4
Kommentare: 942

Hello Carrie,

I understand the issue and will do everything possible from my side to solve it. The source of the is corrupted BCD (Boot Configuration Data) which is responsible for boot process.

The possible reason for the issue is that you haven’t deactivated ASRM (Acronis Startup Recovery Manager) before deleting Acronis Secure Zone which is critical for activating ASRM. In order to deactivate ASRM go to Tools -> Acronis Startup Recovery Manager -> Deactivate or as an alternative you can Restore Windows Boot Loader.

Also please note that Acronis Startup Recovery Manager is independent from Acronis Secure Zone in Acronis True Image Home 2009 Build 9788 or higher. You can download the latest build of Acronis True Image Home 2009 from your account under Registered Products.

In order to solve the issue please do the following:

Boot from Windows Vista installation disc, select language and keyboard or input method, click Next and choose to Repair your computer. Then you will need to select the operating system that you want to repair. In the System Recovery Options dialog box click Command Prompt and type the following:

Bootrec.exe /FixMbr
Bootrec.exe /FixBoot

If you want to completely rebuild Windows Vista Boot Configuration Data, then you should issue the following command:

Bootrec.exe /RebuildBcd

This command scans all disks for installations that are compatible with Windows Vista. Additionally, this option also allows select the installations that you want to add to the Boot Configuration Data store.

Further information is available here 

Concerning the issue with Try & Decide please make sure that Acronis Try&Decide Service (Control Panel -> Administrative Tools -> Services) Startup type is set to Automatic in Properties.

Let me know if the issues persists.

Thank You.

Sa, 11/28/2009 - 10:03
  • Anmelden, um Kommentare verfassen zu können
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Regular Poster
Beiträge: 5
Kommentare: 123

I will throw in a comment related to Startup Recovery Manager and Spyware Doctor. Spyware Doctor (a PCTools anti-malware app) installs a very low level disk access driver just as Acronis does. If you use Spyware Doctor, do not enable Startup Recovery Manager since the two low level disk access drivers will conflict with one another if you try to use Startup Recovery Manager to restore your hard disk. Another option is to permanently disable Spyware Doctor by right-clicking on its system tray icon before rebooting in order to use the Startup Recovery Manager feature to restore your hard drive, reboot so that Spyware Doctor can fully disable its drivers during this reboot, and then reboot again into Startup Recovery Manager in order to do a restore. Another alternative option is to boot with the Acronis Recovery CD in order to do a restore. This will completely bypass any issues with Spyware Doctor since this method doesn't require disabling Spyware Doctor at all. It is possible that similar issues may occur for other types of anti-virus and anti-malware programs and that the above solutions (especially the last one) should work.

Note that this issue apparently doesn't reflect any sort of design flaw with either product. Its just an issue of their low level disk access drivers having to "fight it out" since both drivers hook into the OS for disk access at the lowest possible level.

Sa, 11/28/2009 - 16:07
  • Anmelden, um Kommentare verfassen zu können
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Regular Poster
Beiträge: 5
Kommentare: 123

I should have asked Carrie...

Carrie, what anti-virus and/or anti-malware software do you have installed on your computer?

Sa, 11/28/2009 - 16:27
  • Anmelden, um Kommentare verfassen zu können