question

DavidYorkshire-8836 avatar image
0 Votes"
DavidYorkshire-8836 asked ElevenYu-MSFT answered

Hyper-V Server 2016 to 2019 in-place upgrade failing

I have a test server (Dell Poweredge R710) running the free Hyper-V Server 2016. It's a very simple standalone setup - no shared storage (although it is domain-joined).

I am trying to do an in-place upgrade to Hyper-V Server 2019 - I'm shifting all our Servers to 2019, and it would make things easier for patching, etc, if this one was on the same version. When I run the installer from the command line it fails, and looking at the log file shows this as the cause:

<CompatibilityInfo BlockingType="Hard"/><Message Text="You have the Remote Desktop Virtualization Host (RDVH) role installed on this server. After you upgrade, you won’t be able to add the RemoteFX 3D video adapter to virtual machines."/>

It's just a test server running the standalone VMs I use for trying things out, so it's not a, RDVH host, and RemoteFX is not used or relevant.

Anyone know how to get around this? I could of course do a clean install but that's extra hassle.

Thanks

windows-server-2019windows-server-2016windows-server-hyper-v
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

The much simpler / safer method is to export / copy the VHDs to removable, clean install the new OS, patch fully, add hyper-v role, import virtual machines.

--please don't forget to upvote and 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.

DavidYorkshire-8836 avatar image
0 Votes"
DavidYorkshire-8836 answered

Hi,

Yes, I could do but as I say it's only a test server so I'd rather go with the quicker / easier upgrade option if possible - if the VMs get broken it isn't a major issue.

Thanks

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 then, I'd check the logs for clues.
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--


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.

DavidYorkshire-8836 avatar image
0 Votes"
DavidYorkshire-8836 answered

It's the RDVH role issue - which apparently was included in Hyper-V Server 2016 but not 2019. What I don't know is how to get around that (the role is not needed).

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

Probably the work-around is to clean install it.

--please don't forget to upvote and 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.

DavidYorkshire-8836 avatar image
0 Votes"
DavidYorkshire-8836 answered DavidYorkshire-8836 edited

Well yes, I could do that - but if that has been my first choice I wouldn't have asked the question on here...

Hence if anyone does have a workaround (which doesn't involve clean installing) it would be useful to know.

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, there likely isn't another option. You can also start a case here with product support.
https://support.serviceshub.microsoft.com/supportforbusiness

--please don't forget to upvote and 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.

DavidYorkshire-8836 avatar image
0 Votes"
DavidYorkshire-8836 answered

Prodcut support requires a paid for plan.

I'm unsure why you have replied at all to be honest as you don't appear to have any suggestions other than clean install - which as I said in my original post I can do if I have to but would rather avoid.

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 then.


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.

ElevenYu-MSFT avatar image
0 Votes"
ElevenYu-MSFT answered DavidYorkshire-8836 commented

Hi,

Thank you for posting your issue to Q&A forum.

Since you find the issue seems related to RDVH role, have you confirmed if the role is installed or not in your hyper-v server 2016?

Please run PowerShell Command "Get-WindowsFeature | Where Installed" to check the installed roles on the server.

If RDVH role is in the installed list, you can try to remove the role and see if the issue could be resolved or not.

PowerShell Command: Uninstall-WindowsFeature -Name RDS-Virtualization -Restart

For your reference:
To remove roles and features by using the Uninstall-WindowsFeature cmdlet


Thanks,


If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

· 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.

Thanks. Yes, it is installed - I assume that it must be part of the default install as I didn't manually install it. I will try removing it.

0 Votes 0 ·

You can have a try and share the result. Thanks.

0 Votes 0 ·

Role removed OK, and installer ran this time. However, it failed towards the end of the first percentage screen with a non-helpfil error message (Windows Server 2019 installation has failed).

Any idea which logs I need to look at to find the cause?

Thanks

0 Votes 0 ·

OK, found some logs in C:\Windows\panther\newOs\panther

setupact.log has the following entries from the failure time - I can't see from this what the issue is.

2021-07-26 14:56:18, Error MOUPG CSetupHost::Execute(408): Result = 0xC1900220
2021-07-26 15:27:10, Info MOUPG CInstallUI::ShowExitingSetup: Posted MSG_INSTALLUI_SWITCH_TO_PROGRESS_PAGE
2021-07-26 15:27:10, Info MOUPG CInstallUI::Quit: Posted MSG_INSTALLUI_FORCE_QUIT
2021-07-26 15:27:10, Info MOUPG CInstallUI::CInstallUIMessageWindow::SwitchToProgressPage
2021-07-26 15:27:10, Info MOUPG CInstallUI::SwitchToProgressPage
2021-07-26 15:27:10, Info MOUPG CInstallUI::CInstallUIMessageWindow::ForceQuit
2021-07-26 15:27:10, Info MOUPG Force ending Message pump
2021-07-26 15:27:10, Info MOUPG CInstallUI::ExitInstance
2021-07-26 15:27:10, Info CONX Uninitializing compatibility provider wsc:setup:...
2021-07-26 15:27:10, Info CONX Uninitializing compatibility provider wsc:wica:...
2021-07-26 15:27:10, Info CONX Uninitializing compatibility provider wsc:plugin:...
2021-07-26 15:27:10, Info MOUPG SetupUI: Calling PowerClearRequest with type [0x1]...
2021-07-26 15:27:10, Info MOUPG SetupUI: Power request cleared!
2021-07-26 15:27:10, Info MOUPG SetupHost Logging End

0 Votes 0 ·