Select your VM -> Click Hardware -> Select CD/DVD Drive -> Click Edit -> Choose your storage, select spice-guest-tools-0.164.iso , and click OK .
Handles background synchronization tasks between the host machine and the virtualized guest.
| Error Message | Likely Cause | Solution | |---------------|--------------|----------| | “This installer is not compatible with this version of Windows” | Trying to install 64-bit tools on 32-bit Windows. | Download the 32-bit version ( spiceguesttools016.iso , without the 4). | | “Driver installation failed: Access denied” | UAC or group policy blocking driver installs. | Run the installer from an elevated command prompt. Disable driver signature enforcement temporarily. | | “SPICE Guest Agent service fails to start” | Missing MSVC runtime or corrupted install. | Uninstall via Control Panel, reboot, reinstall as Administrator. | | Mouse doesn't leave VM window | SPICE vdagent not running. | Check Services. If missing, reinstall and ensure “vdagent” is enabled. | | Black screen after installation | QXL driver conflict with another display driver. | Boot into Safe Mode, uninstall other graphics drivers, reinstall SPICE tools, then reboot. | spiceguesttools0164iso download install
Accept the license agreement and proceed with the installation. The installer will automatically inject the QXL graphics driver, VirtIO serial drivers, and the SPICE agent service.
virsh attach-disk <vm-name> /path/to/spice-guest-tools-0.164.iso hdc --type cdrom --mode readonly Select your VM -> Click Hardware -> Select
You cannot copy text, files, or snippets from your host machine and paste them directly into your virtualized environment.
You must expose the downloaded ISO to the Windows guest OS through your hypervisor management tool, such as Virtual Machine Manager ( virt-manager ) or Proxmox VE. Open on your host system. | Download the 32-bit version ( spiceguesttools016
Navigate to and double-click the virtual CD/DVD drive containing the SPICE tools.
Verify that the drivers are operating correctly after the virtual machine reboots: Check Device Manager