MS MCT ISO 22621.382, fails to upgrade from 22000.1042

After all this testing, did you ever see a log or anything else that told you exactly why the system is being blocked? I have not seen that message on any of my systems, although I do have one which has not yet been offered the update and no message as to not being capable.

When you did the second upgrade, did you start with a clean drive or could something been left on the system from the previous install?

The online upgrade does download packages for both the .382 and .521 versions, so being offline may not be the best way to go. It appears the in-place upgrade does not download the .521 update package, but I get that from your and other's comments.

One change might be, that the problems with the .521 update, Microsoft may have taken some steps to wait until that situation has been worked out. If I haven't seen the upgrade offered to my second machine by next Tuesday, I will try the .iso upgrade path.

Hi fg,

Not sure if you read this article on Deskmodder. I had this happen once on my Surface Pro, same block screen but one could still install manually.

Of course, Windows 11 22H2 can also be quickly brought to the current 22621 with an ISO and in-place upgrade. But then problems can occur that can arise due to hardware or drivers. The emphasis here is on can.

If Microsoft has already noticed during the evaluation of the data that drivers or devices can lead to problems, then a "safeguard hold" is triggered. This means that Windows Update matches this list and if a driver or device is detected, then no upgrade is offered.

Even installed software, or the saved setup.exe is sufficient for one block. The products are often outdated software that prevents an upgrade to Windows 11 22H2:

Epson Easy Photo Print 2

Kaspersky various products

Lenovo various software

WiDi Remote

Microsoft .NET Framework 4.5

Microsoft Visual Studio 2012

Acrobat Reader various software

AIDA64 Extreme Edition various software

AOL Instant Messenger Pro

AVG PC TuneUp 2014 and 2015

MicroWorld Technologies Inc. (BackupRecovery_d_ .exe)

Baidu Antivirus Various Software

CCleaner

COMODO various software

Double Anti-Spy

McAfee Miscellaneous Software

Corel DVD MovieFactory 7

Dr.Web Security various software

Kingsoft Security various software

The KMPlayer

Lenovo TrueSuite Fingerprint Software, Touch Fingerprint Manager various software

MysticThumbs

Norton various products

Outpost various software

PC Wizard 2013

Sandboxie

Microsoft LifeCam

AVAST various software

Microsoft Office 2010

Spybot – Search & Destroy

Start Menu 8

UxStyle

AVAST various software

AVG various software

Microsoft XNA Game Studio

AutoCAD miscellaneous software

TaxCut Deluxe 2005

DAEMON Tools Pro

DVDVideoSoftTB Toolbar

Fallout 3 Launcher

McAfee Miscellaneous Software

F-Secure various software

Glary Utilities various software

Samsung various software

HP miscellaneous software

Bitdefender various software

Intel PROSet/Wireless Control Panel Applet

Kingsoft various software

Paragon System Utilities

Agnitum Outpost Firewall 1.0

Trend Micro OfficeScan and miscellaneous software

Dell Support Center and Miscellaneous Software

Broadcom Bluetooth Software

Diskeeper 2009, 2010, 2011

Microsoft Security Essentials Setup

AhnLab various software

Symantec various software

Spy Sweeper

StartIsBack

Alcohol 52%

Diskeeper

Conexant CPT5680 PCI Soft Modem

Cisco Systems VPN Adapter

Hi fg,

Not sure if you read this article on Deskmodder. I had this happen once on my Surface Pro, same block screen but one could still install manually.

Of course, Windows 11 22H2 can also be quickly brought to the current 22621 with an ISO and in-place upgrade. But then problems can occur that can arise due to hardware or drivers. The emphasis here is on can.

If Microsoft has already noticed during the evaluation of the data that drivers or devices can lead to problems, then a "safeguard hold" is triggered. This means that Windows Update matches this list and if a driver or device is detected, then no upgrade is offered.

Even installed software, or the saved setup.exe is sufficient for one block. The products are often outdated software that prevents an upgrade to Windows 11 22H2:

Thanks Johnny,

I don't have any of those products in that list.

What is weird that the same Upgrade with the same ISO worked fine 2 days before on 4 machines, nothing is changed on my side in the last 2 days.

I was just testing the same procedure to verify some of the issues that many users have been reporting and now MS decided to block the upgrade.

Keep in mind that these machines have all been using 22H2 for months without any complaint from MS.

Still, I managed now to bypass this silly block and I have all 4 machines running 22621.521 without any issues the same as they were on Sept 21, 2022.

They should at least give an indication for the reason they are blocking the upgrade.

Keep in mind that all 4 my boxes were offered 22H2 through W.U. on Sept 20, 2022. All worked fine then.

On Sept 21 I just wanted to test the upgrade using the MCT ISO which is 22621.382 and that worked perfectly fine on that day the boxes came up with 22621.521 directly, KB5017321 was downloaded and installed during the upgrade process.

Now 2 days later they blocked me from doing the Upgrade from 21H2 to 22H2 with any ISO including a third-party ISO 22621.521.

If MS wants me to stop testing their faulty upgrade/update procedures, they should just say so instead of putting out that stupid message without any better explanation.

Anyway, I'm back to 22H2 on all 4 boxes now.

The upgrade/update process is still just a typical MS mess. Not ready for prime time or GA. 🤣🤣🤣🤣🤐🤐🤐🤐

After all this testing, did you ever see a log or anything else that told you exactly why the system is being blocked? I have not seen that message on any of my systems, although I do have one which has not yet been offered the update and no message as to not being capable.

When you did the second upgrade, did you start with a clean drive or could something been left on the system from the previous install?

The online upgrade does download packages for both the .382 and .521 versions, so being offline may not be the best way to go. It appears the in-place upgrade does not download the .521 update package, but I get that from your and other's comments.

One change might be, that the problems with the .521 update, Microsoft may have taken some steps to wait until that situation has been worked out. If I haven't seen the upgrade offered to my second machine by next Tuesday, I will try the .iso upgrade path.

No logs or explanation for the reason they are blocking the upgrade. Whatever they get with their telemetry they sure don't give us any hint. 😝

Nothing left from previous install.

I just restore the same image backup that I used 2 days earlier for the same upgrade that worked without any issues going from 21H2 to 22H2. 🤣🤣

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,