I’ve been writing about Windows since version 3.1. I remember the floppy disk shuffle. I remember the joy of actually getting TCP/IP running on Windows for Workgroups. You’d think, after thirty-plus years, I’d have an easier time convincing my own workstation to accept a clean OS install. You would be wrong. Instead, in the words of Supertramp I had to “Take the long way home.”

Why I Had to Take the Long Way Home…

My go-to test PC is a Lenovo ThinkStation P3 Ultra Gen 3. It’s a legitimately serious machine, the kind with big SO-DIMM memory modules and a front panel that looks like it means business. It was humming along on Windows 11 24H2 without complaint. Then Microsoft quietly lit up the Windows 11 25H2 branch, and I figured: let’s do this. Simple in-place upgrade, twenty minutes, done by lunch. Instead, I got error code 0xC1900101-0x20017. Twice.

Driver Madness and Mayhem

If you’ve tangled with Windows upgrade failures before, you know that particular error code is frustratingly vague . Indeed, it lives in the SAFE_OS phase of the upgrade process, which means Windows has already swapped out its core OS files. But it chokes when it tries to apply drivers during the rollback-protected transition. In plain English: the driver stack fell over at exactly the wrong moment. I pulled the SetupDiag logs, confirmed it was a driver-related hang in the SAFE_OS phase, and stared at the ceiling for a while.

There’s a particular flavor of irony in being a professional Windows tech writer whose own PC refuses to cooperate with a Windows upgrade. I considered filing it under “job security” and moved on. After two failed in-place attempts, the logs were clear enough: a clean Windows 11 25H2 install was the only sane path forward. OK, fine. Now it’s time to go the long way, and do it the hard way.

Day 2: USB Media Chaos

I grabbed my trusty ADATA S102 32GB USB 3.0 flash drive — the one that has lived in my desk drawer for so long it practically has squatter’s rights. Next, I fired up Rufus to build a bootable installer. Rufus is usually my go-to. Usually.

This time, Rufus misdetected the hybrid image structure inside the Windows 11 25H2 ISO and produced a drive that my P3 Ultra’s UEFI couldn’t see. No error. No explanation. Just a polite boot menu that pretended the USB drive didn’t exist as a bootable option. Lovely.

Switch to balenaEtcher. Flash succeeds cleanly, the drive is recognized, the installer begins to load. Next, it promptly fails because install.wim inside the 25H2 ISO clocks in north of 5 GB. Alas, the FAT32 filesystem that UEFI boot requires has a hard 4 GB per-file ceiling. We’ve known about this limitation for years. It still bites people. It bit me.

The fix is DISM‘s /Split-Image switch, which carves the oversized WIM into a set of smaller SWM files. The command looks like this:

Dism /Split-Image /ImageFile:install.wim /SWMFile:install.swm /FileSize:4000

That produces install.swm, install2.swm, and however many additional slices it needs to keep every piece under the 4 GB limit. The elegant part: Windows Setup natively recognizes and reassembles SWM files on the fly when it finds install.swm sitting on the same drive. This calls for no extra flags, nor manual stitching. You just copy the SWM files onto your FAT32-formatted USB alongside the rest of the installer content and walk away.

For good measure, I also tried my Kingston DataTraveler 70 (USB-C) routed through my Acasis TB5010Pro USB4/Thunderbolt enclosure. That combination booted without a fuss, confirming the Thunderbolt chain was playing nicely with the UEFI boot stack. Good to know for the future.

Day 3: Secure Boot Shenanigans

With bootable media finally usable, I plugged in the drive, rebooted, and hit the BIOS. ThinkStation P3 Ultra runs Lenovo’s UEFI firmware, and if you’ve never spelunked the Lenovo workstation BIOS, know this: it is thorough. Very thorough. There are settings in there I’m fairly certain have never been touched by human hands.

The Secure Boot section alone offers three distinct modes: Setup Mode, User Mode, and Audit Mode. My machine had been enrolled in Secure Boot with Microsoft’s standard production key. That’s normal for a production workstation. Darned if the USB installer  didn’t trigger a Secure Boot violation on the very first boot attempt. The system refused to load the installer, flagging it as untrusted.

So, I turned Secure Boot off (Disabled). That’s enough of a foothold to get the installer running. Post-install, I turned it back on and everything was properly locked down again. Annoying? A little. Correct behavior by the firmware? Absolutely.

I also needed to check the Startup tab in the BIOS to confirm boot device priority. As expected, the NVMe SSD was sitting above the USB device in the boot orde. That’s normally what you want and exactly what you don’t want when you’re trying to boot from USB. Bumped the USB device to the top, saved, rebooted. Whoever designed UEFI menus clearly never had to navigate one under deadline pressure. That said, at least the ThinkStation’s implementation is logically laid out once you know where to look.

Day 4: BitLocker’s Takes the Stand

By Day 4, I was feeling cautiously optimistic. The installer booted. The language selection screen appeared. Life was good.

Then Windows Setup looked at my target NVMe drive and politely informed me that it was BitLocker-encrypted and couldn’t be formatted without the recovery key. Of course it was. I had BitLocker enabled on the previous 24H2 install. That’s the default, after all. And, alas, I hadn’t decrypted the drive before starting this whole adventure. Classic.

I retrieved the BitLocker recovery key from my Microsoft account at account.microsoft.com/devices/recoverykey, then dropped into a pre-installation WinPE command prompt from the installer’s repair menu. Using manage-bde, I unlocked the drive with the recovery key and kicked off decryption. Depending on drive size and how much data is on it, this can take a while — budget accordingly.

Building Better Boot Media

With the drive decrypted, I used diskpart to nuke the partition table entirely and start clean:

select disk X
clean
convert gpt

This gives you a genuinely fresh GPT partition table, not just a reformatted volume with old metadata lingering in the corners. Worth the extra two minutes every time.

One more wrinkle worth flagging: the ThinkStation P3 Ultra uses a firmware TPM 2.0 via Intel PTT — the chip Windows 11 relies on for both BitLocker and Secure Boot attestation. Decrypting and wiping the drive before the  fresh install prevents TPM ownership conflicts that can otherwise surface post-install, when Windows tries to re-seal the new BitLocker keys to the TPM and finds stale metadata from the previous OS. Getting ahead of that saved me a likely Day 5 headache.

Day 5: Clear Skies at Last

On Day 5, everything finally cooperated. Bootable media: sorted. Secure Boot mode: disabled. Drive: decrypted, wiped, and wearing a fresh GPT partition table. I plugged in the USB drive, rebooted, and watched the Windows 11 25H2 Setup wizard run from start to finish without complaint. It almost felt anticlimactic.

Post-install, the news got better. All Lenovo ThinkStation-specific drivers installed cleanly through Windows Update and Lenovo Vantage. I needed no manual INF hunting, nor saw any Device Manager yellow triangles. The NVIDIA professional GPU drivers (ThinkStation ships with a range of NVIDIA RTX options depending on configuration) updated through Windows Update without drama. The resulting install is fast, clean, and correctly locked down with Secure Boot and BitLocker re-enabled on the fresh volume.

Was it a walk in the park? Not even slightly. It was more obstacle course than OS upgrade — and every single obstacle was one I’ve written about in some form over the years. There’s a certain humbling quality to running face-first into your own documented knowledge. But the system at the end of it is genuinely better for the process: no upgrade cruft, no lingering driver artifacts from the 24H2 stack, no half-migrated settings. Just a clean Windows 11 25H2 install the way the OS was meant to be experienced.

A Looooong Way, Indeed

Supertramp was onto something: sometimes the long way is the only way home. At least when you take the long way, you learn every pothole in the neighborhood. Bonus: you’ll know exactly where they are next time.

Every so often, Windows administrators run into a problem that looks like one thing but turns out to be something else. My recent adventure with Lenovo’s USB Recovery Creator is a good example. What started as a simple attempt to build a recovery USB stick for a ThinkStation P3 Ultra Gen 3 turned into a deep dive into how Windows, UEFI firmware, and USB controllers decide what counts as “removable media.” Spoiler alert: it’s the layout, not the UFD. To access this tool visit Lenovo Support, plug in your Lenovo PC serial number, go to the Drivers & Software page, then click the Submit Recovery Media Order button.

Why I’m Sayin’: It’s the Layout Not the UFD

If you’ve ever plugged in a perfectly good USB flash drive only to have Lenovo’s recovery tool refuse to see it, you’re not alone. I tried half a dozen drives. They included 32+GB models from SanDisk, Kingston, Mushkin, Transcend, ADATA, even a brand‑new 256GB USB‑C DataTraveler. Every single one failed Lenovo’s removable‑media test. Windows saw them. Explorer saw them. Disk Management saw them. But Lenovo’s tool? Nada. The dropdown menu stayed stubbornly empty.

That’s when the real troubleshooting began.

Why the Tool Rejects “Unspecified” Devices

Lenovo’s USB Recovery Creator is picky. Indeed, it’s far pickier than most users expect. It doesn’t simply look for a USB drive. It looks for a USB drive that reports itself as MediaType = Removable through Windows’ storage stack. Anything else—SSD, HDD, or the dreaded Unspecified—gets ignored.

Here’s the catch: many modern USB flash drives, especially high‑performance ones, identify themselves as fixed disks rather than removable media. This is intentional. Manufacturers optimize for speed, wear leveling, and controller behavior to mimic SSDs. Windows is fine with this. UEFI is fine with this. Most tools , ditto. Lenovo’s USB Recovery Creator tool is not.

When I ran:

Get-PhysicalDisk | Select FriendlyName, BusType, MediaType

every single UFD I owned showed up as:

• BusType = USB
• MediaType = Unspecified

That’s the kiss of death for Lenovo’s recovery tool. It will never list a device that reports “Unspecified,” no matter how new, fast, or reliable it is.

Proper Cleaning, Formatting and Partitioning Works

Here’s where the story takes a turn. Conventional wisdom says formatting or repartitioning won’t change how a USB device identifies itself. And that’s true — MediaType doesn’t change. But Lenovo’s tool isn’t only checking MediaType. It’s also checking the partition layout, and that’s where things finally broke open.

After trying multiple drives and ports, I decided to go nuclear and rebuild the USB stick’s layout from scratch using DiskPart. The magic sequence turned out to be:

diskpart
list disk
select disk X
clean
convert gpt
create partition primary size=32000
format fs=fat32 quick
assign
exit

The moment I did this — and I mean immediately — the Lenovo USB Recovery Creator dropdown lit up and showed the UFD. No hesitation. Nothing ambiguous. No more empty menu.

This was the breakthrough: Lenovo’s tool requires a very specific starting layout before it will accept a USB device, even if the device reports MediaType = Unspecified.

In other words, the tool doesn’t just care about whether the drive is removable. It cares about:

• GPT vs MBR
• Partition count
• Partition size
• Partition type
• File system
• Whether the drive is “clean”
• Whether Windows has mounted it consistently

Once the drive was wiped, converted to GPT, given a single 32GB FAT32 primary partition, and mounted cleanly, Lenovo’s tool recognized it instantly. That’s when the lightbulb lit up: it’s the layout, not the UFD.

Why Lenovo’s Tool Needs a Clean GPT/FAT32 Layout

Lenovo’s recovery creator expects to take full control of the USB device. It wants to:

• wipe the drive
• repartition it
• write a bootloader
• copy the recovery image
• verify checksums

If the drive has:

• multiple partitions
• leftover boot sectors
• exFAT or NTFS formatting
• odd alignment
• remnants of previous boot media
• a corrupted MBR
• a GPT with unexpected metadata

the tool simply refuses to show it in the list of acceptable targets. This explains why even brand‑new drives failed: they shipped with factory formatting that didn’t match Lenovo’s expectations. That said, once the layout was corrected, the tool behaved exactly as designed.

The Real Lesson: Modern USB Behavior Requires Modern Troubleshooting

This experience taught me something important: modern USB flash drives aren’t the simple “plug‑and‑play removable media” devices they used to be. They behave more like miniature SSDs, and their factory formatting often reflects that.

Lenovo’s USB Recovery Creator, however, still expects a classic removable‑media layout. When the layout doesn’t match, the tool silently ignores the device. Fortunately, the fix is straightforward once you know what the tool wants to see.

Lesson Learning

If you’re struggling with Lenovo’s USB Recovery Creator, don’t assume your USB flash drive is bad. Don’t assume the ports are faulty. Don’t assume the controller is misbehaving. The real issue is usually the partition layout on the UFD. Clean it. Convert it. Create a simple FAT32 primary partition. Then watch the Lenovo tool recognize it instantly.

In other words: it’s the layout, not the UFD. Here in Windows-World these little details matter. They sucked up my morning and tossed it away. This afternoon, I’m back on the hunt. Whew!