Rufus: "Couldn't find a bootable operating system"

Rabbit_Games

Rabbit_Games

New Member
Full disclosure: I'm completely new to NTLite.

Step 1: I used the Media Creation Tool to make the Windows 11 ISO.
Step 2: I used RUFUS to burn the image to a USB.
Step 3: Used the USB to install Win11 on a different computer and it worked just fine.
Step 4: I grabbed the latest download for NTLite, pointed it to the same ISO I made in Step 1.
Step 5: I used NTLite to create a new ISO following the guides listed here and loaded it onto a USB with RUFUS just like in Step 2. (Including Chris' in-depth one.) I've also tried just letting NTLite create a new ISO without having made ANY changes whatsoever. Basically, I just loaded the ISO and immediately went to Apply and let NTLite create the new ISO.

Each time I try to install the ISO that NTLite creates I get the error in the subject line.
I feel like I'm missing something if even without making and changes, the ISO created by NTLite isn't creating "a bootable operating system". I'll see if I can grab an older version of NTLite and see if it makes any difference.
 
Last edited:
Nope. I've tried RUFUS, Ventoy, and Yumi.
Like I said, any of those tools will load the official ISO onto a USB drive and I can install Win11 from it just fine. Once I open the Official ISO with NTLite, get the green light next to Pro, and then go to Apply to create a new ISO (immediately, without making any changes) and use the same tool (RUFUS, etc.) to load it onto a USB drive, I never get past the Error I posted after trying to boot from that USB. <Shrug>

The only older version of NTLite I've found is from 2022. I might give that a shot when I get back from lunch and see if it makes a difference.
 
There's no image source listed. Is this the correct preset? Otherwise NTLite hasn't done anything at all.

Normally, you load an ISO or extracted image folder and do some work. Then ask NTLite to create an ISO from the working folder.
NTLite extracts that source to a working folder, but you can't write the same folder back to USB. It must be a new ISO file.
 
Check the root of your untouched/orihginal iso and new image file+folder structure and sources folder, see if any setup files and wim files are missing.
 
I just don't get it. I went through (again) and made all the changes I want to make (file included) and click Process. I can't imagine what I'm not doing that requires doing. I do notice that in RUFUS with the unedited ISO from Microsoft it creates a Fat32 partition. With the NTLite ISO the only option is NTFS. <Shrug>

I included the updated XML file and the screenshot from when it's done. The ISO file it creates is larger than the Official one. Official ISO size is 4,689,152KB and the NTLite ISO is 5,774,336KB.
 

Attachments

  • Finished-Screen.png
    Finished-Screen.png
    117.5 KB
  • Rabbit-20230827.xml
    22.7 KB
Grab some of Rufus older versions, use the portables(they have a P in the file name), if it fails with them too we can rule rufus out at least.

Try this - format your usb drive from windows explorer, copy your updated image files to it and try to install.
 
Last edited:
MCT uses ESD compression for the install image, which is ideal if you want to squeeze it under 4GB size (FAT32's maximum filesize).
Therefore Rufus will default to FAT32 filesystem, when applicable.

When you edit images, they must be converted to WIM format (not as compact). If you don't convert back to ESD in NTLite, then your image will normally exceed 4GB. Rufus will default to NTFS filesystem for such ISO's.

If you don't perform DISM cleanup, any superseded components replaced by the Cumulative Update will take up more space. That's also not including natural growth due to patching for new features. Unless you're stripping an image, the natural tendency is to grow over time.

Component removals + DISM cleanup + convert to ESD -> smallest ISO

Don't get obsessed by the ISO size on the first day of school. Take the time to learn how to customize images to your needs. There's no point making a tiny OS if it doesn't run anything you need Windows for.
 
Liting a captured image is the best way to get the smallest, all updates installed and let ntlite do the legwork cleaning it out.
When i say smallest i mean that for even a default type image(no removals at all) ntlite is the best way to clean up after updates and you will get wim and iso sizes close to the original untouched versions.
 
Clanger said:
Grab some of Rufus older versions, use the portables(they have a P in the file name), if it fails with them too we can rule rufus out at least.

Try this - format your usb drive from windows explorer, copy your updated image files to it and try to install.
Click to expand...
I formatted a fresh USB drive and unzipped the new ISO onto it. Same issue when trying to boot to it. Next up is trying an older RUFUS. The one I was using is 4.2p. Gonna try 3.22p next.

** EDIT **
Nope. Different version of RUFUS makes no difference. If there's a checkbox I'm supposed to be clicking, I'm damn sure not seeing it.
 
Last edited:
next time speed up or cut the loading proecss so you upload easier....

from what i see it should be something about your computer's bios settings. you are using GPT format maybe your system is damn old? try bios legacy.
 
crypticus said:
next time speed up or cut the loading proecss so you upload easier....

from what i see it should be something about your computer's bios settings. you are using GPT format maybe your system is damn old? try bios legacy.
Click to expand...
I don't understand the comment. Why wouldn't I use GPT over MBR?
Also, as stated in the original post, before NTLite touches the ISO the process works just fine. I don't understand what NTLite is changing that makes it no longer work.

As for the video, I've never screwed with video editing. I literally installed Geforce Experience just to record that video and upload it.
 
Considering the video's length, a few screen captures would do the same job (for next time). Everything you've done is normal.

What's of interest, but you can't video, is your BIOS settings:
- disable Legacy boot
- disable SecureBoot (for now)
 
I just finished making a new USB and it worked. I had to choose the Compact option when making the ISO and that let RUFUS install as Fat32 just like with the Official ISO. Whereas without the Compact option is was formatting the USB as NTFS and the other system wasn't reading it correctly. It's still using GPT and UEFI on the other system, thus why I wasn't understanding what Crypticus trying to say.
 
NTFS vs FAT32 for SecureBooot, was fixed in Rufus two years ago. It really shouldn't matter unless you have ancient BIOS where Rufus' fix is still unsupported.
 
You must log in or register to reply here.
Back
Top