MS MCT ISO 22621.382, fails to upgrade from 22000.1042

Anonymous
2022-09-23T23:57:40+00:00

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.

Windows for home | Windows 11 | Windows update

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.

0 comments

46 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. TekkieBoy 12,556 Reputation points Volunteer Moderator
    2022-09-24T07:55:24+00:00

    @fg2001

    A hardware block for a Windows upgrade does not automatically mean that it has to be the computer itself.

    Like in this example:

    https://answers.microsoft.com/en-us/windows/forum/all/cannot-update-to-windows-11-version-2022-22h2/b1fda37d-3a10-4bdc-8d56-c6656a14124f?messageId=230bc95a-33d4-4033-9dd4-38c6ecbeee45 

    The Upgrade block was activated by Microsoft on 09/22/2022.

    This does not mean that you have to have the same block on your device.

    There are currently other causes blocking the upgrade too.

    The reasons for a blockage must be determined on each computer itself, so one cannot say in general that, for example, a printer with an IPP class driver is always the cause.

    Greetings

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-09-24T05:17:00+00:00

    Then I've done everything I can do about this. Actually more, since no one else would have taken the time to explain it as fully as I did for you.

    Let me know if I can help further. I'll stay subscribed to this thread in case you need anything else, until the system locks it in a few months.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-09-24T04:57:03+00:00

    Greg,

    I've already reported the problem on FBH.

    Thanks anyway.

    https://aka.ms/AAi6ab9

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-09-24T04:54:39+00:00

    Was there anything else? I gave you the best answer based on more experience in tech forums than almost anyone on the web. I've sat in many meetings with developers as an MVP where they explained gating during these releases in detail. So I shared with you inside information that almost no one else knows since they don't talk about gating publicly that much.

    I wish there was more I can do but in this case letting you know what this has meant for others bases on handling countless similar cases is all I have. I'm sorry if that is not enough. I suggested you report this to developers who will see it via the Feedback Hub, then will not see it here.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-09-24T04:38:45+00:00

    It could be a bug, or the hardware could have become gated as I've already explained. We see this a lot in new Window Edtions and Feature Updates.

    Is it still in an Insider channel? If so remember this is by nature unstable and only to be run on test machines, never on a PC you depend on. You probably already know this but I need to repeat it anyway for those who don't. So that right there would explain the bug.

    Be sure to report this bug to Insider Program using the Feedback Hub in Start Menu. While they will probably not see this here in the forums, but Microsoft developers DO read feedback from customers that comes in via the Feedback Hub.

    Was this answer helpful?

    0 comments