Windows Server PXE over IPV4 unfortunatly...

[jcpamart]

Hi,

I have made a vhdx file from my secretary computer.
But I can't start it without PXE over IPV4.

I'had try all the solution I found on google and AI, but nothing done.

Any idea to help me ?

Thanks for your help
Best regards

 

[ChatGPT]

Hi and welcome!
It sounds like you have a VHDX (virtual hard disk) from your secretary’s computer, but when attempting to start (perhaps using Hyper-V or another virtual environment), it only tries to boot via PXE over IPv4/network, and doesn’t boot the system from the VHDX as you’d expect.
This issue usually means the VM is not seeing a bootable drive. Here are the most common causes and solutions:

---

1. Check Boot Order / Boot Device​

• In your VM settings (e.g., Hyper-V Manager), make sure the VHDX is attached as the primary hard drive, and that the boot order prioritizes the hard drive (sometimes labeled IDE or SCSI, depending on how it’s attached) before any network (PXE) devices.
• If the VM can’t find a bootable disk, it falls back to network boot, which is why you see the PXE message.

How to fix:

• Shut down the VM.
• Go to your VM settings → “Firmware” (in Hyper-V) or equivalent in other managers.
• Move the Hard Drive to the top of the boot order.

2. Check VHDX Attachment​

• Confirm the VHDX is correctly attached to the VM and mapped as the correct type (IDE or SCSI, depending on the OS and VM type/generation).
• Hyper-V Generation 1 VMs must have a boot drive on an IDE controller. Generation 2 VMs use SCSI and UEFI.

3. VHDX Content: Is It Bootable?​

If the VHDX was simply created by copying files, or if system files are missing or corrupted, it may not be bootable.

• Did you use a tool to “capture”/“export” the disk, or just copy user data?
• If the VHDX is from a running Windows installation (disk-imaged), it should contain the system partition and be marked as active/bootable.

4. Repair Boot Files (If Needed)​

If the above is correct but it still won’t boot, you may need to repair the boot files:

• Mount the VHDX to another Windows system (as a secondary drive).
• Use Command Prompt with admin privileges:
  

  bootrec /fixmbr
  bootrec /fixboot
  bootrec /rebuildbcd

• Make sure the system partition is marked as “Active”.

5. Other Issues​

• If you’re converting from a physical machine to VHDX (P2V), driver or partition mismatches can also cause boot issues.
• Try using Microsoft’s “Disk2vhd” or a similar tool for Windows P2V conversions.

---

Final thoughts:
PXE boot appears because the VM doesn’t see a bootable disk. Double-check the VHDX attachment, boot order, and whether the image is actually bootable. If needed, repair the boot sector.
If you give more details (Hyper-V or another VM solution, how you created the VHDX, error screenshots, etc.), I can give much more specific help.
Let me know how it goes, or provide the extra details if you need step-by-step guidance!

 

[datawizard0103]

Your VHDX won’t start because the VM is trying to boot from the network instead of the disk. Check the VM’s boot order and make sure the VHDX is set to boot first. Also, make sure the VHDX has a working system inside. If it came from a physical PC, it might need fixing to boot as a virtual disk.

 

[ChatGPT]

You're correct: if your Hyper-V VM is attempting to boot from the network (PXE) instead of your VHDX, it’s likely due to an incorrect boot order—or the VHDX itself isn’t properly set up as a bootable disk.
Here’s how to fix and further diagnose:

1. Check VM Boot Order:
   • In Hyper-V Manager, shut down your VM.
   • Right-click the VM > Settings > Firmware (or BIOS for Gen 1 VMs).
   • Make sure the VHDX (IDE Controller or SCSI Controller) is listed as the first boot device—not “Network Adapter.”
2. Verify VHDX Has a Bootable OS:
   • Mount the VHDX on another Windows system (right-click > Mount, or use Disk Management).
   • Check that it contains a valid Windows installation (usually \Windows folder, boot files, etc).
   • If you recently converted a physical PC to VHDX, you may need to run Startup Repair from a Windows ISO inside the VM to fix bootloader issues (especially if there’s a blue or black screen, or “No boot device” error).
3. If Still Not Booting:
   • Attach the Windows ISO as a DVD in Hyper-V.
   • Boot from the ISO, and select Repair your computer > Troubleshoot > Startup Repair.
   • This often fixes BCD (boot config) issues after physical-to-virtual (P2V) migration.
4. Compatibility:
   • If the VHDX was created from a physical disk that used legacy BIOS, but you set up a Generation 2 VM (which expects UEFI), it won’t boot.
     • Solution: Match the VM generation to the original PC’s boot mode (Gen 1 for BIOS/MBR, Gen 2 for UEFI/GPT).

If you’re stuck, let me know your VM’s generation and where the VHDX came from (P2V, another VM, etc.), and I can give more targeted guidance. If you want, I can also analyze the files you’ve uploaded for further context!