Guess I will never see that concern. I always install offline during clean installs, upgrades via ISO, etc. Why let MS mess around with the install.
Regards,
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
On 9/23/2022 I tried upgrading from 22000.1042 with ISO 22621.382 and got the message on the bottom screenshot.
What is weird is that the same exact process worked fine on Sept 21st. 2022.
I already have a working backup copy of the system that was upgraded on Sept 21st. ����
What is changed in the last 2 days? What is it complaining about? There is no explanation showing on the learn more link.
Windows 11, version 22H2 known issues and notifications | Microsoft Learn
Here is my FBH report link: https://aka.ms/AAi6ab9
This is a Dell XPS 8940.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Guess I will never see that concern. I always install offline during clean installs, upgrades via ISO, etc. Why let MS mess around with the install.
Regards,
Upgrade went through very fast from 22000 to 22621.382
This was on a compliant vm done offline.
Regards,
Offline, with no network connected works fine for me too on a real box from 22000.1042 to 22621.382 looks like yours no problem.
The problem occurs only when connected to the internet.
Edit:
Also, they seem to have fixed today 9/24/2022 error 0x800f0806 for kb5017321 with W.U. 🤷♂️
Hi fg,
It wouldn't be MS if they would clearly explain what went wrong, or why. I do find it unusual that the upgrade worked initially and not couple days later. I can only assume MS found another block issue.
I will try same upgrade path later this weekend.
Regards,
This is interesting:
You can now check if your PC is compatible with Windows 11 22H2 (windowslatest.com)
Hi fg,
It wouldn't be MS if they would clearly explain what went wrong, or why. I do find it unusual that the upgrade worked initially and not couple days later. I can only assume MS found another block issue.
I will try same upgrade path later this weekend.
Regards,