search

virtio-win / virtio-win-guest-tools-installer

122 stars 19 forks source link

Unable to install guest tools v0.1.262 #64

Open Taomyn opened 3 months ago

Taomyn commented 3 months ago

Describe the bug On a test machine running guest tools v0.1.248, I am unable to install, it fails and rolls back

To Reproduce Run installer from: virtio-win-0.1.262-1/virtio-win-guest-tools.exe

Expected behavior Clean installation

Host:

Guest:

Additional context

Same happens with same version .MSI installer

Virtio-win-guest-tools_20240806094248_000_virtio_win_gt_x64.msi.log

Virtio-win-guest-tools_20240806094248.log

setupapi.dev.log

vrozenfe commented 3 months ago

@Taomyn Let me check it. Thanks. Vadim.

mac-linux-free commented 3 months ago

same on my side...thank you

wsycqyz commented 3 months ago

PVE7.4,Windows11 Guest virtio-win version: 0.1.248->262 also see the issue.

alexus-m commented 3 months ago

Hello! The same issue with update 0.1.248->262 and for clean install of 0.1.262 Guest OS: Windows 10 Enterprise 2021 LTSC Both ./virtio-win-0.1.262/virtio-win-gt-x64.msi ./virtio-win-0.1.262/virtio-win-guest-tools.exe rolled back. Log record is attached. virtio-win-0.1.262.failed.txt

HurinSteadfast commented 3 months ago

As alexus-m points out. The same error occurs even on a clean, new VM with no prior virtio-win presence (other than the storage driver being installed during the Windows setup process).

vrozenfe commented 3 months ago

thanks a lot. can you please give a try to the new build available at https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.262-2/

Sorry for any inconvenience. The virtio-win installed is under some reconstruction. So please let us know if you see any regressions or other problems.

Cheers, Vadim.

tuxmaster5000 commented 3 months ago

Yes, 0.1.262-2 will fix the error message, but now no drivers will be installed.

vrozenfe commented 3 months ago

@tuxmaster5000

Strange. Can you please post setupapi.dev.log file?

Thanks, Vadim.

tuxmaster5000 commented 3 months ago

@vrozenfe where can I found it? And for the virtscsi driver I have to update it manual, because the installer will install the version from 2023.

vrozenfe commented 3 months ago

@tuxmaster5000 it can be found under c:\Windows\INF directory https://learn.microsoft.com/en-us/windows-hardware/drivers/install/setupapi-device-installation-log-entries

Can yo tell me if that vioscsi driver is operating on the system or data volume? Thanks, Vadim.

tuxmaster5000 commented 3 months ago

Hi @vrozenfe the vioscsi driver is used for the OS volume. After looking for the other drivers, also the video driver was not replaced. After install it was an release from 2019. After manual update from the iso, it was from 2020. (The QXL OD one) Here are the log:

tuxmaster5000 commented 3 months ago

GH reject the log file :( also zipped :(

tuxmaster5000 commented 3 months ago

Now :) Rename and Zip setupapi.zip

alexus-m commented 3 months ago

thanks a lot. can you please give a try to the new build available at https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.262-2/

Fresh complete installation of virtio-win-0.1.262-2 via virtio-win-guest-tools.exe on new Win10 VM successfully done.

Taomyn commented 3 months ago

I tried the .exe installer to upgrade from .248 on Windows Server 2022, it still fails. The setupapi.dev.log file did not have any new entries, but I have attached the installer logs.

Virtio-win-guest-tools_20240807112709_000_virtio_win_gt_x64.msi.log Virtio-win-guest-tools_20240807112709.log

Also:

image

Not useful when notepad.exe is not installed, perhaps it could use file associations when attempting to open the log?

myssv commented 3 months ago

thanks a lot. can you please give a try to the new build available at https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.262-2/

Fresh complete installation of virtio-win-0.1.262-2 via virtio-win-guest-tools.exe on new Win10 VM successfully done.

Also not for me:

Virtio-win-guest-tools_20240807121657.log

vrozenfe commented 3 months ago

Guys, can I ask you to try running the MSI in verbose mode and upload the resulting log files It can be done by running the following command from elevated command prompt: "msiexec /i virtio-win-gt-x64(x86).msi /l*v install.log"

The qemu command lines are also welcome.

Sorry again for the troubles. Vadim.

Taomyn commented 3 months ago

Guys, can I ask you to try running the MSI in verbose mode and upload the resulting log files It can be done by running the following command from elevated command prompt: "msiexec /i virtio-win-gt-x64(x86).msi /l*v install.log"

Here you go. Not sure about the qemu command you want as I am running my VMs on Proxmox.

install-262.log

iq2luc commented 3 months ago

Same issue on Windows 11 Pro (Microsoft Windows [Version 10.0.22631.2428]) guest and Archlinux (kernel 6.10.3 / qemu 9.0.2) host. Still not working with the latest virtio-win-0.1.262-2 (from https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.262-2).

Also tried to uninstall old version (0.1.248) first (Windows add / remove programs): TryingToRemoveOldVersion

Installing the new version (0.1.262-2) I get the following error and log file: TryingToInstallNewVersion Virtio-win-guest-tools_20240807140345.log

Thank you, L.

P.S.: See the next post for a detailed installation log.

iq2luc commented 3 months ago

Attached a detailed (verbose) log for the installation process: verbose-logging-install-0-1-262.log

santiagobiali commented 3 months ago

Using "virtio-win-0.1.262-2":

DIFXAPP: ERROR 0x2 encountered while opening persistent-info key for component '{824217E9-568A-403A-82E1-408171BDB05B}'
DIFXAPP: UninstallDriverPackages failed with error 0x2

"msiexec /i virtio-win-gt-x64.msi /l*v install.log" virtio-win-gt-x64_20240807081429.log

Virtio-win-guest-tools_20240807075518.log

Host:

Guest:

alexus-m commented 3 months ago

can you please give a try to the new build available at https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.262-2/

Successfully updated including drivers 0.1.248->262 on Windows 10 Pro for Workstations 22H2

myssv commented 3 months ago

msiexec /i virtio-win-gt-x64(x86).msi /l*v install.log

install.log

DmDS commented 3 months ago

install262-2.log

iq2luc commented 3 months ago

Clean install on Windows 11 guest works OK for me using https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.262-2 (failed when using https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.262-1).

Updating from 0.1.248 fails with both (as mentioned in the posts above).

myssv commented 3 months ago

From my point of view it is not an error with the new version.

I also got an error trying to uninstall the 0.1.248.

uninstall.log

iq2luc commented 3 months ago

From my point of view it is not an error with the new version.

I second that, it certainly looks so (at least for 0.1.262-2).

Laurent-1971 commented 3 months ago

Hello, same problem for me (0.1.262-1 or 0.1.262-2) on Windows Server 2022 machines Error is when the package try to update balloon driver

MSI (s) (4C:C8) [13:07:51:944]: Executing op: ActionStart(Name=MsiUninstallDrivers,,)
Action 13:07:51: MsiUninstallDrivers. 
MSI (s) (4C:C8) [13:07:51:960]: Executing op: CustomActionSchedule(Action=MsiUninstallDrivers,ActionType=3073,Source=BinaryData,Target=UninstallDriverPackages,CustomActionData=2.15{824217E9-568A-403A-82E1-408171BDB05B}6Virtio-win-driver-installerRed Hat, Inc.)
MSI (s) (4C:4C) [13:07:51:960]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI2E4.tmp, Entrypoint: UninstallDriverPackages
DIFXAPP: UninstallDriverPackages()
DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.
DIFXAPP: 'CustomActionData' property 'UI Level' is 5.
DIFXAPP: 'CustomActionData' property 'componentId' is {824217E9-568A-403A-82E1-408171BDB05B}.
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 '{824217E9-568A-403A-82E1-408171BDB05B}'
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 13:07:51: InstallFinalize. Return value 3.
Taomyn commented 3 months ago

Does anyone know how to remove the 0.1.248 version? On my Server 2022 machine I tried to do a repair to fix the balloon driver not starting, I tried a repair which seemed to complete and rebooted, but now it's complete gone - trying anything else with the 0.1.248 MSI file always fails with a rollback.

Update I was fortunate that the ballooning drivers/service files were still present and even though the driver was still enabled and loaded, the service config was gone, so that didn't get rolled back. So I fixed that by manually creating it again using "sc" from the command-line and getting the parameters from another machine.

vrozenfe commented 3 months ago

@Taomyn By any chance, did you inflate balloon before uninstalling. Technically the balloon driver designed to deflate itself on unload, but it might be some bug that we didn't trigger yet.

Taomyn commented 3 months ago

@Taomyn By any chance, did you inflate balloon before uninstalling. Technically the balloon driver designed to deflate itself on unload, but it might be some bug that we didn't trigger yet.

No, I didn't do anything but attempt the installs

ivanmara555 commented 2 months ago

I have the same issue with update 0.1.240->0.1.262-2 rolled back with Error 0x80070643 After manually uninstall 0.1.240 and install 0.1.262-2 rolled back with Error 0x80070643 But for clean OS install of 0.1.262-2 everything Ok.

Guest OS: Windows 10 Enterprise 2021 LTSC [Version 10.0.19044.4780] Both ./virtio-win-0.1.262/virtio-win-gt-x64.msi ./virtio-win-0.1.262/virtio-win-guest-tools.exe

Log record is attached.

Virtio-win-guest-tools_20240819145907_virtio-win-guest-tools.log

geotekberlin commented 2 months ago

Same Problem here. Updating the x64 VirtIO Drivers from 240 to 262-2 on a German Windows 2022 Standard Server, the installation failed and said it had rolled back. However, in the list of installed programs, VirtIO 262 was still shown as being installed, and the network card disappeared from the windows network and never came back. So it appears that not only the upgrade process doesn't work and kills the network connections, the rollback is broken as well.

Manual uninstalling 262 did not remove the entry from the list of installed programs, not even after a reboot. Reinstalling 240 failed, saying that a newer version was already installed.

As it was impossible to roll back to 240 or install a working 262 version, ended up restoring the VM from backup,

This driver installation seems to be badly broken and IMO it should be withdrawn to prevent more damage.

tuxmaster5000 commented 2 months ago

@geotekberlin The networking problem have I also seen on many win 10 systems. After an reboot the adapter will often shown as "...#2" but lose it's configuration.

Crash1602 commented 2 months ago

I have the same issue with update 0.1.240->0.1.262-2 rolled back with Error 0x80070643 After manually uninstall 0.1.240 and install 0.1.262-2 rolled back with Error 0x80070643 But for clean OS install of 0.1.262-2 everything Ok.

Guest OS: Windows 10 Enterprise 2021 LTSC [Version 10.0.19044.4780] Both ./virtio-win-0.1.262/virtio-win-gt-x64.msi ./virtio-win-0.1.262/virtio-win-guest-tools.exe

Log record is attached.

Virtio-win-guest-tools_20240819145907_virtio-win-guest-tools.log

I have the same issue on three Windows 10 LTSC VMs. No matter what I try, it fails.

Virtio-win-guest-tools_20240910103214.log

the-moog commented 2 months ago

Dunno if this is of any help. But I stumbled across this after just installing 262 (not the -2 patch version) on Win10 22H2 without any issues (actually trying to fix another issue - blank screen on a PCI pass-through). Perhaps related? Is there perhaps something I can check to see why it is working here and other are having issues?

willmcginnis commented 1 month ago

Dunno if this is of any help. But I stumbled across this after just installing 262 (not the -2 patch version) on Win10 22H2 without any issues (actually trying to fix another issue - blank screen on a PCI pass-through). Perhaps related? Is there perhaps something I can check to see why it is working here and other are having issues?

Might be specific to Server and LTSC. I'm about to a fresh install on Windows 11 Pro and Windows 11 LTSC IoT on Proxmox 8.2.6 and will see if this happens.

willmcginnis commented 1 month ago

The drivers seem to install fine on Windows 11 LTSC IoT but the guest agent service is not installed. Even after multiple "repair" installs of the exe and running the ga msi. Running the ga msi with "uninstall" then "install" did seem to install the agent, which can then be set from "manual" to automatic. Notably the VSS service was installed and set to manual.

Taomyn commented 1 month ago

Any progress on this issue? I see that 0.1.262-2 has been moved to stable, but it doesn't help those of us with machines stuck on earlier builds that will not upgrade or even uninstall.

vrozenfe commented 1 month ago

@Taomyn

Next week we are giving this issue another go and will do our best to get it sorted.

Best regards, Vadim.

Directox01 commented 1 month ago

@vrozenfe Hello, please verify if you are using the CD on SCSI or IDE. I think SCSI Is causing the issue

bbeata commented 1 month ago

+1 for bringing this issue back up. I have two production machines that the balloon service will not start and I cannot roll back. .262 - 2 just fails on install.

TineUser commented 3 weeks ago

I've got the same issue on two Win 10 22H2 systems. With .248 everything was OK but update to .262 results in rollback.

bbeata commented 3 weeks ago

@vrozenfe ??

vrozenfe commented 3 weeks ago

We are still working on this issue. As for now, it looks as most of 262-2 install cases failed because of the following issue:

DIFXAPP: ERROR 0x2 encountered while opening persistent-info key for component '{824217E9-568A-403A-82E1-408171BDB05B}' DIFXAPP: UninstallDriverPackages failed with error 0x2

which happens when uninstalling the previous version. This issue was mentioned by several people in this thread and can be found in many log files shared with us.

This issue seems to be similar to https://github.com/virtio-win/virtio-win-guest-tools-installer/issues/33 And might be caused by DIFx , at least the very similar issues was reported by several other sources like https://sourceforge.net/p/wix/mailman/message/26729446/ for example.

Technically, the virtio-win installer executes "RemoveExistingProducts" actions before installing a new set of binaries. So, if this action fails then no new drivers will be installed.

What we can do as a workaround is try to uninstall the previous version of virtio-win manually, reboot VM, and then try to install the new virtio-win version. If the uninstall fails for some reason then try to run virtio-win msi repair (not the bundle) . If the repair cannot fix the problem and there is still a problem to uninstall the previous version of virtio-win, then we can try to rebuild that missing DIFx component Registry key manually and try again to uninstall the old version of virtio-win msi.

Vadim.

myssv commented 3 weeks ago

try to run virtio-win msi repair (not the bundle)

Can you explain how to do this? Starting the MSI paket und press "Repeair"?

A manual uninstall failed also here.

Taomyn commented 3 weeks ago

@vrozenfe on my test Win11 VM, I mounted the .248 ISO and used the MSI to attempt a repair, it went through and asked for a reboot. After that I switched to the .262 ISO tried to use the guest installer and it failed again, as did running the newer MSI installer.

So how do we rebuild the DIFx component in the registry?

vrozenfe commented 3 weeks ago

try to run virtio-win msi repair (not the bundle)

Can you explain how to do this? Starting the MSI paket und press "Repeair"?

Correct. There are two ways to install virtio-win drivers - by installing virtio-win-gt-x86/x64.msi or by running virtio-win-guest-tools.exe bundle. Both of them have "Repair' function but only msi repairs the installed drivers.

A manual uninstall failed also here.

TineUser commented 3 weeks ago

Repair doesn't work for me.

I can confirm that the installation of VirtIO-Win .262 is working fine on newly installed VMs.

vrozenfe commented 3 weeks ago

@vrozenfe on my test Win11 VM, I mounted the .248 ISO and used the MSI to attempt a repair, it went through and asked for a reboot. After that I switched to the .262 ISO tried to use the guest installer and it failed again, as did running the newer MSI installer.

So how do we rebuild the DIFx component in the registry?

@tuxmaster5000

Can you please dump to files and share the following Registry keys ? HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DIFx ,and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DIFxApp

Thanks, Vadim.