From 7da5dfbee3b1eae7a849e07f609350bcd126a1bf Mon Sep 17 00:00:00 2001 From: JochenKorge <70751057+JochenKorge@users.noreply.github.com> Date: Thu, 26 Jan 2023 20:46:34 +0100 Subject: [PATCH] clarified need to assign specific drive letter MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit After a lot of try and error I stumbled over this. (I found the error logs on C:\) Better solution would probably be a check during install, but that´s out of my scope. --- docs/os/windows/windows-tools41.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/os/windows/windows-tools41.md b/docs/os/windows/windows-tools41.md index 59f36eb..7a65d2d 100644 --- a/docs/os/windows/windows-tools41.md +++ b/docs/os/windows/windows-tools41.md @@ -16,7 +16,8 @@ Qubes Windows Tools (QWT) are a set of programs and drivers that provide integra - Xen PV Disk Drivers: paravirtual storage drivers - Xen PV Network Drivers: paravirtual network drivers - Move user profiles: user profile directory (`C:\users`) is moved to VM's private disk backed by `private.img file` in `dom0` (useful mainly for HVM templates). - + > **Note**: If you choose to move profiles, drive letter Q: must be assigned to the secondary (private) disk. + > **Note**: Xen PV disk drivers are not installed by default. This is because they seem to cause problems (BSOD = Blue Screen Of Death). We're working with upstream devs to fix this. *However*, the BSOD seems to only occur after the first boot and everything works fine after that. **Enable the drivers at your own risk** of course, but we welcome reports of success/failure in any case (backup your VM first!). With disk PV drivers absent `qvm-block` will not work for the VM, but you can still use standard Qubes inter-VM file copying mechanisms. On the other hand, the Xen PV drivers allow USB device access even without QWT installation if `qvm-features stubdom-qrexec` is set as `1` Below is a breakdown of the feature availability depending on the windows version: