Author: CUNFSTUCKER
Subject: VHD not start after disk2vhd
Posted: 04 January 2013 at 9:00pm
This seems to be a common problem and instead of just responding with a single line and link to a thread, let me summarize that others have said it is related to using Disk2VHD while the box is online and despite its reliability it seems impossible to account for all possibilities when it comes to locked directories.
Subject: VHD not start after disk2vhd
Posted: 04 January 2013 at 9:00pm
This seems to be a common problem and instead of just responding with a single line and link to a thread, let me summarize that others have said it is related to using Disk2VHD while the box is online and despite its reliability it seems impossible to account for all possibilities when it comes to locked directories.
In the past, I was having issues with an IBM inlcuded software (forget the name sorry, but it was 5 years ago and hopefully fixed) that was an altenrative to Windows System Restore and it was creating a tighttly locked direcotry at %systemdrive% that couldn't be accessed and was in some nether region since the GUI and XCAcls OR SUBINACL couldn't reset the perms and grant an Admin access to the direcotry.
Delete at boot wasn't working and I couldn't get access to it until I started a system shell with an AT job and accessed and deleted it that way but still had to take perms but could at least get access to takie ownership.
If you have the time to spare and care to experiment, are you prepared to rerun the disk2vhd while logged on as the local system account ? It could make a difference.
