Error to install VirtIO on Windows Server 2016 Standard | Nutanix Community
Skip to main content
I tryed to run xtract but I'm facing a problem to install the VirtIO tools. Using the automatic script on xtract it's end with the error: "ExitCode: '1603'". If I try to install VirtIO manually the show this message "ended prematurely because of an error. Your system has not been modified". Creating a verbose log file, from the installation, I see some errors like this:

MSI (c) (08:18) [22:06:00:591]: Package to be registered: 'Nutanix-VirtIO-1.1.3.msi'

MSI (c) (08:18) [22:06:00:591]: Note: 1: 2205 2: 3: Error

MSI (c) (08:18) [22:06:00:591]: Note: 1: 2262 2: AdminProperties 3: -2147287038

or

Action start 22:06:00: PrepareDlg.

MSI (c) (08:50) [22:06:00:623]: Note: 1: 2205 2: 3: Error

MSI (c) (08:50) [22:06:00:623]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2898

Info 2898.For WixUI_Font_Normal textstyle, the system created a 'Tahoma' font, in 0 character set, of 13 pixels height.

MSI (c) (08:50) [22:06:00:623]: Note: 1: 2205 2: 3: Error

MSI (c) (08:50) [22:06:00:623]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2898



without any another information that I can identify the reason..

I'm trying to convert from a ESXi 6.5 into AOS 5.10.1.1 and VirtIO version 1.1.3.



Thx for any support or idea.
Check out this web-site on resolving the 1603 (lots of possibilities, sorry)



https://www.msigeek.com/715/how-to-troubleshoot-the-error-1603-fatal-error-during-installation



Also, make sure the service account has sufficient privs and the msi has not been altered (going thru A/V has done this to me).



Good luck!
Hi, this solution doesn't solve the problem.

Its related with the digital driver signature.. with this off it's possible to install the virtio and migrate the machine..
Excellent. Thanks for letting the community know!
To help all, thiis steps solved the problem and Works fine for me (2 VM Win 2016 migrated to Nutanix/AHV) this commands enable the unsigned driver installation:



Installing VirtIO drivers fails during migration with Exit Code 1603. This workaround will allow the migration to complete.

Solution

Fix can be found in the external Microsoft KB:

https://docs.microsoft.com/en-us/windows-hardware/drivers/install/the-testsigning-boot-configuration-option

The steps are:

Open the console to the VM

Open a cmd prompt as administrator

Enter the command: bcdedit /set testsigning on

Restart the VM

Verify that you can install the VirtIO 1.1.3 driver
Terms & Conditions