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

TomaszW-0873 156

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

Brian Hoyt 111 Reputation points

2023-03-16T16:10:12.6666667+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.
Robert Sandri (rsandri) 5 Reputation points

2023-03-20T01:39:34.63+00:00

The Feb 2023 ISO will not work if you have applied VMware Tools 12.2.0 first. A Windows Server 2019 running VMware Tools 12.1.5 (and never previously upgraded to VMware Tools 12.2.0) will upgrade using the Feb 2023 ISO. If the Windows Server 2019 guest has been upgraded to the 12.2.0 VMware Tools, you will not be able to upgrade 2019 to 2022 for the time being.
DavidYorkshire 91 Reputation points

2023-03-20T08:27:43.78+00:00

Presumably you could uninstall the VMWare tools, do the upgrade then reinstall the tools?
Robert Sandri (rsandri) 5 Reputation points

2023-03-20T12:53:57.1166667+00:00

Removing or downgrading the VMware Tools has no effect. I did have success by using the Windows Server 2022 initial ISO released from Microsoft. Others have reported the same but using an ISO from 2021. I have not tested the latter.
Robert Sandri (rsandri) 5 Reputation points

2023-03-22T12:47:27.6833333+00:00

Solution: If you have already installed VMware Tools 12.2.0, you must use an older Windows 2022 ISO to perform an upgrade. I can confirm that the initial Windows Server 2022 release ISO works for the upgrade. Others have reported success with year 2021 ISO releases.
Chris Findley 0 Reputation points

2023-04-17T19:59:24.87+00:00

Experience date: April 2023, running VMware Tools version 12.1.0, Server 2019 with 23-04 Windows updates.

Using SW_DVD9_Win_Server_STD_CORE_2022_2108.11_64Bit_English_DC_STD_MLF_X23-17134.ISO failed with and without disabled update check.

Using SW_DVD9_Win_Server_STD_CORE_2022_2108.19_64Bit_English_DC_STD_MLF_X23-40586.ISO succeeded but only with disabled update check.

The subsequent check for Windows updates found 23-04 Cumulative and 22-08 Security for 21H2.
Robert Sandri (rsandri) 5 Reputation points

2023-06-13T13:12:29.76+00:00

I can confirm that the May 2023 version of the Windows Server 2022 ISO works for upgrades regardless of the situations outlined above,
Anonymous

2023-12-05T01:34:09.34+00:00

Hi Robert Sandri, Can you please post the May 2023 version of the Windows Server 2022 ISO full file name with prefix number part of it? e.g. SW_DVD9_Win_Server_STD_CORE_2022_2108.23_64BitEnglish_DC_STD_MLFX23-50413.ISO

As i am facing the issue with "The installation failed in the SAFE_OS phase" but it does not say : "INSTALL_UPDATES operation" for me but fails with: The installation failed in the SAFE_OS phase

I am trying to upgrade from Windows Server 2016 Standard(Desktop) to Windows Server 2022 (Desktop)
My VM is running on VMware Tools version is on: version:12384 as my ESXi hosts are running on ESXi version 8
Massimo Cracchiolo 0 Reputation points

2025-05-01T21:00:44.8233333+00:00

I was having the same problem with the Feb 2023 ISO. I happened to check and saw that there is a March 2025 ISO. I used the March 2025 ISO and was able to upgrade successfully without issue.

23 answers

Jesse Nanes 6 Reputation points

2022-07-29T14:58:56.507+00:00

I'm in this boat, but disabling Updates during install, disabling nic have not helped. I checked and do not have RAS Connection Manager Administration Kit installed.

After my upgrade attempt from 2019 to 2022 I get "0xC1900101 – 0x20017 and in the setuperr log I see lots of :

2022-07-29 09:53:44, 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]
2022-07-29 09:53:44, Error [0x080863] MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]
2022-07-29 09:56:53, 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]
2022-07-29 09:56:53, Error [0x080863] MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() failed hr=0x8007007f.[gle=0x0000007f]

Please don't come here to say "iN pLaCe UpGraDe R BaD"
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Val 1 Reputation point

2022-08-01T21:49:13.21+00:00

Removing the computer from the domain may help.
Make sure you have local admin credentials.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Matt Starczak 1 Reputation point

2022-10-10T03:02:38.027+00:00

On Hosts running VMServer and ShadowProtect (backup solution)
Increasing the number of processors to 2, and turning off Shadow Protect has worked reliably
Once the upgrade is finished I turn Shadow Protect back on (deleting the chain first)
I also was stupidly running the upgrade from a virtual disk mounted within the machine, switched to using the file attached to the virtual drive
Currently I'm failing on HyperV but I'll see how it goes disabling the HyperV virtual adapter, in the end, I succeeded without doing this
Free Space required 20gb
2 Processors
Deleted an old version of Microsoft Endpoint

For HyperV, client I think has to be Gen2

I failed several times on the most recent Server2022 Iso, but just had success with the August 2021 iso
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Sasha ASD 6 Reputation points

2022-10-26T18:28:24.833+00:00

Using ISO from Aug. 2021 was the solution for me.
Please sign in to rate this answer.
Sal Urbina 5 Reputation points

2023-03-10T04:18:48.7466667+00:00

can you please provide a link to where that can be obtained?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
DS 31 Reputation points

2022-12-08T14:57:03.91+00:00

2021 ISO also worked for me, disabled online updates, didnt change anything else. Worked the first time no drama. Everything was perfect after the upgrade. Saved me hours of work. Thanks to everyone who commented.
Please sign in to rate this answer.
Sal Urbina 5 Reputation points

2023-03-10T05:00:26.8033333+00:00

can you provide a link to where i can obtain the 2021 august iso?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

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

23 answers

Your answer