RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1697760 [details]
tool install logs

Description of problem:
Install/uninstall doesn't always prompt to reboot machine, we need to always ask for a reboot to be on the safe side


How reproducible:
100%

Steps to Reproduce:
1.boot up windows guest.
2.try to install/uninstall virtio driver, spice and qemu-guest-agent via virtio-win-guest-tools.exe.


Actual results:
There is no hint to reboot the machine, install log is in attachment.

Expected results:
Better to ask for a reboot after install/uninstall.

Created attachment 1763602 [details]
setupapi.dev.log

Reopen it according to comment5

I still have doubts that we need to force a system reboot after successful device drivers installation
or update action.
https://docs.microsoft.com/en-us/windows-hardware/drivers/install/device-installations-and-system-restarts

However, living it to Martin and Amnon to comment on this issue.

The problem mentioned at https://bugzilla.redhat.com/show_bug.cgi?id=1847856#c5 needs to be investigated
as a separate issue.

Best regards,
Vadim

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.