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
An in-place upgrade can be problematic and is never recommended. Better option is a clean install, patch fully, migrate roles over. You can check the logs for additional details.
https://docs.microsoft.com/en-us/troubleshoot/windows-client/deployment/windows-setup-log-file-locations
--please don't forget to upvote and Accept as answer if the reply is helpful--
While your warning is technically "valid", in response to the question asked, it's unhelpful. When someone explains they're having trouble doing a Windows upgrade (which Microsoft and Windows do allow admins to do, for good reason), "you shouldn't be doing that" just comes across as dismissive, especially before asking why they're doing an upgrade instead of a fresh install. I have been upgrading my Windows OSes my entire life, and, fortunately, aside from some small snags here and there, my upgrades have saved me countless hours of time. Like many people, time is something I never have enough of, so I value mine greatly. For the average configuration, despite the warnings about upgrading, I've found that Microsoft actually tends to do a pretty good job of making Windows upgrades work very well, and that seems to have gotten better with every release. In fact, I'm pretty sure (try not to gasp) that I upgraded my main PC all the way from Windows 95 to Windows 10 (even moving it to different hardware), and have several servers that have gone through 4 or 5 Windows Server version upgrades, and continue to work beautifully. Since an upgrade takes FAR less time than doing a fresh OS install, and reinstalling and reconfiguring every single component and app on that machine, those of us who don't have hours of time to do full re-installs on our workstations and/or servers have really good reasons to go the upgrade route, instead.
It is a on-prem machine, so it will be difficult, but I will look in the logs.
Sounds good, you're welcome; a simpler solution may be to clean install, patch fully, migrate roles over and move on.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
List any of these installed non-Microsoft software:
a) antivirus
b) firewall
c) drive encryption
Run setupdaig > post a share link into this thread
https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag
Post commands with results for these administrative command prompt commands:
sfc /scannow
dism /online /cleanup-image /restorehealth
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\desktopsfcdetails.txt
findstr /c:"conx" c:\$windows.~bt\sources\panther\setupact.log >"%userprofile%\desktop\setupactdetails.txt"
copy %windir%\logs\cbs\cbs.log "%userprofile%\desktop\cbs.txt"
Find the new text files on the desktop and post share links into this thread.
.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.
On the bottom of each post there is:
Propose as answer = answered the question
On the left side of each post: Vote = a helpful post
.
.
.
.
.
Hello,
Due to the error that you receive it looks like the system that you are applying contains binaries that are older than the Kernel of your system (superseeded). Please ensure that you are downloading the latest ISO version available from a Microsoft official source.
Regards,
I am downloading the ISO from Azure for Education site, so I don't really have a choice. Unless you know an official repository with the newest ISO that is publicly available.
I just ran into the same error on a VM attempting to upgrade from 2019 to 2022. The VM only runs some basic routing and remote access roles and was created fairly recently.
I'm having the same issue on a server also running RRAS, if by any luck you've got an answer...
Thanks
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]
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.
I have the exact same issue / error has @Mike-2930 but ticking Not Right Now on the update during the setup does not resolve the issue and the upgrade fails.
I don't have CMAK (RAS Connection Manager Administration Kit) installed on the server and I've also tried delating all of the profiles within the registry, except the local admin account that I'm using. No luck!
Any one else have any other suggestions?
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\DUImageSandbox*Microsoft-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.
I had the same error. I disabled the NICs on this machine, and was able to proceed with the upgrade. Hopefully this helps others.
I have got a different error 0xC1900101 - 0x20017 (A driver has caused a problem) when trying to do an in-place upgrade from Windows Server 2019 to Windows Server 2022 in a domain environment. Updated all device drivers to the latest still getting that error code and your method to disable NICs does the trick. Able to upgrade to Windows 2022 successfully without problem and after the restart the main NIC automatically enable back.
How did you get to know has to disable NICs to get the upgrade works? Anyway, thanks for the method.
Thank you! This helped me. After I disabled the NIC in Device Manager I was able to run the upgrade again without problem and then re-enabled after the upgrade.
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"
22 people are following this question.
