Boot into Win PE is extremly slow.

That info i also got when trying my manouvers earlier in the thread, i ignored it and went ahead. After install i wondered what it was all about since i did not get any warning, ever.

As i understand it Ms changed something regarding the mentioned feature, hence the message about a future warning. On new ISOs i of course did not see it.

 

Most likely the Microsoft signed certificate embedded in the ISO is expired, so the installation media will not boot on a PC with secure boot enabled. Rufus is just giving a warning.

Ask your friend to temporarily disable secure boot in their BIOS. If the option to disable secure boot is greyed out then they will first need to set a BIOS admin password, disable secure boot, and then remove the BIOS admin password. With secure boot disabled, Rufus should no longer give this warning.

Secure boot just prevents your PC from booting through a malware infested bootable media, thus bypassing the OS built in security. If you know the media is from a trustworthy source, and you are the only person who uses the PC, then there are no issues in temporarily disabling it.

 

Thanks guys. Last night I downloaded 22HD and tried Rufus on my Win11 computer with Secure Bot enabled. I saw the Rufus warning but went ahead and made the UFD. The UFD booted on my Win11 computer with Secure Boot enabled.

Just now I disabled Secure Boot on my Win 11 computer and tried Rufus with the same ISO. The Rufus warning still appeared.

 

The RUFUS warning will always occur because it has no idea where you plan to use the UFD it's about to create... so it warns you.

The ISO you're burning contains the somewhat current Microsoft "trust anchor" needed by SECURE BOOT to BOOT properly in a given machine. A few years back, Black Lotus appeared on the scene and was discovered to be able to break SECURE BOOT. As a result, Microsoft needed to come up with a different Boot Anchor scheme to insure the integrity of Secure Boot. It has been working on this issue since 2023, with a plan to deprecate all previous boot anchors when the final release occurs next year. RUFUS knows all about this and the registration codes of all the boot anchors about to be deprecated. If your future ISOs don't have the new boot anchors, they will never BOOT into Secure Boot, sometime next year..

You can read about the issue HERE...

 

Thanks TRF, the UFD made from 22H2 did boot in my Win11 computer with Secure Boot enabled. But my UEFI BIOS likely has the latest Secure Boot definitions.
My mate has a Win10 computer. He doesn't want to boot from the 22H2 UFD; he wants to upgrade to Win11. His concern is will Win11 boot with or without Secure Boot enabled if the upgrade is successful.

 

I don't think things are really "final" (latest) until MicroSloth releases the final fix next year. There may have been some mods along the way but not... "the
final solution."

A lot of System BiOSes haven't even been modded yet by their particular OEMs just so things don't break before they have to.

 

He made a UFD from 22H2 while ignoring the Rufus message. Once again the Win11 upgrade failed with an incompatible hardware message.

I'll have his laptop in September and I'll try the Win11 upgrade on my computer.

 

Did it say which hardware was incompatible? Do you have the specs for the PC?

 

RUFUS (current version) will not only offer that warning but also an option panel for the ISO build. On that panel, there is an important option which must be selected (by DEFAULT it's not) or that gen CPU (anything older than Gen 8 ) will not allow W11 to be installed. The DEFAULT option panel is below and the option needed for a Gen 6 CPU is the 1st one.

Can you be sure your mate is using that?

 

He used the first, 5th and 6th.

 

i7-6600U
TPM 2.0
The error message was generic and didn't specify the hardware issue.

 

^This CPU is on a Microsoft block list and Rufus cannot bypass CPU checks.

The following threads might be some help.

This person was able to upgrade their i7-6600U PC to Windows 11.

This is the process they followed.

Another thread discussing the same process.

Hope this helps...

 

Great advice.
TRF asked what the error message said so I asked him to run setup.exe again. On the error message was an Accept button which he'd been ignoring. I suggested he press it and the upgrade started. It's not finished yet but it looks promising.

 

I have often thought about trying NTLite, but have never done so.

 

Success. He has Win11 22H2. He'll try for 24H2 tomorrow.

The joys of running support over the phone.

 

Success again. He now has Win11 24H2.

 

Onwards and... upwards

24H2 has had a lot of "anomalies" along the way... stay diligent.

 

I upgraded a Win10 Home 22H2 laptop, with a 2nd generation CPU, to Win11. I omitted the intermediate upgrades mentioned above and used Win11 24H2. There was a warning concerning incompatible hardware but if you click the Accept button the upgrade continues.