Problem with in-place upgrade from Windows Server 2019 to 2022

TomaszW-0873 131 Reputation points
2021-09-18T19:12:09.42+00:00

I have an issue when I try to do an in-place upgrade from Windows Server 2019 to Windows Server 2022. Installation itself starts, run okay but after restarting, system reverts to older version of Windows and I got the following errors:

0x800F081E-0x2003
The installation failed in the SAFE_OS phase with an error during INSTALL_UPDATES operation

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,470 questions
{count} votes

22 answers

Sort by: Most helpful
  1. Mike-2930 61 Reputation points
    2021-10-29T19:44:15.03+00:00

    In my case this could be resolved by setting the setup procedure so as to not install any updates (click "Change how Setup downloads updates" in the initial panel, then select "Not right now").

    Elsewhere, others had suggested deleting all other user profile references under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList, but I did not try this (seemed too radical). But I did try installing as the local administrator rather than as the domain account, and that made no difference, it still failed. Disabling updates was the solution.

    10 people found this answer helpful.

  2. MaximillianC 86 Reputation points
    2022-05-14T21:36:04.553+00:00

    It sounds like @Mike-2930 's answer would have worked for me too, but I ended up doing a similar-but-different thing to fix this same issue, because, unfortunately, I thought the answer at the top (which basically said "don't do upgrades") was the "accepted answer", and initially didn't scroll down and see the other more-helpful responses. For others who may encounter this issue, I hope this info helps you solve it quicker than me. Hopefully people vote up mine and/or @Mike-2930 's responses to push them above the less-helpful one that's currently "above the fold"

    0x800F081E ("CBS E NOT APPLICABLE") is a Windows Update/DISM error that means an update was attempted to be installed that is not relevant/applicable to your system. I searched for 0x800F081E in C:\$WINDOWS.~BT\Sources\Panther\setuperr.log (upgrade logs explained here), and found the following:

    2022-05-14 03:45:20, Error SP CAddCbsPackage::DoExecute: Failed to add package Add [2] package C:\$WINDOWS.~BT\DUImageSandboxMicrosoft-Windows-RasCMAK-Client-Package~31bf3856ad364e35~amd64~~.cab to C:\$WINDOWS.~BT\NewOS. Error: 0x800F081E

    In my case, I had the RAS Connection Manager Administration Kit Windows component (that's what "RasCMAK" stands for) installed on our IIS Servers... so I went into Server Manager and uninstalled that component, then ran the upgrade again. The upgrade then completed successfully.

    Again, @Mike-2930 's solution probably would've probably worked for me too, if I'd seen it the first time I found this thread, but my alternative solution above may be preferred for some, as it allows you to still updates as part of the upgrade process, reducing or eliminating the patching required after the upgrade completes.

    8 people found this answer helpful.

  3. Alec Garcia 46 Reputation points
    2022-08-03T04:58:31.117+00:00

    I have been running into the same thing with most of my Windows Servers I have tried to upgrade. I tried just about everything else everyone mentioned. I finally tried using the original ISO form Microsoft and not the latest updated one they have. Seems to be working fine now for in place upgrade. Just have to do more windows updates afterwards.
    SW_DVD9_Win_Server_STD_CORE_2022__64Bit_English_DC_STD_MLF_X22-74290.ISO

    6 people found this answer helpful.

  4. Joe K 16 Reputation points
    2022-06-21T23:31:35.643+00:00

    I had the same error. I disabled the NICs on this machine, and was able to proceed with the upgrade. Hopefully this helps others.

    2 people found this answer helpful.

  5. Mike-2930 61 Reputation points
    2021-10-29T07:04:13.53+00:00

    The common element in this thread seems to be RRAS? Same here, simple 2019 VM with nothing else.

    setupact.log contains the following:

    2021-10-29 06:08:07, Error [0x08085f] MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH) failed gle=0x7f.[gle=0x0000007f]
    2021-10-29 06:08:07, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: File is present, most likely it does not load on the current OS version
    2021-10-29 06:08:07, Error [0x080863] MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
    ...
    2021-10-29 06:28:18, Error [0x08085f] MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: LoadLibraryExW(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll, LOAD_WITH_ALTERED_SEARCH_PATH) failed gle=0x7f.[gle=0x0000007f]
    2021-10-29 06:28:18, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: File is present, most likely it does not load on the current OS version
    2021-10-29 06:28:18, Error [0x080863] MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]

    1 person found this answer helpful.
    0 comments No comments