20

My Windows Server 2008 R2 won't start and stops with Stop 7B, so I start the recovery console and use diskpart to check the disk. There are to partitions one of Type 17 and one of type 07, the detail disk command show me that the disk is not a boot disk. How can I set this boot flag with diskpart? Or is this flag only set true if the MBR works fine. I try following commands:

bootsect /nt60 ALL /force /mbr
bootrec /fixboot
bootrec /fixmbr
bootrec /rebuildbcd

the last command show me the number of OS is 0, so how can I set this flag to true?

Here is the output of diskpart detail disk: enter image description here

Improve this question
4
  • you should detail how you fixed it, so that others can benefit. And if you can't remember then you should have detailed how you fixed it so that others could benefit
    – barlop
    Commented Dec 20, 2015 at 1:37
  • 2
    As I mentioned in the Comments of your answer it was a issue with the driver signature. After deactivate the signature verification while startup I can start the system reinstall the driver and everything works well. So the solution was to recreate the MBR and start without driver verification.
    – kockiren
    Commented Dec 20, 2015 at 5:26
  • 1
    To clarify: Bugcheck 0x7b (INACCESSIBLE_BOOT_DEVICE) means that Windows did indeed begin booting, but was unable to find a driver for accessing its partition after switching to direct storage access.
    – Daniel B
    Commented Dec 30, 2015 at 11:55
  • Note: As I understand it, "Boot disk" in diskpart only means that this is the disk from which the Windows has booted. Not that the disk is bootable from the BIOS. In addition, use "list volumes" to see which is the "System" volume, which contains the Windows OS currently running. (These might be in different disks.)
    – Shalom Craimer
    Commented Oct 19, 2022 at 6:33

6 Answers 6

Reset to default
9

The diskpart in recovery console doesn't allow you to make a partition active(bootable).

Use Gparted Live.

http://en.wikipedia.org/wiki/Diskpart "On the Recovery Console, which is included in all Windows 2000, Windows XP and Windows Server 2003, there is a diskpart command which is significantly different from the one included in the actual operating system. It only provides functionality for adding and deleting partitions, but not for setting an active partition. The utility is also provided in the Windows Recovery Environment, the successor of the original Recovery Console"

Improve this answer
9
  • I boot from a live-Linux and start gparted. The Bootflag is set but the detail disk show me "boot disk" no
    – kockiren
    Commented May 18, 2013 at 11:14
  • 1
    @kockiren there are some more commands you can try social.technet.microsoft.com/Forums/en-US/winserversetup/thread/… like sfc (with some parameters like sfc /SCANNOW /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows where d is your windows drive) and startrep.exe and if both those fail then you might have to reinstall windows. As windows server 2008 apparently has no repair installation w7 has no repair installation either! xp does.
    – barlop
    Commented May 18, 2013 at 11:47
  • 1
    also if you just made it active/bootable when it those commands can't see windows, then you're not likely to be able to even start getting into windows. if you can reach a stage where those commands can see windows, particularly the rebuildbcd command which found 0 Oss, if running those other commands leads it to find the Os then great, if not, then maybe that's a basic problem that leads diskpart to not see that it's bootable when gparted set it to bootable.
    – barlop
    Commented May 18, 2013 at 11:51
  • I run sfc and startrep but it dosent help. No bootrec /rebuild find a Installation but the System won't start correctly. It stops with 7B and now Dumpfile was create :-(
    – kockiren
    Commented May 18, 2013 at 12:00
  • 1
    I didnt need a fresh install, Windows won't start with Drivererrors, after I fix it windows start correctly and then the Boot Disk flag is set.
    – kockiren
    Commented May 18, 2013 at 18:54
8

I have successfully restored an VHD GPT-disk from a Windows 8.1 PC combining information from this and other threads on another windows 8.1 Hyper-V-Server.

My steps:

  1. Rip the disk using Disk2vhd from Microsoft Sysinternals.
  2. Mount the vhd in the file system of the Hyper-v-host. (i.e dubble click the vhd).
  3. Download and install AOMEI Partition Assistant.
  4. Start AOMEI Partition Assistant and select the VHD-disk which appear as an ordinary disk. Mark the disk av select to convert disk to MBR-disk from the Disk-menu.
  5. Remove all partitions that contains recovery disks and other non Windows partitions.
  6. Detach VHD from HOST (Restart may be necessary).
  7. Create a new Virtual Machine in Hyper-V Manager and use your modified VHD.
  8. Boot VM from Windows Installation disk an go to recovery console and select command prompt.
  9. Use diskpart as described below:
    • DISKPART (to open the partition utility),
    • LIST DISK (disk number(s) will be shown),
    • SELECT DISK n (where n is the number of the disk - probably 0),
    • LIST PARTITION (partition number(s) will be shown),
    • SELECT PARTITION n (where n is the number of the Primary partition you wish to make Active),
    • ACTIVE (the selected partition on the selected disk will be made Active),
    • EXIT (to exit DiskPart),
    • EXIT (to exit the Command Prompt),
    • Restart computer.
  10. Repeat step 8. 11.Rebuild MBR, as described bellow, ie:
    • bootrec /fixboot,
    • bootrec /fixmbr,
    • bootrec /rebuildbcd.
  11. Exit command prompt.
  12. Use Recovery options to restore windows system files (Both partial recovery and advanced recovery options may me used).
  13. Repeat 13 until VM boots from your VHD.
Improve this answer
2
  • 1
    Thank you for an answer, but please review "Mark the disk av" and try to provide better quality answer next time.
    – g2mk
    Commented Dec 30, 2015 at 12:26
  • 1
    What does "13. Repeat 13 until VM boots from your VHD" mean? Evidently there is a problem with the step numbers, but I can't tell what step must actually be meant.
    – Reg Edit
    Commented Feb 6, 2021 at 18:43
2

DISKPART (to open the partition utility)

LIST DISK (disk number(s) will be shown)

SELECT DISK n (where n is the number of the disk - probably 0)

LIST PARTITION (partition number(s) will be shown)

SELECT PARTITION n (where n is the number of the Primary partition you wish to make Active)

ACTIVE (the selected partition on the selected disk will be made Active)

EXIT (to exit DiskPart)

EXIT (to exit the Command Prompt)

Restart computer.

Improve this answer
2
  • 7
    The the Partition is marked as active but not as Boot Disk. There is a flag called "Boot Disk" and has value no but in well working systems this flag is always set to yes.
    – kockiren
    Commented May 18, 2013 at 5:30
  • add a screenshot for detail partition, that would say active or not.
    – barlop
    Commented May 18, 2013 at 12:00
1

I realize that this is an old thread, however . . .

Steps 9 and 10 above by g2mk worked for me when I needed to slide a Win81 partition to the unallocated space at the front of the drive, because . . .

I originally had XP in partition0, then I installed Win81 (aka Dual Boot) and it installed Win81 to partition1. Btw, there's a procedure to remove the old Microsoft partition0 OS elsewhere on the web (says for Win7)(btw,you can use gparted to set Win81 as Boot, which equals Active via Diskpart). Then I used Gparted to slide the Win81 partition over the unallocated space. Then I needed to use Steps 9 and 10 above to get rid of 0xc000025 on winload.exe and be able to boot into Win81 on the HDD.

Btw, unless I'm missing something, everyone should note that as written, these procedures are for Windows installed on a MBR disk (ie. not for Windows installed onto a GPT disk on UEFI hardware).

HTH

Regards . . .

Improve this answer
2
  • Welcome to Super User! On this Q&A site we try to provide good answers to questions people post. Part of a good answer is including all the steps required to making your answer work. Referencing to someone else's answer by saying 'above' isn't enough because the order of answers on Stack Overflow is not fixed. Please include the steps you are referring to in your own post. Providing credit by linking to the answer you're referring to is never a problem, of course!
    – Cas
    Commented Oct 10, 2016 at 13:43
  • This bit of your answer is why I upvoted it: "everyone should note that as written, these procedures are for Windows installed on a MBR disk (ie. not for Windows installed onto a GPT disk on UEFI hardware)." Indeed, even the answer mentioning "VHD GPT-disk" first converts VHD to MBR as there is no way that DISKPART will let you make any partition "Active" on a GPT-disk. When you have a GPT disk, follow the steps in superuser.com/a/1444266/14061 by @Nathan2055
    – Jeroen Wiert Pluimers
    Commented Dec 29, 2022 at 18:09
1

While attempting to load Windows Server 2003 on a new drive of my Windows 7 machine, I somehow wiped out the boot on the Windows 7 drive.

Windows could not start because of a computer disk hardware configuration problem

After three days of poking around, I was able to use the following steps to correct the issue:

  1. Boot from Windows 7 Install Disk
  2. Select "Repair" Option
  3. Select "Startup Repair" (this will run but not find any issues)
  4. Select Advanced Options to get to "Command Prompt"
  5. bootsect /nt60 SYS
  6. Restart the computer normally
Improve this answer
1
  • This is an answer to a different question ...
    – DavidPostill ♦
    Commented Nov 19, 2016 at 11:05
0

The only solution for me was to write the Minitool Partition Wizard BootCD (or Gparted) to USB using MultiBootUSB(or YUMI) utility.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .