Share via

Server 2019 -> 2022 in place upgrade failure

Brian Hoyt 106 Reputation points
2022-07-06T16:23:30.853+00:00

I am trying to do an in place upgrade of a 2019 Windows Server to 2022. It is a DC and not much else. Please don't respond about not doing in-place upgrades. I have done them for 20 years across hundreds of servers and it is a fully supported scenario.

Upon the first reboot the system has a blue screen with system thread exception not handled. After booting back into original OS I get:
0xC1900101 - 0x20017
The installation failed in the SAFE_OS phase with an error during BOOT operation

I have tried multiple times. I am using the June 2022 ISO from VLSC with latest CU integrated. The current install is running 17763.3046. I tried allowing updates during setup and not allowing updates.

I ran SetupDiag and posted logs at https://studentfasps-my.sharepoint.com/:f:/g/personal/brianh_fasps_org/EklsQwGt2h9HvQY2xBKck7kBRm3skysfe0JkPkwDAC6_dQ?e=xwxYO1 .

I have done the same upgrade on my other DC without issue. Any help is appreciated.

Windows for business | Windows Server | User experience | Other

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. KC 11 Reputation points
    2022-07-15T15:36:48.503+00:00

    I have the exact errors and doing the same upgrade as you ie in-place upgrade winsvr2019 to winsvr2022.
    Refer here https://learn.microsoft.com/en-us/answers/questions/557419/problem-with-in-place-upgrade-from-windows-server.html the last post how I managed to do the in-place upgrade successfully.

    1 person found this answer helpful.
  2. Brian Hoyt 106 Reputation points
    2023-03-16T16:07:08.9666667+00:00

    The final answer for me was an updated ISO. I was told by a MSFT person that this was a bug fixed in November update. I got the latest ISO (Feb 2023 at the time) and was able to do in place upgrade on all my remaining servers.

    1 person found this answer helpful.
  3. Anonymous
    2022-07-06T17:51:35.73+00:00

    Doing an in-place upgrade of a domain controller is never recommended and since you have more than one should not be necessary. Assuming you wanted to reuse the name you could move roles off, decommission / demote, then stand up the new one for replacement.

    The two prerequisites to introducing the first 2019 or 2022 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
    https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

    I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019 or 2022, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

  4. Alexander Straub 1 Reputation point
    2022-07-22T15:17:02.487+00:00

    I have the same errormessage and tried some inplace updates on various hyper-v vm's. If there is any solution I wait for it.
    We do some testing for an production inplace upgrade in August for a customer. But on any hyper-v machine we are trying to do an inplace upgrade we get the same error.

    0 comments
  5. DS 31 Reputation points
    2022-12-08T16:37:32.313+00:00

    Went from 2012 R2 to 2022 by using the AUG 2021 ISO and disabling live updates. Vsphere 7.X

    Found this solution in another thread. Worked like a dream, even on the DC's

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.