virtio-win-0.1.217 and Windows 10 :-(

Spoonman2002

Member
Jul 6, 2021
61
9
8
50
Holland
When I did an update on my Windows 10 vm (virtio-win-0.1.215 to virtio-win-0.1.217),
the installation did a "rollback". It failed to install virtio-win-0.1.217.....
So I thought I could happily continue to run with virtio-win-0.1.215.
However...... my Windows 10 vm had no virtio drivers whatsoever.
And reinstalling virtio-win-0.1.215 did not do the trick.
I had to manually remove ALL virtio drivers and folders, reboot and do a fresh installation
with virtio-win-0.1.215.
Is virtio-win-0.1.217 not for Windows 10 but for Windows 11 ?
 
  • Like
Reactions: Mihai
Aug 19, 2021
5
1
3
I experienced similar problems on different Windows 10 prof. machines (German version).
When I tried to update from 0.1.215 to 0.1.217 via the virtio-win-guest-tools.exe I consistently get an error
"0x80070643: Failed to install MSI package". In one of my Win10 machines I had to manually re-add the NetKVM network adapter.
(attached files W10-de- ...)

In a Windows 11 prof. machine the network adapter disappeared too, I had to re-add it manually.
In addition, yellow exclamation marks are newly set for:
VSP für die Microsoft Hyper-V NT-Kernel-Integration
Der Gerätetreiber für diese Hardware kann nicht initialisiert werden (Code 37). Objekt wurde nicht gefunden. (driver not found)
Microsoft Hyper-V-Busanbieter für virtuelle Computer
Der Gerätetreiber für diese Hardware kann nicht initialisiert werden (Code 37). Die Anforderung wird nicht unterstützt. (driver not supported)
(attached files W11-de- ...)

I then created a fresh Windows 10 21H2 x64 machine with en-us-language and German language support using fresh drivers from virtio 0.1.217.
It started well. But when I tried to run the virtio-win-guest-tools.exe I again got the error 0x80070643.
In addition the NetKVM adapter disappeared as well as the balloon driver and the virtio-serial-driver. Manual reinstallation worked for 0.1.217.
(attached files W10-fresh-enus-...)


The relevant passages to me seem to be:

Windows 10:
Property(S): PackageCode = {166171F6-9ABF-4CFA-9D48-6E5DED8D2BB1}
Property(S): MsiLogFileLocation = C:\Users\user\AppData\Local\Temp\Virtio-win-guest-tools_20220418120603_000_virtio_win_gt_x64.msi.log
MSI (s) (60:54) [12:07:05:013]: MainEngineThread is returning 1603
MSI (s) (60:F4) [12:07:05:014]: RESTART MANAGER: Session closed.
MSI (s) (60:F4) [12:07:05:016]: RESTART MANAGER: Session closed.
MSI (s) (60:F4) [12:07:05:016]: No System Restore sequence number for this installation.
MSI (s) (60:F4) [12:07:05:017]: User policy value 'DisableRollback' is 0
MSI (s) (60:F4) [12:07:05:017]: Machine policy value 'DisableRollback' is 0
MSI (s) (60:F4) [12:07:05:017]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (60:F4) [12:07:05:017]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (60:F4) [12:07:05:018]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (60:F4) [12:07:05:019]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (60:F4) [12:07:05:019]: Destroying RemoteAPI object.
MSI (s) (60:D0) [12:07:05:019]: Custom Action Manager thread ending.
MSI (c) (78:0C) [12:07:05:020]: Back from server. Return value: 1603
MSI (c) (78:0C) [12:07:05:020]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (78:0C) [12:07:05:020]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'.
Action ended 12:07:05: ExecuteAction. Return value 3.
MSI (c) (78:0C) [12:07:05:020]: Doing action: FatalError
MSI (c) (78:0C) [12:07:05:020]: Note: 1: 2205 2: 3: ActionText
Action 12:07:05: FatalError.
Action start 12:07:05: FatalError.
Action 12:07:05: FatalError. Dialog created
Action ended 12:13:35: FatalError. Return value 2.
Action ended 12:13:35: INSTALL. Return value 3.
Property(C): UpgradeCode = {05294E2F-7778-4E46-B2A3-CF039D5767C8}
Property(C): REGISTRY_PRODUCT_NAME = Windows 10 Pro
....
Property(C): PackageCode = {166171F6-9ABF-4CFA-9D48-6E5DED8D2BB1}
Property(C): MsiLogFileLocation = C:\Users\user\AppData\Local\Temp\Virtio-win-guest-tools_20220418120603_000_virtio_win_gt_x64.msi.log
=== Logging stopped: 18.04.2022 12:13:35 ===
MSI (c) (78:0C) [12:13:35:625]: Note: 1: 1708
MSI (c) (78:0C) [12:13:35:625]: Note: 1: 2205 2: 3: Error
MSI (c) (78:0C) [12:13:35:625]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708
MSI (c) (78:0C) [12:13:35:625]: Note: 1: 2205 2: 3: Error
MSI (c) (78:0C) [12:13:35:625]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (c) (78:0C) [12:13:35:625]: Product: Virtio-win-driver-installer -- Installation failed.

MSI (c) (78:0C) [12:13:35:625]: Windows Installer installed the product. Product Name: Virtio-win-driver-installer. Product Version: 0.1.217. Product Language: 1033. Manufacturer: Red Hat, Inc.. Installation success or error status: 1603.

MSI (c) (78:0C) [12:13:35:626]: Grabbed execution mutex.
MSI (c) (78:0C) [12:13:35:626]: Cleaning up uninstalled install packages, if any exist
MSI (c) (78:0C) [12:13:35:627]: MainEngineThread is returning 1603
=== Verbose logging stopped: 18.04.2022 12:13:35 ===


Windows 11:
DIFXAPP: UninstallDriverPackages()
DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.
DIFXAPP: 'CustomActionData' property 'UI Level' is 5.
DIFXAPP: 'CustomActionData' property 'componentId' is {7E770B97-A137-4350-837D-A562CEB878AC}.
DIFXAPP: 'CustomActionData' property 'flags' is 0x6.
DIFXAPP: 'CustomActionData' property 'ProductName' is Virtio-win-driver-installer.
DIFXAPP: 'CustomActionData' property 'ManufacturerName' is Red Hat, Inc..
DIFXAPP: ERROR 0x2 encountered while opening persistent-info key for component '{7E770B97-A137-4350-837D-A562CEB878AC}'
DIFXAPP: UninstallDriverPackages failed with error 0x2
DIFXAPP: RETURN: UninstallDriverPackages() 2 (0x2)
CustomAction MsiUninstallDrivers returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 14:22:09: InstallFinalize. Return value 3.
MSI (s) (40:80) [14:22:09:747]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 14:22:09: INSTALL. Return value 3.

Any help is appreciated.
 

Attachments

  • W10-de-Virtio-win-guest-tools_20220418120603.log
    18.3 KB · Views: 7
  • W10-fresh-enus-Virtio-win-guest-tools_20220420175551_000_virtio_win_gt_x64.msi.log
    652.9 KB · Views: 2
  • W11-de-Virtio-win-guest-tools_20220419140826.log
    22 KB · Views: 1
  • W11-de-Virtio-win-guest-tools_20220419140826_000_virtio_win_gt_x64.msi.log
    1,004.3 KB · Views: 0
  • W10-de-Virtio-win-guest-tools_20220418120603_000_virtio_win_gt_x64.msi.log
    992.6 KB · Views: 0
  • W10-fresh-enus-Virtio-win-guest-tools_20220420175551_000_virtio_win_gt_x64.msi.log
    652.9 KB · Views: 2
Aug 19, 2021
5
1
3
103 conf file of the Windows 11 machine
102 conf file of the Windows 10 fresh enus machine
109 conf file of the Windows 10 de machine
 

Attachments

  • 103.txt
    1.7 KB · Views: 1
  • 102.txt
    686 bytes · Views: 2
  • 109.txt
    649 bytes · Views: 1

basanisi

Active Member
Apr 15, 2011
40
2
28
Hello the community,

I had exact same problem with fresh installed VM from windows cloud
 

LincolnHawk

New Member
Jan 1, 2022
3
0
1
47
Couldn't install virtio-win-0.1.217 guest utils on windows 11 VM , however virtio-win-0.1.215 works fine.
 

Kmob07

New Member
Jan 19, 2022
2
0
1
56
Thank you! I am surprised that the stable version would be updated with an install crash bug like this one - I appreciate the links to the legacy versions! .1.215 worked great for me (Although oddly I had to actually roll my windows VM back to a prior backup prior to the .217 install for it to work).
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!