• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Sign in to follow this  
Followers 0
Mandar K

Win2003 client fails to boot restored using WinPe 2.0

5 posts in this topic


I am trying to restore Win2003 client from its full backup where its system volume (c:) is of type "dynamic".

After w2k3 client restore, during first boot windows splash screen appears and in a moment blue screen gets displayed with below error message. I am wondering what is going wrong here.


A problem has been detected and windows has been shut down to prevent damage to your computer.

If this is the first time you've seen this stop error screen, restart your computer. If this screen apprears again, follow these steps:

Check for viruses on your computer. Remove any newly installed hard drive controllers. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your computer.

Technical indormation:

*** STOP: 0x0000007B (0xF884AA98, 0XC0000034, 0X00000000, 0X00000000)


Below high level steps are carried out in WinPe 2.0 for this client restore. The similar stuff works well using WinPe 1.6. Also client restore and boot works using WinPe 2.0 but only if system drive is on "basic partition".


1. Booted into WinPe 2.0

2. Used diskpart tool and followed below steps.

- Clean disk

- Manually wrote MBR (512 bytes) on the disk at offset 0.

- Converted disk into dynamic

- Created simple volume using command “create volume simple align=0”. [ I observed that if align=0 is not used then volume to partition association does not work and need to run diskpart command retain explicitly. But in this case it creates some extra partitions (extended containing 3 logical and one of them is associated with the C: volume). ]

- Formatted this volume with NTFS.

- Below are diskpart details after creating dynamic volume and formatted for NTFS. (Please note that the other hard disk of size 112 GB is unformatted.)

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt

-------- ---------- ------- ------- --- ---

Disk 0 Online 112 GB 112 GB

Disk 1 Online 37 GB 512 B *

Disk 2 Online 3830 MB 0 B

DISKPART> select disk 1

Disk 1 is now the selected disk.

DISKPART> list volume

Volume ### Ltr Label Fs Type Size Status Info

---------- --- ----------- ----- ---------- ------- --------- --------

Volume 0 C OS_VOL NTFS Simple 37 GB Healthy

Volume 1 D CD-ROM 0 B No Media

Volume 2 E FAT32 Removable 3830 MB Healthy

DISKPART> select volume 0

Volume 0 is the selected volume.

DISKPART> detail volume

Disk ### Status Size Free Dyn Gpt

-------- ---------- ------- ------- --- ---

* Disk 1 Online 37 GB 512 B *

Read-only : No

Hidden : No

No Default Drive Letter: No

Shadow Copy : No

Dismounted : No

BitLocker Encrypted : No

Volume Capacity : 37 GB

Volume Free Space : 37 GB

DISKPART> list partition

Partition ### Type Size Offset

------------- ---------------- ------- -------

Partition 1 Dynamic Data 37 GB 32 KB

DISKPART> select partition 1

Partition 1 is now the selected partition.

DISKPART> detail partition

Partition 1

Type : 42

Hidden: Yes

Active: No

Volume ### Ltr Label Fs Type Size Status Info

---------- --- ----------- ----- ---------- ------- --------- --------

* Volume 0 C OS_VOL NTFS Simple 37 GB Healthy

3. Changed MBR to set the partition active. For this I changed 1BE byte of MBR as 80. [ Otherwise the partition will not be set as active and MBR boot code does not find operating system during boot. ]

4. Restored whole client data from the backup to this C: drive of type dynamic volume. For this I am using a backup-restore sw.

5. Done required registry changes in the restored registry system hive by referring current system hive in WinPe 2.0 environment. These changes are related to volume GUIDs and mounted devices.

6. Rebooted the system for first boot and observed the mentioned error.

I am wondering if I am missing some step over here or W2k3 LDM will not be able to understand volumes created using VDS based diskpart. But again if I boot using WinPe 1.6, I can see volumes and partitions details using LDM based diskpart. So why it is going bad during booting step?

Any help is much appreciated.




Share this post

Link to post
Share on other sites

0x7B means that the mass storage driver in the image is unable to initialize the hard drives that it is booting off of. Make sure that you are deploying onto the same hard drive controller and same settings like RAID or AHCI, etc.


Share this post

Link to post
Share on other sites
- Manually wrote MBR (512 bytes) on the disk at offset 0.

Did you clone disk signature in the MBR? :unsure:

0x0000007b means "inaccessible boot device", generally due to a missing mass storage driver, but not only, it could be also the MBR or the bootsector:


The NT/2K/XP/2003 relies on disk signature in the MBR to identify drives/partitions, including the boot one.

See here for reference:



A tool you might find useful:




Optional pseudo_GUI for it:



Edited by jaclaz

Share this post

Link to post
Share on other sites

Thanks friends for your replies on this problem.

The issue has been resolved.

The problem was after restoring original client data in WinPe 2.0 environment i was not modifying disk group details under SERVICES/dmio/ key of original clients system registry hive. It was still pointing to original dg name and GUID. I updated these disk group details with new DG GUID and DG name that I created in winpe 2.0 environment.

Rebooted the client and first boot worked successfully.




Share this post

Link to post
Share on other sites

My first question was if my reply or the reply with the links helped you at all.

I have not attempted to use 2003 with WinPE yet but I doubt i will get that chance. I have not yet had the opportunity to streamline our server deployments, and time constraints make me think this is far off for me. Rest assured, I will try to remember this issue in case I get this chance.


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.