Acronis Disk Director 11 Blows up Boot.ini
I just purchased Acronis disk director today. i made a boot media/recovery media. i booted from it and used it to resize 2 partitions on the disk.
The result was a failure to boot after this process. Through troubleshooting and testing on multiple machines to confirm it is a product deficiency and not a hardware issue I have determined the problem.
Acronis Disk Director changed the partition ID in the boot.ini file from a (1) to a (0). Launching the recovery console and performing a bootcfg /rebuild was needed to fix this. Once I got the OS to boot I manually edited and corrected the boot.ini file.
1. To confirm this deficiency I tested it on another machine. I looked at the boot.ini and verified that the tag for the OS partition was (1). The drive has 2 partitions.
2. I launched disk director from the recovery media and resized both partitions.
3. Attempted to boot back into the OS – MAJOR FAIL. NTOSKRNL.EXE not found.. NICE!
4. Performed a bootcfg /rebuild from the recovery console and added the found installation to the boot.ini
5. Rebooted – success
6. Edited and (corrected boot.ini)
During the above steps I DID NOT change the active partitions nor did I change partition types. I simply took unallocated space on the drive and allocated it to both C: and D:
So why does Acronis Disk Director 11 blow up the boot.ini when resizing partitions from the recovery media?
Please fix this major deficiency in your product. I’m sure this is causing major problems for folks less knowledgeable then myself who are likely reinstalling their operating systems to fix this issue.

- Log in to post comments

Was OSS installed and activated?
DD11 itself doesn't touch boot.ini, though if Windows reboots then the BCD or registry could alter the contents of various files if it tries to use default settings. That is when I've tested it.
What OS are you using?
- Log in to post comments