Has MS Caught on with Flyoobe?

So a few months back I used Flyoobe to update an older Lenovo Thinkpad, model T420. Windows 11 took OK and it installed version 24H2 which at the time seemed fine. I only use this as a back up and only recently started to use it regularly once again while working in a remote office. I leave my primary system at home.

On a check I decided to see if there were any Windows Updates to be installed and I was confronted with a KB5086672 (26100.8117) download. This is a March 2026 update that a lot of systems took. MY home system (Win 11 25H2) took it with no issues. I then moved to download it to the Lenovo T420 and the system popped up that I do not have the TPM and it refused to allow the update to be installed. It seems that Microsoft built in a TPM checker with this update. See attached images 1 and 2.

I am wondering if anyone else has had this show up that used Fly to install Win 11? It was somewhat expected that MS might eventually catch on with Flyoobe. Is this the bellwether?

Now, more recently I updated a Lenovo H30 desktop to Windows 11 but the ISO I used with Fly was for 25H2. So far no warnings but this install was done within the last 48 hrs so I have the latest 25H2 on board.

So the question is, if MS if blocking this now would downloading the most recent ISO be the course to follow now for my trusty T420, or might that get blocked as well at some point?

Is there a specific Flyoobe sub for this or a forum for discussion elsewhere?

Thanks

you can use a Rufus made USB stick with Windows on
and then do the in place repair using the setup.exe within the USB stick.

also have you updated your secure boot keys?
this maybe of help if you need to.

best of luck Steve ..

sunclad said:

It was somewhat expected that MS might eventually catch on with Flyoobe. Is this the bellwether?

Click to expand...

Rufus has been around a lot longer and it's obvious MS couldn't care less. Indeed, as fast as MS introduce another hurdle, Rufus tweaks itself and all continues on its merry way.

For Rufus, it's almost as if Windows has become open-source software

If this FlyOOBE thing is not working, it's probably because it hasn't been updated to workaround whatever was the latest MS Windows security machination

sunclad said:

It seems that Microsoft built in a TPM checker with this update. See attached images 1 and 2.

Click to expand...

If what you clicked was the "Fix issues" button, then you're not getting a cumulative update. You're getting a set of repair files to fix your Windows installation. That would be the reason for the system compliance check.

Yes, I am getting that "Fix Issues" button and that is the result. So it appears I may have to go the full installation route again which will hopefully work. That will be a weekend project however. The system is in place in usage by me and one other.

You should first try this command as Admin, and then re-run Windows Update.
It might prevent the update check.

Your screenshot shows "Windows 11, version 24H2 (repair version)." The installation fails because the system does not meet Windows 11 hardware requirements, which the installer verifies before proceeding.

How to fix it:

To perform a repair install on a system that doesn't meet Windows 11 system requirements, you will need to perform option three here first, then do the steps in an option in this tutorial below.

Contents

• Option One: Repair Install Windows 11 using Windows Update
• Option Two: Repair Install Windows 11 using ISO or USB Installation Media

Click to expand...

I have not tested that registry tweak myself; in my opinion, the easiest way to bypass the system requirements is as follows:

- Mount (open) the Windows 11 ISO file. It will appear as a virtual drive, allowing you to access its files as if it were a physical disc.
- Run the following command, replacing "X" with the drive letter of the mounted ISO file:

X:\setup.exe /product server

Celery said:

I have not tested that registry tweak myself.

Click to expand...

I tested this in a virtual machine. "Fix problems using Windows Update" works on an unsupported system if you first run the commands mentioned in the link below. Note that these commands only work in an elevated Command Prompt (Administrator).

To perform a repair install on a system that doesn't meet Windows 11 system requirements, you will need to perform option three here first, then do the steps in an option in this tutorial below.

Click to expand...

Option One: Repair Install Windows 11 using Windows Update

Click to expand...

"Fix problems using Windows Update" reinstalls the exact version and build of Windows currently installed, not just the base feature version. It does not remove any files, settings, or apps.

Edit:

Use Option Two in the link below to perform a repair install (in-place upgrade) to a newer feature update. To bypass the system requirements check on an unsupported system, you can, for example, use the command X:\setup.exe /product server (replace “X” with the drive letter of the Windows 11 USB flash drive or mounted ISO file). Alternatively, you can use a Rufus-created Windows 11 USB flash drive.

Option Two: Repair Install Windows 11 using ISO or USB Installation Media

Click to expand...

Thanks to all. The system is in daily usage right now and is working fine for now. In this instance it appears that I will need to run FLY again and gat a fresh copy of the ISO to get passed this "Fix" issue.

Thanks much.