Hi all, I have a big problem regarding Vista cloning on a new disk: the new diskl does not boot : I have the BSOD with 0x0000007B error ate the very first stage of Vista boot The procedure: I have a 320 Gbytes HD with Vista on primary partition and 4 other logical partitions. I wanted to change this on a new disk of 500 GB. So, for this I used the Acronis True Image cloning tool in automatic mode. (I used the 2009 version I just bought). So, Acronis performs all copies of the partitions from one disk to another, at boot time. When finished, I remove my old disk and put the new disk as primary disk (in fact I disconnect the SATA cable from the initlal disk and plugged the new disk SATA cable in the same connector as the initial drive, so this one becomed now the boot disk). At this time, windows either does not find the winload.exe program >> I use the Vista DVD to make a repair and after that, the 0.0000007B error comes, even after the repair. Or directly shows the 0x0000007B error. My copy of Vista is an EOM. I changed the processor, the memory, and added a new disk. I do not think this is related to this, as when I come back with my initial disk and keeping the new disk, all things return to normal and Vista boots without any problem Other thing, when I go back to the initial state with my intial disk as bootablez disk) (so in this state, the new disk and its content are seen as data), then sometimes all partitions are shown in this new disk and sometimes some are missing (for example, the primary partition is not shown for the moment) (for different tries of cloning, because, obviously, I tried several times with different scenarios for cloning). Might be this related to the content of the master boot record on the new disl (but this si also copied by Acronis...) So, for the moment I keep my initial disk, but still try to understand what is going wrong here). I checked the drivers of my new disk and they are up to date and also the serial ATA srivers of my motherboard (Asus P5W DH Deluxe). My new disk is new with no error. Processor and memory work well in initial state (old disk as boot , new disk as data). So, this is not a HW problem. Thanks for any help. I tried to find the root cause for 2 days full time now and did not find anything. WBR. Patrice.