Status: 0xc0000428 at boot After deploymnet

Question

Hi,
I have a WES7 reference device created with ICE.
Tried to deploy it to another machine but with out success.
The reference device has 3 partitions
1. 100mb reserved partition create by the IBW
2. partition as drive c
3. partition as drive d
I used imagex to create wim files from c and d only and created only the c and d on the target.
After reboot it shows The status: 0xc0000428
How should I clone such 3 partition disk to a target device?
Thanks,
Avi Wertheimer

Answer 1

Hi Sean,
Thanks for your reply. and surly will learn this solution.
Meanwhile, I would like to share with the public my last days experience.
It started with a customer request for WES7 image creation service.
I used my ICE and created a pretty standard image with size of about 3-4 gb.
The customer asked for solution of disabling most of the key combinations, so I looked for the Keyboard Filter solution.
It written in MSDN, that Keyboard Filter present in WES7 Since SP1, which appears to be inaccurate, as I have ICE installed from WES7 SP1 disk.
So, I installed the WEDU and updated the DS and the ICE.
Now the keyboard Filter appeared In the DS tree.
Next I added the Keyboard Filter and, innocently,  I ran "Add Applicable updates" (it increased the size of the image by additional 6gb, so I recreated a new answer file but this time without "Add Applicable updates", just used the
Keyboard Filter)
I created IBW from answer file and installed the OS.
at the disk management window of the IBW, I erased all partitions and created C=20gb, D=the rest of available space.
the IBW added automatically 100mb "System reserved partition" and OS installation ran in to successful completion.
Next, I created WinPE bootable Disk, with cloning command as follows:
capture.bat contains:
               imagex /capture c: e:\image_C.wim "Drive C" /verify /compress maximum
               imagex /capture d: e:\image_D.wim "Drive C" /verify /compress maximum
Note: e: is the Disk On Key (DOK)
Next, I replace the hard disk with a new one and created few batch files.
PrepDisk.bat contains:
                     Diskpart /s disport.txt
                       wpeutil reboot
Diskpart.txt contains
select disk 0
clean
create partition primary size=20000
active
format fs=ntfs quick
assign
create partition primary
format fs=ntfs quick
assign
exit
Last file name is deploy.bat contains the following:
\imagex /apply e:\image_C.wim 1 c:
\imagex /apply e:\image_D.wim 1 d:
bcdboot.exe c:\windows /s c:
bcdedit /set {default} device partition=c:
bcdedit /set {default} osdevice partition=c:
bcdedit /set {bootmgr} device partition=c:
bcdedit /set {default} bootstatuspolicy ignoreallfailures
bcdedit /timeout 3
wpeutil reboot
At this point I ran cleandisk.bat
After the reboot I ran deploy.bat
Now: After second reboot (and removal of DOK), I expected to get the new cloned disk to boot up with the cloned OS, but instead, the result was error screen with the message: Status: 0xc0000428.
After I verified that this is not a random error, or bad DOK or and other hardware ( I used several new DOKs and several target devices and several hard disks), I start to think, what I am doing wrong.
One idea was, maybe I must to do Sysprep/Generelize/shutwon - didn't solved the problem
Next, I created a whole new answer file and removed the bitlocker package and created 2 partitions C, D (without "System Reserved Partition)
I captured and deployed the image again - didn't Solved the problem.
I draw the line above, no notify that I found some interesting thing:
I diskpart/cleaned and recreated 20gb sized partition on disk, leaving the rest, unpartitioned.
I ran imagex /deploy... and bcdboot c:\windows /s c: and reboot after completion and to my surprise, the New OS booted.
Note: the image wasn't syspreped, but still everything works fine.
Must say, excluding a situation where a new SID is required, I didn't find any justification to ran Sysprep (it causes a long first time boot period, extending dramatically the cloning time which is a big con, when many cloning has to be made from time
to time)
at this point, I AM WONDERING, why, the automated process, failed and the manually creation of the only C and deploying the image was successfully accomplished (WITH THE SAME WIM FILE.)
As I am still searching for a solution, I will continue to try figure out the cause and solution, and hope to update here in next days.
Avi Wertheimer