Target Machine Will Not Boot. Repair Does Not Work. MBR 1,2 or 3 Error. SD5 Changed Target from MBR to GPT.
My HP 6305 SFF Desktop will not boot after deploying the image. The master image was created on the same hardware model. I have tried with and without Universal deploy.
It is UEFI but the Secure Boot option is turned off. It is set to EFI, not Legacy EFI and not AHCI.
I am getting an MBR error. When I booted into PE from a USB and performed diskpart, there is a disk 0 listed and the partitions seem ok in size. Trying a Repair with a Windows 7 disk fails. Keeps telling me it is not correct, even though I have tried both 32 and 64 bit disks. I can't even get to the command prompt to attempt a fixmbr.
At one point I saw that my disk was listed as GPT. The master image machine is MBR. I verified. So I was able to use diskpart to format the disk as MBR and then attempted deploying the image again. Still would not boot.
What is happening? I've successfully deployed images before on the HP 6305. I did have a prior case where deploying an image to a 6305 that was captured from that very same computer did not work unitl I was asked to use Universal Deploy. (Which makes zero sense when it was the exact machine the image came from).
Tech support has been no help on the phone twice now.
On HP modern machines you SHOULD mdify BIOS and disable UEFI boot - than it will boot in LEGACY mode.
If the image you dploy is MBR and you boot with a CD in UEFI mode I think you will gat an automatic change to UEFI for the target.
This is somehow connected with installing Windows on a clean target from a CD : if the BIOS is UEFI you will get a GPT install of Windows - else it will bge MBR.
MMH,
You say that the system is UEFI, but the master image is MBR and that you formatted the drive as MBR already.
However, when you boot to your offline bootable recovery media you need to make sure you are booting it in the same mode as your original image was created from (legacy MBR or UEFI GPT) as well. IF you have an MBR Legacy image, but start your recovery media in UEFI mode, it will try to format the drives in UEFI before deploying the image. This is the same behavior as Windows installers use too.
In this case, you may need to also ensure that your new system has CSM/Legacy mode enabled and that you are selecting the bootable recovery media to boot in legacy mode first (often this is easier using the system one time boot menu/boot override menu and ensuring the legacy boot option is selected and not the UEFI one in this case).
I would also think that since you are deploying an MBR image, it should be "Legacy EFI" and not just EFI as you have selected. I'm not familiar with HP bios though so can't be sure. On a Dell, an MBR image should be deployed to Legacy/CSM/Bios builds and a UEFI image should be deployed to UEFI/GPT builds.
Then, hopefully your image deployment will be successful.
While creating bootable media for non-UEFI devices in ASD5, an available bootable iso file is created in Legacy ASD5. Legacy cannot be selected while printing the prepared iso file with rufus etc. programs. How can I do this in ASD5?
(01). MVP WinPE Builder (02). MVP LogViewer
(03). MVP Google Drive (04). Cleanup Utility
(05). Cloning Correctly (06). Clone vs Backup
(07). Community Tools (08). Contact Support
(09). Product Documentation (10). OS MBR vs UEFI
(11). BOOT MBR vs UEFI (12). Common OEM Drivers