question

65614808 avatar image
0 Votes"
65614808 asked SimonGRAMAINPerso-7438 answered

0xc1900101 - 0x20017 windows server 2016 14393, cant in-place upgrade Windows Server 2019

Hello everyone!
Windows Server 2016 14393
I'm trying to upgrade to 2019, but I get error 0xC1900101 - 0x20017 ERROR in the SAFE_OS phase
This is a VMWare virtual machine
memory, hard disk space is sufficient.

log file:
https://yadi.sk/d/x1SlPO1kU1IpOg90577-setuperr.log

90539-image.png


windows-server
image.png (23.2 KiB)
setuperr.log (21.5 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DSPatrick avatar image
0 Votes"
DSPatrick answered DSPatrick commented

In-place upgrades are never recommended, better option is to clean install it, patch fully, migrate roles over.
https://docs.microsoft.com/en-us/troubleshoot/windows-client/deployment/windows-setup-log-file-locations

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


· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

In place upgrade repairs work well for Windows 10.

Please post references so readers can read why they are not recommended for server 2016.
If it is the same / different for server 2012 and server 2019 please post additional references.

0 Votes 0 ·

The issues with doing in-place upgrades can be problematic (which you have found out) and are long well known by most IT professionals. If further assistance is needed I'd suggest starting a case here with product support.
https://support.serviceshub.microsoft.com/supportforbusiness

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


0 Votes 0 ·

it is clear that migration is always better than an in-place upgrade

But this is an application server, there are no infrastructure roles on it (IIS only)

Why do we need WINDOWS 2019?

There are application servers for WS 2016 (about 40), the TermServices Session host role is used - but the license is available for WS 2019

The environment is virtualized. Migrate each virtual machine longer than in-Place Upgrade

Such situation:
Previously, 2 virtual machines were cloned, Sysprep was dropped, etc.
one virtual machine was successfully updated to WS 2019, while the other got an error. Here's a paradox

If necessary, I can pull out the logs and so on, tell me where to dig for In -place Upgrade

0 Votes 0 ·
Show more comments
Docs-4663 avatar image
0 Votes"
Docs-4663 answered 65614808 commented

If there are references please post.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Debugging windows log is beyond scope of forums support so if further assistance were needed you could open a request ticket with Microsoft support. Thanks for your understanding.
https://support.serviceshub.microsoft.com/supportforbusiness

0 Votes 0 ·

Good day!

Thanks for the answer.

Is this a paid service / support?

0 Votes 0 ·
65614808 avatar image
0 Votes"
65614808 answered

91954-%D1%81%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA.jpg




I found this error.
Tried to fix it but failed yet.
Moreover, the system is being updated, for example, having this error - I have already updated to Cumulative \ Servicing Update 2016 2021-04.
Tried to fix it, wrote sc config start = auto on wuauserv bits cryptsvc trustedinstaller services
restarted services and renamed the softWareDistributionion and catroot folders
checked through powershell Repair-WindowsImage -Online -Checkhealth and Scanhealth - showed that there are no errors


снимок.jpg (61.8 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

TeemoTang-MSFT avatar image
0 Votes"
TeemoTang-MSFT answered

Yes, log analysis belongs to paid service.
I still suggest to clean install rather than spend time on troubleshooting in-place upgrade.
In fact, since Windows 10/Server 2016 released, upgrade processes are essentially a clean-install, and then migrate data. It's actually quite a sweet technique they're moving towards where it's almost like partition-based installs but with the same registry/data/programs folders.


If the Answer is helpful, please click "Accept Answer" and upvote it.
Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DSPatrick avatar image
0 Votes"
DSPatrick answered

Any progress or updates?

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


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

65614808 avatar image
0 Votes"
65614808 answered

I apologize for the long absence, there were holidays.
I did not solve the problem, I was busy with another.
Decided to migrate to a clean installation WS 2019
I partially updated it in place and transfer part of it by migration, but I could not find a solution

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DSPatrick avatar image
0 Votes"
DSPatrick answered

Sounds good, clean install is always a better option.

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


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SimonGRAMAINPerso-7438 avatar image
0 Votes"
SimonGRAMAINPerso-7438 answered

We encountered exactly the same error during a W2012R2 to W2019 In-Place Upgrade of a VMWare Virtual Machine
We solve the issue by upgrading the VMWare VM version. For W2019 it must be 11 or higher. Our VMware VM was version 9 ...
It is very quick and easy to upgrade VMWare VM version but, this need a VM shutdown. It cannot be transparent to users ...

Use VMWare VSphere client
Search the VM you want to upgrade and click on it
Among others infos you get the VM version
Right clic on the VM and Shutdown it .
When Shutdowned, Right clic on the VM and chose: "Upgrade Virtual Hardware"
You get an advice explaining that it is an important change that cannot be rollback ! Be sure to have a valid Snapshot before proceed.
Select YES and the VM version instantaneously change to 11
Restart the VM and you can successfully In-Place Upgrade it.

Hope that would be helpfull for some people. Have a nice day

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.