Trying to update to Windows11 22h2 but always fails even when trying to install fresh ISO

Anonymous
2023-02-14T15:21:30+00:00

I've been trying to update to the latest Win11pro 22h2 since last December. Not working well at all. It always gets to 98% and then "something happened" and it rolls it back to 21h2 as you see below. I've tried everything except to nuke the SDD and treat it like is was a new unit. Not really wanting to go that route.

I started just with the Windows update, no joy.

moved to the ISO, mounted and install, no joy.

turned off my Antivirus and tried above two methods again, no joy.

uninstalled my Antivirus and tired above two methods again, no joy.

I've been reading these forums and trying their ideas, no joy.

need a little help here I guess to move forward. I've pasted my machine info below and there are links to SETUPACT.log, SETUPAPI.LOG, and a screen shot of the error after a reboot from trying to install from ISO and it did its automatic roll back.

SETUPACT.log: https://1drv.ms/u/s!ApNnd0WJC5zahVcJuecXbkgIqPYG?e=NJ3zEk

SETUPAPI.LOG https://1drv.ms/u/s!ApNnd0WJC5zahVaWIlWpf14BL4l-?e=PWShbz

screen shot: https://1drv.ms/b/s!ApNnd0WJC5zahVnCV9ccg2DCKH4d?e=2iqg8J

Device name JOES-DESKTOP-072019

Full device name

Processor AMD Ryzen 5 2600 Six-Core Processor 3.85 GHz

Installed RAM 32.0 GB

Device ID 0201820E-6Bxx-47E5-9B71-xxxxxxx456F4

Product ID

System type 64-bit operating system, x64-based processor

Pen and touch No pen or touch input is available for this display

Edition Windows 11 Pro

Version 21H2

Installed on ‎1/‎17/‎2022

OS build 22000.1281

Experience Windows Feature Experience Pack 1000.22000.1281.0

Any help is appreciated,

JoeF

Windows for home | Windows 11 | Install and upgrade

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

44 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Ramesh 181.9K Reputation points Volunteer Moderator
    2023-02-16T19:42:02+00:00

    Joe,

    This could be a user rights assignment issue.

    From this Microsoft Learn webpage: ___________________________________________________________________________________________

    This security ID may not be assigned as the owner of this object.

    Explanation:

    The owner of a new object must be one of the users or groups you have been given the right to assign as the owner. Typically, this is your user account and, if you are an administrator, the administrator's local group.

    User Action:

    Learn which users and groups you have the right to assign as owner. Then try again.

    ___________________________________________________________________________________________

    And the most important thing I found from your setup log:

    2023-02-15 13:16:31, Info MOUPG Target OS: Detected Source DomainName = [DPBROWN]

    2023-02-15 13:16:31, Info MOUPG Target OS: Detected Source DomainJoined = [Yes]

    ___________________________________________________________________________________________

    That confirms that this is a user rights assignment issue.

    Since your PC is connected to a domain, the Active Directory governs the user rights and security policies.

    Create a local admin account

    The best option I can think of is to create a local user account and run setup from there. And yes, clean-booting is always recommended, regardless.

    Let's know how it goes.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-02-16T19:58:14+00:00

    Well, I am an administrator and have the rights but we have struggled through the MS server on issues like that before.

    But my question is, if it is a user rights issue, then why have I been able to update this since I built it on Win8.1?

    I upgraded it to the Win 10pro and then last year went to Win11pro in January. Never had any of these issues then...

    We haven't updated our server (which needs it badly). So nothing should have changed.

    I will drop out of the domain and see about updating that way. Will let you know then.

    Thanks for the help.

    JF

    Was this answer helpful?

    0 comments
  3. Ramesh 181.9K Reputation points Volunteer Moderator
    2023-02-16T20:16:33+00:00

    Joe,

    I'm just interpreting the log for you. The error code 0x51B and the official explanation are very clear; those entries are logged for a reason. Especially when they appear at the tail end of the log, they have more significance, IMO.

    But my question is, if it is a user rights issue, then why have I been able to update this since I built it on Win8.1?

    I upgraded it to the Win 10pro and then last year went to Win11pro in January. Never had any of these issues then...

    The user rights assignments may have changed recently. I don't know. It's not about *your* account's admin rights. There is a bunch of other User Rights Assignment settings in the GPO [Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment].

    I've uploaded the screenshot of my Local Policies/URA page here (BTW that's from a Windows 10 PC).

    I will drop out of the domain and see about updating that way. Will let you know then.

    Ok 👍

    Edit:

    To quickly create a local account, run the following:

    • net user backupuser /add
    • net localgroup administrators backupuser /add

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-02-16T21:59:05+00:00

    Ok, so no need to create a new local account because when I built the computer, I use a local account until it's ready with all the "other software(s)" I need then I join the domain.

    So I logged out and signed in back in as LOCAL ADMINISTRATOR and went to system updates, downloaded the update and.....

    same thing as always... "we have encountered an error and backing out all updates".... bla bla bla.

    I guess I can log back in local and run those log programs and post those here as well so you can see the difference if any.

    I'll work on that and try to post those yet tonight.

    Was this answer helpful?

    0 comments
  5. Ramesh 181.9K Reputation points Volunteer Moderator
    2023-02-17T03:09:00+00:00

    So I logged out and signed in back in as LOCAL ADMINISTRATOR and went to system updates, downloaded the update and.....

    same thing as always... "we have encountered an error and backing out all updates".... bla bla bla.

    Any idea if the error code and description (SYSPREP_SPECIALIZE) are the same as before? This is the first time I have seen the setupact.log 0x51B error.

    I guess I can log back in local and run those log programs and post those here as well so you can see the difference if any.

    I'll work on that and try to post those yet tonight.

    Ok. Please also compare the Local Policies/URA settings with the SS I posted.

    Was this answer helpful?

    0 comments