For more than 30 years as a software engineer, I've built countless bootable USB drives.
I've used UltraISO for years without giving it much thought. It always worked, whether I was installing Windows on desktops, laptops, or servers. So when I recently restored an old Lenovo ThinkStation P410, I expected the installation process to be routine.
It wasn't.
What looked like a hardware problem turned out to be something much more subtle: UEFI boot compatibility.
The Symptom
I prepared a Windows installation USB using UltraISO, plugged it into the P410, powered on the machine, and pressed F12 to open the Boot Menu.
Nothing.
The USB drive simply wasn't listed.
I tried multiple USB ports.
I checked the BIOS settings.
I switched between UEFI and Legacy boot modes.
I enabled Legacy USB support.
Everything looked perfectly normal, yet the boot menu refused to recognize the installer.
At first, I suspected the workstation.
Then I suspected the BIOS.
Then I even started questioning my PCIe SSD adapter.
None of those turned out to be the real problem.
The BIOS Wasn't the Culprit
The ThinkStation's BIOS configuration looked correct:
- UEFI boot enabled
- USB devices enabled
- Legacy USB support enabled
- AHCI mode enabled
- Secure boot wasn't blocking anything
Nothing stood out as obviously wrong.
This made the situation even more confusing.
One Small Change Solved Everything
Eventually, I recreated the exact same Windows installation USB.
The only difference?
Instead of UltraISO, I used Rufus.
I plugged the USB drive into the same port.
Powered on.
Pressed F12.
The installer appeared immediately.
No BIOS changes.
No firmware update.
No hardware modification.
The only thing that changed was the tool used to create the bootable USB.
Why This Happens
Modern PCs generally follow the UEFI specification much more strictly than machines from a decade ago.
Although UltraISO can certainly create bootable media, its UEFI implementation doesn't always produce media that every firmware accepts equally well.
Many systems boot it just fine.
Some older enterprise workstations, however, are much more selective.
Rufus spends considerable effort maintaining compatibility across different firmware implementations, partition layouts, and Windows installation images. That extra compatibility work is probably why it succeeded where UltraISO failed.
A Second Surprise
While troubleshooting, I also discovered something else.
I had installed an M.2 SSD on a simple PCIe adapter, yet Windows Setup couldn't detect the drive.
Initially, I assumed the adapter or BIOS was incompatible.
After checking the SSD model, I realized my mistake.
The drive was:
SK hynix SC311 SATA M.2 SSD
Not NVMe.
The inexpensive PCIe adapter I was using was designed for NVMe (PCIe) drives only.
Although both drives use an M.2 connector, they speak completely different protocols:
- M.2 SATA → SATA/AHCI
- M.2 NVMe → PCIe/NVMe
The connector looks the same.
The protocol is not.
It's an easy mistake to make if you're focused on the physical connector rather than the interface underneath.
Lessons Learned
Even after decades of working with computers, this experience reminded me that assumptions can be expensive.
Two simple assumptions wasted hours:
- "UltraISO has always worked before, so it must still be the best choice."
- "Every M.2 SSD is basically the same."
Neither assumption held true.
Today, when I'm creating Windows installation media, Rufus has become my default recommendation.
And whenever I see an M.2 SSD, I check one thing before anything else:
Is it SATA or NVMe?
That tiny detail changes everything.
Final Thoughts
What surprised me most wasn't the technical issue itself.
It was realizing that I had never questioned a tool I'd trusted for years.
Sometimes the hardest bugs aren't caused by broken hardware or incorrect BIOS settings.
They're caused by a perfectly reasonable assumption that quietly became outdated.
If you're working on an older workstation, your USB installer doesn't appear in the boot menu, and you've already verified your BIOS settings, don't overlook the tool that created the installer.
Sometimes, recreating the USB with a different utility is all it takes.
It certainly was for me.