Missing partition table, I keep creating an ISO file that won't boot

[kreemerz]

for some reason, everytime I create a new image (iso file), I can't get my desktop to boot from it. I've tested other drives with windows and no problem. But the one I created from NtLite just wont boot.

I've used Rufus and BalenaEtcher to create the USB file. But Balena says the iso is missing a patition table.

Any ideas?

 

[garlin]

Don't use balenaEtcher. While some users swear by it, their website quotes:

Can Etcher write Windows ISO?

Windows images are not bootable without extra treatment that etcher is not designed to do. If you need to make a bootable disk for windows you can find more information in our documentation.

That's why Rufus exists. You're probably using Rufus incorrectly.

NTLite's output is an ISO file, which is a disk volume which your USB program is supposed to write along with the proper boot loader, and other overhead. Check if you're mixing UEFI and legacy BIOS modes.

 

[Necrosaro]

Don't use balenaEtcher. While some users swear by it, their website quotes:


That's why Rufus exists. You're probably using Rufus incorrectly.

NTLite's output is an ISO file, which is a disk volume which your USB program is supposed to write along with the proper boot loader, and other overhead. Check if you're mixing UEFI and legacy BIOS modes.

Ever since I discovered Rufus I have used it religiously. Such a good program.

 

[nuhi]

To add to it, you can check bootability of an ISO in a virtual machine, if it boots, focus on the USB preparation steps.

However, the recent boot manager updates and secure boot locks complicate this matter, but probably not it in this case.
More info here.

 

[francis11]

I use Ventoy - most easy tool ever to handle iso drag and drop for booting.
On a big GB/ MB usb you can use a configurated json file on the usb to point for the iso folder on bootup for at fast start up process to get the job done.

 

[Necrosaro]

I use Ventoy - most easy tool ever to handle iso drag and drop for booting.
On a big GB/ MB usb you can use a configurated json file on the usb to point for the iso folder on bootup for at fast start up process to get the job done.

What just put the iso or whatever file that is supported and away you go. This is madness

 

[francis11]

Yep - already pointed out from a well respected member ages ago - aka Kasual - try search function.

 

[kreemerz]

So in Rufus, I selected MBR instead of GPT and it finally saw the USB drive.

So it goes through the installation process, I get 3 green checkmarks, downloads all files, installs, suddenly I get the message: Windows cannot update the computer's boot configuration. Installation cannot proceed.

Facepalm...

 

[kreemerz]

So in Rufus, I selected MBR instead of GPT and it finally saw the USB drive.

So it goes through the installation process, I get 3 green checkmarks, downloads all files, installs, suddenly I get the message: Windows cannot update the computer's boot configuration. Installation cannot proceed.

In my bios, the boot mode is set to UEFI secure boot ON.

Facepalm...

 

[garlin]

Confirm your Unattended disk layout matches the boot type (UEFI vs MBR). Then check if the install image is missing the required driver for your boot disk's controller.

 

[garlin]

Don't mix UEFI and GPT modes. You have SecureBoot enabled, which means Rufus should write in UEFI format, and NTLite uses UEFI layout.

 

[kreemerz]

Confirm your Unattended disk layout matches the boot type (UEFI vs MBR). Then check if the install image is missing the required driver for your boot disk's controller.

So is that under 'configure disk?' in the unattended section?

The screenshot shows my current setting.

Do I need to put a checkmark in the "copy to boot image"?

 

[garlin]

Disk layout is correct, don't touch the other checkboxes.

 

[Kennkish]

So is that under 'configure disk?' in the unattended section?

The screenshot shows my current setting.

Do I need to put a checkmark in the "copy to boot image"?

Did you get it to work? or else i maybe have the answer for you, and do not copy any files to nothing more then the main windows 10/11 home/pro whatever you are making.

 

[kreemerz]

Did you get it to work? or else i maybe have the answer for you, and do not copy any files to nothing more then the main windows 10/11 home/pro whatever you are making.

Did not. It's because I'm not sure what "disk layout" is refering to. I see "configure disk". But unsure if I need to change anything there. or leave as is. I've used the tool before and never had to change or mess with anything there. Maybe Rufus has something else I have configured incorrectly?

 

[kreemerz]

Yup. Still getting the same error. I've been trying different things all day now... not sure what has changed in rufus or ntlite.... where this is no longer working...

 

[garlin]

When making the ISO, you have the option to create an Unattended disk layout. If there isn't one defined, Setup will try to use the existing layout it finds on the install disk. This may be a problem if you're switching between UEFI and MBR modes.

To minimize the risk of Setup breaking, you should:
1. With licensed NTLite, enable a UEFI or MBR disk layout. This will wipe the existing install disk's partitioning and create a new one.

2. Without a license, boot a copy of the original ISO that doesn't have any unattended file. When Setup pauses, enter shift-F10 to open a CMD window and run diskpart to wipe the current layout.

diskpart
list disk
select disk 0

IMPORTANT: confirm this is the right disk!

clean
convert gpt  <-- Additional step if UEFI
exit

Quit the CMD window, now you can switch to booting a modified ISO.

Setup will create a default layout using the entire disk (minus the Recovery partition). If you don't want the Recovery partition, you can remove it later on the live system and reclaim the disk space. Or just use a specific Unattended layout with no Recovery assigned.

 

[kreemerz]

When making the ISO, you have the option to create an Unattended disk layout. If there isn't one defined, Setup will try to use the existing layout it finds on the install disk. This may be a problem if you're switching between UEFI and MBR modes.

To minimize the risk of Setup breaking, you should:
1. With licensed NTLite, enable a UEFI or MBR disk layout. This will wipe the existing install disk's partitioning and create a new one.

2. Without a license, boot a copy of the original ISO that doesn't have any unattended file. When Setup pauses, enter shift-F10 to open a CMD window and run diskpart to wipe the current layout.

diskpart
list disk
select disk 0

IMPORTANT: confirm this is the right disk!

clean
convert gpt  <-- Additional step if UEFI
exit

Quit the CMD window, now you can switch to booting a modified ISO.

Setup will create a default layout using the entire disk (minus the Recovery partition). If you don't want the Recovery partition, you can remove it later on the live system and reclaim the disk space. Or just use a specific Unattended layout with no Recovery assigned.

I have a licensed copy.

 

[kreemerz]

Looks like it succeeded.

 

[kreemerz]

Had no idea this section even existed. I must have overlooked it and dove into the other tweaks.