Question Update for Windows 11

[BonzaiDuck]

I don't pretend to be an expert on the specialty of upgrading ineligible hardware from Win 10 to Win 11, but I learned a lot, even if only to make caveats with different hardware situations.

This new suggestion -- to execute "setup /product server" is a surprise to me.

I have the Kaby Lake processor, which just precedes Coffee Lake at the top of the eligibility list. I had Z170 motherboards which had pinouts for a $25 TPM 2.0 plugin module. At that time, I was advised (by a Tom's Guide article) to run this registry hack:

Tom's Guide, April 2025
"Open Registry Editor (regedit.exe) as an administrator and navigate to HKEY_LOCAL_MACHINE\SYSTEM\Setup.

"If the MoSetup key doesn’t exist, create it by right-clicking Setup, selecting New > Key, and naming it MoSetup.

"Select the MoSetup key, then right-click in the right pane and choose New > DWORD (32-bit) Value.

"Name the new value AllowUpgradesWithUnsupportedTPMOrCPU, then double-click it and set its value to 1.

"Then click OK and restart your PC."

Even so, I had the TPM2.0, the UEFI, the Secure Boot. Suddenly, this is all irrelevant now because of "Setup /product server".

As I've said elsewhere, I needed to make minor provisions for the Feature Update (24H2 to 25H2). First, turn off third-party AV or anti-malware, leaving Defender to operate, but disabling the other software through reboot and an idle desktop. Second, I have to temporarily uninstall Drive Pool software like StableBit DrivePool.

Others may have different requirements, but a failed Win 11 upgrade (rolling back to the initial Win 10 operating state) will be an indication to look for some Startup software causing the difficulty.

I've not had any other issues letting Win 11 Windows Update operating on its own without intervention.

If the OP can install Win 11 on an Ivy Bridge system without issue, it would seem that the upgrade from Windows 10 is not much of a major issue for anybody.

 

[WelshBloke]

Has anyone with a local Win11 account had Windows trigger the whole oobe thing on a restart?
I have a Win11 VM that suddenly did that out of the blue. Was running fine before with a pro license.
Its fine now, I just had to shut down and restart the VM a few times but it was weird.

 

[BonzaiDuck]

Has anyone with a local Win11 account had Windows trigger the whole oobe thing on a restart?
I have a Win11 VM that suddenly did that out of the blue. Was running fine before with a pro license.
Its fine now, I just had to shut down and restart the VM a few times but it was weird.

I wouldn't know the answer to that, but the OOBE always annoyed me. My Opera and Edge web browsers do that. they seem to need frequent updates or upgrades.

I'm not ashamed to say that I'm getting old, and I get annoyed at "frequent changes and new requirements".

The "Microsoft Account" feature always annoyed me, since I had been networking my computers in a "Home LAN" since around 1994, and even if I were a single user with three PCs, I became comfortable at have an account_ID and password step at boot time on all the machines. Obviously these were all "local accounts". It seems to have worked out pretty well, though, in the integration with the MS account.

 

[tcsenter]

Has anyone with a local Win11 account had Windows trigger the whole oobe thing on a restart?
I have a Win11 VM that suddenly did that out of the blue. Was running fine before with a pro license.
Its fine now, I just had to shut down and restart the VM a few times but it was weird.

Yes, a few days ago when I updated to either the 25H2 or the latest Cumulative Update for 25H2 (can't remember which of the two for sure) via Windows Update. Native not in VM. It was weird I played around with the prompts to sign in or create a MS account, thinking the next screen might offer an opt-out, then use the 'back' or 'cancel' arrow then finally just restarted the PC. Already had a local account.

Something else, too. On a (different) Haswell PC, I installed 25H2 over 24H2 as an in-place upgrade (Windows Update would not offer the update so I used the Rufus deal). So it is reported there is a bug in the Cumulative Update that leaves computers without any USB keyboard or mouse support in a Recovery or Repair environment, for which MS issued an emergency out-of-band update KB5070773.

The KB5070773 fails to install, I suspect because it is checking for W11 hardware requirements/compliance? I tried using Windows Update (it is being offered), downloading and running the MSU as a stand-alone update, and command line. All of them fail with error 0x800f0983.

I ran restorehealth, system file checker, reset Windows Update components, disk cleanup, chkdsk, etc all of which complete successfully but the update still fails.