[WIP] Windows/QWT user reports revisions

Go back to topic: [WIP] Windows/QWT user reports

  1. v32 anchor; v32 full version
  2. v31 anchor; v31 full version
  3. v30 anchor; v30 full version
  4. v29 anchor; v29 full version
  5. v28 anchor; v28 full version
  6. v27 anchor; v27 full version
  7. v26 anchor; v26 full version
  8. v25 anchor; v25 full version
  9. v24 anchor; v24 full version
  10. v23 anchor; v23 full version
  11. v22 anchor; v22 full version
  12. v21 anchor; v21 full version
  13. v20 anchor; v20 full version
  14. v19 anchor; v19 full version
  15. v18 anchor; v18 full version
  16. v17 anchor; v17 full version
  17. v16 anchor; v16 full version
  18. v15 anchor; v15 full version
  19. v14 anchor; v14 full version
  20. v13 anchor; v13 full version
  21. v12 anchor; v12 full version
  22. v11 anchor; v11 full version
  23. v10 anchor; v10 full version
  24. v9 anchor; v9 full version
  25. v8 anchor; v8 full version
  26. v7 anchor; v7 full version
  27. v6 anchor; v6 full version
  28. v5 anchor; v5 full version
  29. v4 anchor; v4 full version
  30. v3 anchor; v3 full version
  31. v2 anchor; v2 full version

Revision #32

Edited on
2022-03-30
Edited by user
taradiddles
## Migrating Windows qubes created under Qubes R4.0 to R4.1 See [this issue](https://github.com/QubesOS/qubes-issues/issues/7088). (tl;dr; feasible but not straightforward). ## Obtaining Windows Windows ISOs can be downloaded directly from Microsoft (eg. [here](https://www.microsoft.com/en-us/software-download/windows10ISO) for Win10). Unofficial "debloated" ISOs from projects like [reviOS](https://www.revi.cc/revios) or [ameliorated](https://ameliorated.info) can be found on the net, although obviously you should consider them even "unsafer" than MS provided ISOs. Alternatively, one could download an official ISO and run scripts/apply patches before installation. Some of the "tweaks" might end up being too much depending on the qube's planned usage though (eg. no appx functionality in ameliorated windows - so the installation of Windows Store apps is impossible, even with powershell). ## Installing Windows Simple Windows install (gui based): follow the steps under "Installation procedure" in this [community guide](https://github.com/Qubes-Community/Contents/blob/master/docs/os/windows/windows-vm.md#simple-windows-install) (TODO: the guide should be updated, the "works"/"doesn't work" sections are outdated because QWT now works on R4.x). Alternatively, on R4.0 you may use @elliotkillick's [qvm-create-windows-qube](https://github.com/elliotkillick/qvm-create-windows-qube) scripts. R4.1 support is unknown (see [this issue](https://github.com/elliotkillick/qvm-create-windows-qube/issues/52)). Don't forget to `qvm-clone` your qubes from times to times. Windows being Windows, it's easy to do something that renders your windows qube unusable (eg. BSOD, boot loop, ...). Known issues: - Recent versions of Windows won't show the cdrom drive after starting the qube with `qvm-start vm --cdrom ...` (or using the gui). The [solution](https://forum.qubes-os.org/t/win-10-standalone-vm-seems-to-have-no-cdrom-drive/8645/3) is to disable hibernation in Windows with the following command in a command prompt (that command is included in QWT's setup but it's necessary to run it manually in order to be able to open QWT's setup iso/cdrom in Windows). `powercfg -H off` - Qubes OS' default qrexec timeout (60 seconds) might be too short when Windows applies updates and/or check disks. So in case you have Windows Updates enabled you might want to increase it, eg. `qvm-prefs [windows-qube] qrexec_timeout 300` ## Qubes Windows Tools (QWT) QWT works on Qubes OS R4.x thanks to the great work of @jevank et al. QWT's main features are: - copy/paste between qubes - copy files between qubes - attaching USB devices to the qube - attaching block devices to the qube (XEN PV disk driver must be installed) - automatically set up networking - automatically set up time/clock synchronization - XEN PV drivers (some of them optional) - optional user migration from `c:` to the qubes' private volume (to be able use the qubes as a TemplateVM). - seamless mode (win7 only for now) - propagating keyboard layout ? Changelog/commits are [here](https://github.com/tabit-pro/qubes-windows-tools-cross/commits/master). Compiled rpm/iso are available [here](https://github.com/tabit-pro/qubes-windows-tools-cross/releases) (until QWT eventually [makes its way](https://github.com/QubesOS/qubes-issues/issues/3585#issuecomment-1049118557) as an official Qubes package). Alternatively building QWT is easy and doesn't take much time - just follow [those instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). In order to install QWT we need to be able to access the setup .exe in the windows qube. This is usually done by attaching the QWT iso to the qube but alternatively you could download the .exe from the network (web site, remote network share, or even [inter-vm-networking](https://www.qubes-os.org/doc/firewall/#enabling-networking-between-two-qubes)); the latter is outside the scope of this wiki though, as attaching the iso is a lot simpler: - with the GUI: in your windows qube's "Qubes Settings", go to the "Advanced" tab, choose "Boot qubes from CD-ROM", then "from file in qubes" and choose the qube and path where you have downloaded/installed/built QWT (the path is `/usr/lib/qubes/qubes-windows-tools.iso` if installed from the rpm). - or with the CLI: - In the qube where you have the QWT iso run: `sudo losetup -f /path/to/the/iso` (the path is `/usr/lib/qubes/qubes-windows-tools.iso` if installed from the rpm). - In dom0, assuming the qube where you've run the `losetup` command above is named `qwt` and your windows qube is named `win10`, start your windows qube with: `qvm-start win10 --cdrom qwt:loop0` Note: if you've previously ran `losetup` in the `qwt` qube then `loop0` might not be the right device (check the output of `qvm-block` in dom0). Again, don't forget to `qvm-clone` your qube before you install QWT in case something goes south. Setup/usage notes: - XEN PV drivers provide much faster disk and network IO performance. They're included in QWT's setup but aren't selected by default as they are unstable on some setups. In case you decide to install them, XEN's drivers setup will ask to restart the system during QWT's setup: choose "restart later" to allow QWT's installer to complete the installation. - USB support must be enabled for the qube in dom0 in order to be able to attach *USB* devices (devices under "USB Devices" in the graphical widget, or devices attached with `qvm-usb`); in dom0, run: `qvm-features [windows-qube] stubdom-qrexec 1` - Simililarly, audio support must be enabled for the qube; in dom0, run: `qvm-features [windows-qube] audio-model ich6` - Attaching *block* devices (with the graphical widget or with `qvm-block`) should work when XEN PV disk drivers are installed: the attached block device is then shown as a regular disk volume in Window; there won't be a "safely remove" feature though (eg. "eject device") so you must be certain that any copied data is sync'ed before detaching the block device. So when possible it is recommended to attach usb devices like flash disks as a *usb* device rather than a *block* device. Note: some content in QWT's [community documentation](https://github.com/Qubes-Community/Contents/blob/master/docs/os/windows/windows-tools.md) is outdated as the documentation hasn't been updated yet to reflect the newer R4.1 release and QWT's current development/features (contributors welcome). ## Post-install best practices Optimize resources for use in virtual machine as "vanilla" version of Windows are bloated; eg: - set up Windows for best performance (this pc -> advanced settings -> ...) - think about Windows' page file: is it needed ? should you set it with a fixed size ? maybe on the private volume ? - investigate "debloat" scripts ; eg. [Windows10Debloater](https://github.com/Sycnex/Windows10Debloater), [decrapifier](https://community.spiceworks.com/how_to/148624-how-to-clean-up-a-single-windows-10-machine-image-using-decrapifier), [OOShutUp10](https://www.oo-software.com/en/shutup10), etc. - disable services you don't need - disable networking stuff in the network adapter's setting (eg. link discovery, file and print server, ...) - background: set a solid color - ... Please read the [Windows qube documentation](https://www.qubes-os.org/doc/windows/) (thanks to @GWeck the community documentation is now updated for Qubes OS R4.1 so this section's content is deleted).

Revision #31

Edited on
2022-03-26
Edited by user
GWeck
@GWeck; date: 23 Feb 2022, updated 24 March 2022 @GWeck; date: 23 Feb 2022, updated 26 March 2022
- no Network and no Disk drivers - Network and Disk drivers
- seamless mode (dynamic via Que Manager and static via registry) - seamless mode (dynamic via Qube Manager and static via registry)
- attaching USB devices to the qube
- setting decent screen resolution for non-seamless mode using Alt-F8 key - setting decent screen resolution for non-seamless mode using Alt-F8 key - user migration from `C:` to the qube's private volume (needs to rename drive `D:` to `Q:` **before** QWT installation)
- user migration from `c:` to the qube's private volume (has to be done manually) - attaching devices to the qube (attached block devices don't show up) Xen disk and network drivers can be installed after completing the previous steps. This will probably cause Windows activation to become invalid, but the activation can be restored using the Microsoft telephone activation method. After this, USB devices can be attached and used, and booting is about two thirds faster. - attaching SATA and NVME devices to the qube (crashes the qube) Xen disk and network drivers can be installed during installation or after completing the previous steps. This will probably cause Windows activation to become invalid, but the activation can be restored using the Microsoft telephone activation method. After this, USB devices can be attached and used, and booting is about two thirds faster.
@GWeck; date: 23 Feb 2022, updated 16 March 2022 @GWeck; date: 23 Feb 2022, updated 26 March 2022
- no Network and no Disk drivers - Network and Disk drivers
- attaching USB devices to the qube
- user migration from `c:` to the qubes' private volume `Q:` - user migration from `C:` to the qubes' private volume `Q:`
- seamless mode - attaching devices to the qube (attached block devices don't show up) Xen disk and network drivers can be installed after completing the previous steps. Contrary to Windows 7, activation did not become invalid. After this, USB devices can be attached and used, and booting is about one third faster. - attaching SATA and NVME devices to the qube (crashes the qube) - seamless mode Xen disk and network drivers can be installed during installation or after completing the previous steps. Contrary to Windows 7, activation did not become invalid. After this, USB devices can be attached and used, and booting is about one third faster.

Revision #30

Edited on
2022-03-25
Edited by user
GWeck
@GWeck; date: 23 Feb 2022, updated 16 March 2022 @GWeck; date: 23 Feb 2022, updated 24 March 2022
- copy/paste between qubes - copy files between qubes - audio output (needs to activate Windows Audio Endpoint Builder service) - copy/paste between qubes (both directions in and out) - copy files between qubes (both directions in and out)
- setting decent screen resolution for non-seamless mode using Alt-F8 key
- setting decent screen resolution for non-seamless mode - user migration from `c:` to the qubes' private volume (has to be done manually) - user migration from `c:` to the qube's private volume (has to be done manually)
- copy/paste between qubes - copy files between qubes - copy/paste between qubes (both directions in and out) - copy files between qubes (both directions in and out)

Revision #29

Edited on
2022-03-17
Edited by user
taradiddles
Compiled rpm/iso are available [here](https://github.com/tabit-pro/qubes-windows-tools-cross/releases) (until QWT eventually makes its way as an official Qubes package). Alternatively building QWT is easy and doesn't take much time - just follow [those instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). Compiled rpm/iso are available [here](https://github.com/tabit-pro/qubes-windows-tools-cross/releases) (until QWT eventually [makes its way](https://github.com/QubesOS/qubes-issues/issues/3585#issuecomment-1049118557) as an official Qubes package). Alternatively building QWT is easy and doesn't take much time - just follow [those instructions](https://github.com/tabit-pro/qubes-windows-tools-cross).

Revision #28

Edited on
2022-03-16
Edited by user
GWeck
@GWeck; date: 23 Feb 2022, updated 12 March 2022 @GWeck; date: 23 Feb 2022, updated 16 March 2022
Xen disk and network drivers can be installed after completing the previous steps. This will probably cause Windows activation to become invalid, but the activation can be restored using the Microsoft telephone activation method. After this, USB devices can be attached and used, and booting seems to be significantly faster (just a subjective feeling...). Xen disk and network drivers can be installed after completing the previous steps. This will probably cause Windows activation to become invalid, but the activation can be restored using the Microsoft telephone activation method. After this, USB devices can be attached and used, and booting is about two thirds faster.
@GWeck; date: 23 Feb 2022 @GWeck; date: 23 Feb 2022, updated 16 March 2022
Xen disk and network drivers can be installed after completing the previous steps. Contrary to Windows 7, activation did not become invalid. After this, USB devices can be attached and used, and booting is about one third faster.

Revision #27

Edited on
2022-03-14
Edited by user
taradiddles
Known issues: - Recent versions of Windows won't show the cdrom drive after starting the qube with `qvm-start vm --cdrom ...` (or using the gui). The [solution](https://forum.qubes-os.org/t/win-10-standalone-vm-seems-to-have-no-cdrom-drive/8645/3) is to disable hibernation in Windows with `powercfg -H off` (that command is included in QWT's setup but it's necessary to run it manually in order to be able to open QWT's setup iso/cdrom in Windows). Known issues: - Recent versions of Windows won't show the cdrom drive after starting the qube with `qvm-start vm --cdrom ...` (or using the gui). The [solution](https://forum.qubes-os.org/t/win-10-standalone-vm-seems-to-have-no-cdrom-drive/8645/3) is to disable hibernation in Windows with the following command in a command prompt (that command is included in QWT's setup but it's necessary to run it manually in order to be able to open QWT's setup iso/cdrom in Windows). `powercfg -H off` - Qubes OS' default qrexec timeout (60 seconds) might be too short when Windows applies updates and/or check disks. So in case you have Windows Updates enabled you might want to increase it, eg. `qvm-prefs [windows-qube] qrexec_timeout 300`

Revision #26

Edited on
2022-03-12
Edited by user
GWeck
@GWeck; date: 23 Feb 2022 @GWeck; date: 23 Feb 2022, updated 12 March 2022
Xen disk and network drivers can be installed after completing the previous steps. This will probably cause Windows activation to become invalid, but the activation can be restored using the Microsoft telephone activation method. After this, USB devices can be attached and used, and booting seems to be significantly faster (just a subjective feeling...).

Revision #25

Edited on
2022-03-05
Edited by user
taradiddles
In order to install QWT we need to be able to access the setup .exe in the windows qube. This is usually done by attaching the QWT iso to the qube (like you did when initially installing Windows) but alternatively you could download the .exe from the network (web site, remote network share, or even [inter-vm-networking](https://www.qubes-os.org/doc/firewall/#enabling-networking-between-two-qubes)); the latter is outside the scope of this wiki though, as attaching the iso is a lot simpler: In order to install QWT we need to be able to access the setup .exe in the windows qube. This is usually done by attaching the QWT iso to the qube but alternatively you could download the .exe from the network (web site, remote network share, or even [inter-vm-networking](https://www.qubes-os.org/doc/firewall/#enabling-networking-between-two-qubes)); the latter is outside the scope of this wiki though, as attaching the iso is a lot simpler:

Revision #24

Edited on
2022-03-05
Edited by user
taradiddles
Note: if you've previously ran `losetup` in `qwt` then `loop0` might not be the right device (check the output of `qvm-block` in dom0). Note: if you've previously ran `losetup` in the `qwt` qube then `loop0` might not be the right device (check the output of `qvm-block` in dom0).
- USB support must be enabled for the qube in dom0 in order to be able to attach *USB* devices (with the graphical widget under "USB Devices" or with `qvm-usb`): run `qvm-features [windows-qube] stubdom-qrexec 1` in dom0. - Simililarly, audio support must be enabled for the qube: run `qvm-features [windows-qube] audio-model ich6` in dom0 - Attaching *block* devices (widget or `qvm-block`) should work when XEN PV disk drivers are installed: the attached block device is then shown as a regular disk volume in Window; there won't be a "safely remove" feature though (eg. "eject device") so you must be certain that any copied data is sync'ed before detaching the block device. So when possible it is recommended to attach usb devices like flash disks as a *usb* device rather than a *block* device. - USB support must be enabled for the qube in dom0 in order to be able to attach *USB* devices (devices under "USB Devices" in the graphical widget, or devices attached with `qvm-usb`); in dom0, run: `qvm-features [windows-qube] stubdom-qrexec 1` - Simililarly, audio support must be enabled for the qube; in dom0, run: `qvm-features [windows-qube] audio-model ich6` - Attaching *block* devices (with the graphical widget or with `qvm-block`) should work when XEN PV disk drivers are installed: the attached block device is then shown as a regular disk volume in Window; there won't be a "safely remove" feature though (eg. "eject device") so you must be certain that any copied data is sync'ed before detaching the block device. So when possible it is recommended to attach usb devices like flash disks as a *usb* device rather than a *block* device.

Revision #23

Edited on
2022-03-05
Edited by user
taradiddles
Unofficial "debloated" ISOs from projects like [reviOS](https://www.revi.cc/revios) or [ameliorated](https://ameliorated.info) can be found over the net, although obviously you should consider them even "unsafer" than MS provided ISOs. Alternatively, one could download an official ISO and run scripts/apply patches before installation. Some of the "tweaks" might end up being too much depending on the qube's planned usage though (eg. no appx functionality in ameliorated windows - so the installation of Windows Store apps is impossible, even with powershell). Unofficial "debloated" ISOs from projects like [reviOS](https://www.revi.cc/revios) or [ameliorated](https://ameliorated.info) can be found on the net, although obviously you should consider them even "unsafer" than MS provided ISOs. Alternatively, one could download an official ISO and run scripts/apply patches before installation. Some of the "tweaks" might end up being too much depending on the qube's planned usage though (eg. no appx functionality in ameliorated windows - so the installation of Windows Store apps is impossible, even with powershell).
## QWT QWT's main features are: ## Qubes Windows Tools (QWT) QWT works on Qubes OS R4.x thanks to the great work of @jevank et al. QWT's main features are:
QWT changelog/commits are [here](https://github.com/tabit-pro/qubes-windows-tools-cross/commits/master). Installation: QWT works on Qubes OS R4.x thanks to the great work of @jevank et al. Binaries are available [here](https://github.com/tabit-pro/qubes-windows-tools-cross/releases) until QWT makes its way as an official Qubes package; alternatively building QWT is easy and doesn't take much time - just follow [those instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). Changelog/commits are [here](https://github.com/tabit-pro/qubes-windows-tools-cross/commits/master). Compiled rpm/iso are available [here](https://github.com/tabit-pro/qubes-windows-tools-cross/releases) (until QWT eventually makes its way as an official Qubes package). Alternatively building QWT is easy and doesn't take much time - just follow [those instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). In order to install QWT we need to be able to access the setup .exe in the windows qube. This is usually done by attaching the QWT iso to the qube (like you did when initially installing Windows) but alternatively you could download the .exe from the network (web site, remote network share, or even [inter-vm-networking](https://www.qubes-os.org/doc/firewall/#enabling-networking-between-two-qubes)); the latter is outside the scope of this wiki though, as attaching the iso is a lot simpler: - with the GUI: in your windows qube's "Qubes Settings", go to the "Advanced" tab, choose "Boot qubes from CD-ROM", then "from file in qubes" and choose the qube and path where you have downloaded/installed/built QWT (the path is `/usr/lib/qubes/qubes-windows-tools.iso` if installed from the rpm). - or with the CLI: - In the qube where you have the QWT iso run: `sudo losetup -f /path/to/the/iso` (the path is `/usr/lib/qubes/qubes-windows-tools.iso` if installed from the rpm). - In dom0, assuming the qube where you've run the `losetup` command above is named `qwt` and your windows qube is named `win10`, start your windows qube with: `qvm-start win10 --cdrom qwt:loop0` Note: if you've previously ran `losetup` in `qwt` then `loop0` might not be the right device (check the output of `qvm-block` in dom0).
- XEN PV drivers provide much faster disk and network IO performance. They're included in QWT's setup but aren't selected by default as they are unstable on some setups. In case you decide to install them, XEN's drivers setup will ask to restart the system during QWT's setup: choose "restart later" to allow QWT's installer to complete the installation. - USB support must be enabled for the qube in dom0 in order to be able to attach *USB* devices (with the graphical widget under "USB Devices" or with `qvm-usb`): run `qvm-features [windows-qube] stubdom-qrexec 1` in dom0. - Simililarly, audio support must be enabled for the qube: run `qvm-features [windows-qube] audio-model ich6` in dom0 - XEN PV drivers provide much faster disk and network IO performance. They're included in QWT's setup but aren't selected by default as they are unstable on some setups. In case you decide to install them, XEN's drivers setup will ask to restart the system during QWT's setup: choose "restart later" to allow QWT's installer to complete the installation. - USB support must be enabled for the qube in dom0 in order to be able to attach *USB* devices (with the graphical widget under "USB Devices" or with `qvm-usb`): run `qvm-features [windows-qube] stubdom-qrexec 1` in dom0. - Simililarly, audio support must be enabled for the qube: run `qvm-features [windows-qube] audio-model ich6` in dom0

Revision #22

Edited on
2022-03-04
Edited by user
taradiddles
Please contribute too ! It's easy: edit this wiki page (the edit/'pen' icon at the bottom of the post), copy the content of the [user report template](#template) at the end of this post and paste it in the relevant "Contributed user reports" Windows sections. Even is someone has already added a report with the same version of Windows (and optionally QWT) it's perfectly fine to add another report as your use case (/features you use) might differ. Detailed notes about a given Windows/QWT combination (eg. very detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page in the user report: that way the post's author is free to use whatever layout and amount of information he/she sees fit and this keeps relevant questions/answers threads contained in a post rather than in the more "generic" comments here. Please contribute too ! It's easy: edit this wiki page (the edit/'pen' icon at the bottom of the post), copy the content of the [user report template](#template) at the end of this post and paste it in the relevant "Contributed user reports" Windows sections. Even is someone has already added a report with the same version of Windows (and optionally QWT) it's perfectly fine to add another report as your use case (/features you use) might differ.
QWT works on Qubes OS R4.x thanks to the great work of @jevank et al. Binaries are available [here](https://github.com/tabit-pro/qubes-windows-tools-cross/releases) until QWT makes its way as an official Qubes package; alternatively building QWT is easy and doesn't take much time - just copy/paste the [instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). Again, don't forget to `qvm-clone` your qube before you install QWT in case something goes south. Note: XEN PV drivers provide much faster disk and network IO performance. They're included in QWT's setup but aren't selected by default; if you decide to install them, XEN's drivers setup will ask to restart the system during QWT's setup: choose "restart later" to allow QWT installer to complete the installation. QWT main features: QWT's main features are:
- attaching devices to the qube - attaching USB devices to the qube - attaching block devices to the qube (XEN PV disk driver must be installed)
- seamless mode ? QWT changelog/commits are [here](https://github.com/tabit-pro/qubes-windows-tools-cross/commits/master) - seamless mode (win7 only for now) - propagating keyboard layout ? QWT changelog/commits are [here](https://github.com/tabit-pro/qubes-windows-tools-cross/commits/master). Installation: QWT works on Qubes OS R4.x thanks to the great work of @jevank et al. Binaries are available [here](https://github.com/tabit-pro/qubes-windows-tools-cross/releases) until QWT makes its way as an official Qubes package; alternatively building QWT is easy and doesn't take much time - just follow [those instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). Again, don't forget to `qvm-clone` your qube before you install QWT in case something goes south. Setup/usage notes: - XEN PV drivers provide much faster disk and network IO performance. They're included in QWT's setup but aren't selected by default as they are unstable on some setups. In case you decide to install them, XEN's drivers setup will ask to restart the system during QWT's setup: choose "restart later" to allow QWT's installer to complete the installation. - USB support must be enabled for the qube in dom0 in order to be able to attach *USB* devices (with the graphical widget under "USB Devices" or with `qvm-usb`): run `qvm-features [windows-qube] stubdom-qrexec 1` in dom0. - Simililarly, audio support must be enabled for the qube: run `qvm-features [windows-qube] audio-model ich6` in dom0 - Attaching *block* devices (widget or `qvm-block`) should work when XEN PV disk drivers are installed: the attached block device is then shown as a regular disk volume in Window; there won't be a "safely remove" feature though (eg. "eject device") so you must be certain that any copied data is sync'ed before detaching the block device. So when possible it is recommended to attach usb devices like flash disks as a *usb* device rather than a *block* device.
- investigate "debloat" scripts ; eg. [this](https://github.com/Sycnex/Windows10Debloater), [this](https://community.spiceworks.com/how_to/148624-how-to-clean-up-a-single-windows-10-machine-image-using-decrapifier), [this](https://www.oo-software.com/en/shutup10), etc. - investigate "debloat" scripts ; eg. [Windows10Debloater](https://github.com/Sycnex/Windows10Debloater), [decrapifier](https://community.spiceworks.com/how_to/148624-how-to-clean-up-a-single-windows-10-machine-image-using-decrapifier), [OOShutUp10](https://www.oo-software.com/en/shutup10), etc.
- attaching devices to the qube - attaching *usb* devices to the qube
- user migration from `c:` to the qubes' private volume - attached block devices (USB or loopback devices) don't show up - user migration from `c:` to the qubes' private volume
- attaching devices to the qube (attached a USB device ; however there is no 'eject' functionality, maybe because of AME tweaks, so I have to make sure data is sync'ed before detaching). - attaching *block* devices to the qube (no 'eject' functionality) - attaching *usb* devices to the qube
The template below is meant to be improved ! It isn't exhaustive by any means and most of the fields aren't mandatory. It's OK to add a bit more "free text" when contributing a report to avoid having to create a dedicated post with only a few lines. Please discuss non-trivial changes you'd like to make to the template before editing it. The template below is meant to be improved ! It isn't exhaustive by any means and most of the fields aren't mandatory. More detailed notes about a given Windows/QWT combination (eg. very detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page in the user report: that way the post's author is free to use whatever layout and amount of information he/she sees fit, and this keeps relevant questions/answers threads contained in a post rather than in the more "generic" comments here. That said it's OK to add a bit more "free text" to the template when contributing a report to avoid having to create a dedicated post with only a few lines. (In case you want to change the template's text itself, please discuss any major changes in this post's comments).
- attaching devices to the qube - attaching *block* devices to the qube [with widget under "Data (Block) devices" or with `qvm-block`] - attaching *usb* devices to the qube [with widget under "USB devices" or with `qvm-usb`] - attaching audio input devices to the qube [with widget under "Audio Input"]

Revision #21

Edited on
2022-03-04
Edited by user
taradiddles
Getting and installing: QWT works on Qubes OS R4.x thanks to the great work of @jevank et al. There are no binaries yet (though this should [change](https://github.com/QubesOS/qubes-issues/issues/7240)) so it has to be built; the process is straightforward and doesn't take much time - just copy/paste the [instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). Again, don't forget to `qvm-clone` your qube before you install QWT in case something goes south. QWT works on Qubes OS R4.x thanks to the great work of @jevank et al. Binaries are available [here](https://github.com/tabit-pro/qubes-windows-tools-cross/releases) until QWT makes its way as an official Qubes package; alternatively building QWT is easy and doesn't take much time - just copy/paste the [instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). Again, don't forget to `qvm-clone` your qube before you install QWT in case something goes south.

Revision #20

Edited on
2022-03-04
Edited by user
taradiddles
> :warning: **Please note** This is a *work in progress guide* (WIP), created to crowdsource user experience about using Windows in Qubes, optionally with Qubes Windows Tools ("QWT"), following up on [this github issue](https://github.com/QubesOS/qubes-issues/issues/3585). Contributing is easy: edit this wiki page (the edit/'pen' icon at the bottom of the post), copy the content of the "Template report" below between the `[details=...]` and `[/details]` tags (including those tags) and paste it in the relevant "Contributed user reports" Windows sections. Detailed, specific notes about a given Windows/QWT combination (eg. very detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page: that way the post's author is free to use whatever layout and amount of information he/she sees fit; this also keeps relevant questions/answers threads contained in a post rather than in more "general" comments here. The template below is meant to be improved ! It isn't exhaustive by any means and most of the fields aren't mandatory. It's OK to add a bit more "free text" when contributing a report to avoid having to create a dedicated post with only a few lines. Please discuss non-trivial changes you'd like to make to the template before editing it. # Template report ```text [details="R4.x / Windows XXX / QWT XXX"] @userxyz ; date: xx month year Windows - installed from scratch, or migrated from an older Qubes OS release ? - build/iso [eg. '21H1', 'ameliorated 20H1', ...] - disk space required by the installer [if known] - ram used when installing [doesn't mean it is the required amount] - ram usage after install [if known] - disk space usage after install [if known] - if display resolution was changed, does it work ? - if audio was tested, does it work ? - problems running the VM ? QWT [optional] - first installation or migration/re-installation over an older version ? - installed just after windows' first boot, or after a full windows update ? - features selected during installation if not the default choice [eg. Xen PV drivers]. - features removed during installation if not the default choice [eg. UAC]. - features that were tested to work [delete line that aren't relevant/not tested]: - copy/paste between qubes - copy files between qubes - attaching devices to the qube - networking - time/clock synchronization - XEN PV disk driver - XEN PV network driver - user migration from `c:` to the qubes' private volume to be able use the qubes as a TemplateVM). - features that don't work [possibly with workarounds]: ... Summary / notes [if any]: Link to a specific post [if any - it could contain detailed instructions, known issues, workarounds, hints/tips, description of the author's workflow, productivity tips, ...] [/details] ``` > :warning: **Please note** This is a *work in progress guide* (WIP) created to crowdsource user experience about using Windows in Qubes, optionally with Qubes Windows Tools ("QWT"), following up on [this github issue](https://github.com/QubesOS/qubes-issues/issues/3585). Please contribute too ! It's easy: edit this wiki page (the edit/'pen' icon at the bottom of the post), copy the content of the [user report template](#template) at the end of this post and paste it in the relevant "Contributed user reports" Windows sections. Even is someone has already added a report with the same version of Windows (and optionally QWT) it's perfectly fine to add another report as your use case (/features you use) might differ. Detailed notes about a given Windows/QWT combination (eg. very detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page in the user report: that way the post's author is free to use whatever layout and amount of information he/she sees fit and this keeps relevant questions/answers threads contained in a post rather than in the more "generic" comments here.
## Migrating Windows qubes created under Qubes R4.0 to R4.1 See [this issue](https://github.com/QubesOS/qubes-issues/issues/7088). (tl;dr; feasible but not straightforward).
Getting and installing: QWT works on Qubes OS R4.x thanks to the great work of @jevank et al. There are no binaries yet (though this should [change](https://github.com/QubesOS/qubes-issues/issues/7240)) so it has to be built; the process is straightforward and doesn't take much time - just copy/paste the [instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). Note: when installing XEN PV drivers, XEN's drivers setup will ask to restart the system: choose "restart later" to allow QWT installer to complete the installation. Getting and installing: QWT works on Qubes OS R4.x thanks to the great work of @jevank et al. There are no binaries yet (though this should [change](https://github.com/QubesOS/qubes-issues/issues/7240)) so it has to be built; the process is straightforward and doesn't take much time - just copy/paste the [instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). Again, don't forget to `qvm-clone` your qube before you install QWT in case something goes south. Note: XEN PV drivers provide much faster disk and network IO performance. They're included in QWT's setup but aren't selected by default; if you decide to install them, XEN's drivers setup will ask to restart the system during QWT's setup: choose "restart later" to allow QWT installer to complete the installation.
Try to also install QWT with the XEN PV disk and network drivers ticked (again, don't forget to clone your qube before).
[/details] [/details] # <a href="template"></a>User report template The template below is meant to be improved ! It isn't exhaustive by any means and most of the fields aren't mandatory. It's OK to add a bit more "free text" when contributing a report to avoid having to create a dedicated post with only a few lines. Please discuss non-trivial changes you'd like to make to the template before editing it. > :warning: Copy the text in the text area below including the `[details=...]` and `[/details]` tags ```text [details="R4.x / Windows XXX / QWT XXX"] @userxyz ; date: xx month year Windows - installed from scratch, or migrated from an older Qubes OS release ? - build/iso [eg. '21H1', 'ameliorated 20H1', ...] - disk space required by the installer [if known] - ram used when installing [doesn't mean it is the required amount] - ram usage after install [if known] - disk space usage after install [if known] - if display resolution was changed, does it work ? - if audio was tested, does it work ? - problems running the VM ? QWT [optional] - first installation or migration/re-installation over an older version ? - installed just after windows' first boot, or after a full windows update ? - features selected during installation if not the default choice [eg. Xen PV drivers]. - features removed during installation if not the default choice [eg. UAC]. - features that were tested to work [delete line that aren't relevant/not tested]: - copy/paste between qubes - copy files between qubes - attaching devices to the qube - networking - time/clock synchronization - XEN PV disk driver - XEN PV network driver - user migration from `c:` to the qubes' private volume to be able use the qubes as a TemplateVM). - features that don't work [possibly with workarounds]: ... Summary / notes [if any]: Link to a specific post [if any - it could contain detailed instructions, known issues, workarounds, hints/tips, description of the author's workflow, productivity tips, ...] [/details] ```

Revision #19

Edited on
2022-03-01
Edited by user
deeplow
> :warning: **Please note** This is a *work in progress guide*, created to crowdsource user experience about using Windows in Qubes, optionally with Qubes Windows Tools ("QWT"), following up on [this github issue](https://github.com/QubesOS/qubes-issues/issues/3585). > :warning: **Please note** This is a *work in progress guide* (WIP), created to crowdsource user experience about using Windows in Qubes, optionally with Qubes Windows Tools ("QWT"), following up on [this github issue](https://github.com/QubesOS/qubes-issues/issues/3585).

Revision #18

Edited on
2022-02-24
Edited by user
taradiddles
- optional user migration from `c:` to the qubes' private volume (to be able use the qubes as a TemplateVM). - optional user migration from `c:` to the qubes' private volume (to be able use the qubes as a TemplateVM). - seamless mode ?
Note: some content in QWT's [community documentation](https://github.com/Qubes-Community/Contents/blob/master/docs/os/windows/windows-tools.md) is outdated as the documentation hasn't been updated yet to reflect the newer R4.1 release and QWT's current development/features (contributors welcome).

Revision #17

Edited on
2022-02-24
Edited by user
taradiddles
[details="R4.1 / Windows 21H2 / QWT master 2022-02-12"] [details="R4.1 / Windows 21H2 / QWT 4.1.67 - Feb. 2022"]
[details="R4.1 / Windows AME 21H1 / QWT master 2022-02-12)"] [details="R4.1 / Windows AME 21H1 / QWT 4.1.67 - Feb. 2022)"]

Revision #16

Edited on
2022-02-23
Edited by user
GWeck
- disk space usage after install: 40GB - disk space usage after install: 15GB
- user migration from `c:` to the qubes' private volume `Q:`
- user migration from `c:` to the qubes' private volume (has to be done manually)

Revision #15

Edited on
2022-02-23
Edited by user
GWeck
(placeholder) [details="R4.1 / Windows 11 Pro 21H2 / QWT 4.1.67 of 2022-02-14"] @GWeck; date: 23 Feb 2022 Windows: - installed from scratch as template VM, using TPM-disable patch during installation - build/iso: 21H2, downloaded from Microsoft - ram used when installing: 4GB - ram usage after install: 4GB - disk space usage after install: 40GB QWT: - first installation - features selected during installation: - Base Xen PV drivers - no Network and no Disk drivers - Move User Profiles - features that were tested to work: - build / use AppVM based on that template - setting decent screen resolution for non-seamless mode - copy/paste between qubes - copy files between qubes - audio output (somewhat scratchy) - networking (for AppVM based on that template) - time/clock synchronization using `qvm-features VMname timezone localtime` - features that don't work: - seamless mode - user migration from `c:` to the qubes' private volume (has to be done manually) - attaching devices to the qube (attached block devices don't show up) Summary / notes: rather slow, as well on booting and shutdown as on using; installation requires disabling the check for TPM 2.0, using the trick described in [Windows 11 in Qubes](https://forum.qubes-os.org/t/windows-11-in-qubes/6759/8) - using Windows 11 is a good motivation for migrating to Linux :-) [/details]

Revision #14

Edited on
2022-02-23
Edited by user
GWeck
(placeholder) [details="R4.1 / Windows 7 Pro SP1 updated until Oct 2020 / QWT 4.1.67 of 2022-02-14"] @GWeck; date: 23 Feb 2022 Windows: - installed from scratch as template VM - build/iso: Windows7ProfSP1.iso of 2016-05-28, downloaded from Microsoft - updated using WinFuture Patch kit "WinFuture_7SP1_x64_UpdatePack_2.107_Januar_2020-Vollversion.exe" and manual updates after that - ram used when installing: 4GB - ram usage after install: 4GB - disk space usage after install: 27GB QWT: - first installation - installed just after completing the update horror to get the system current - features selected during installation: - Base Xen PV drivers - no Network and no Disk drivers - Move User Profiles - features that were tested to work: - build / use AppVM based on that template - seamless mode (dynamic via Que Manager and static via registry) - copy/paste between qubes - copy files between qubes - networking (for AppVM based on that template) - time/clock synchronization using `qvm-features VMname timezone localtime` - features that don't work: - setting decent screen resolution for non-seamless mode - user migration from `c:` to the qubes' private volume (has to be done manually) - attaching devices to the qube (attached block devices don't show up) Summary / notes: can be reasonably used in seamless mode; access to functions via XFCE menu or by hitting Windows keyboard key in a VM's window and thus displaying the Windows menu [/details]

Revision #13

Edited on
2022-02-23
Edited by user
taradiddles
- features selected during installation if not the default choice (eg. Xen PV drivers). - features removed during installation if not the default choice (eg. UAC). - features that were tested to work (delete line that aren't relevant/not tested): - features selected during installation if not the default choice [eg. Xen PV drivers]. - features removed during installation if not the default choice [eg. UAC]. - features that were tested to work [delete line that aren't relevant/not tested]:
- user migration from `c:` to the qubes' private volume (to be able use the qubes as a TemplateVM). - features that don't work (possibly with workarounds): ... Summary / notes (if any): Link to a specific post - if any: ... (free form post: it could have detailed instructions, known issues, workarounds, hints/tips, description of the author's workflow, productivity tips, ...) - user migration from `c:` to the qubes' private volume to be able use the qubes as a TemplateVM). - features that don't work [possibly with workarounds]: ... Summary / notes [if any]: Link to a specific post [if any - it could contain detailed instructions, known issues, workarounds, hints/tips, description of the author's workflow, productivity tips, ...]
- features that were tested to work (delete line that aren't relevant/not tested): - features that were tested to work:
- features that don't work (possibly with workarounds): ... - features that don't work:

Revision #12

Edited on
2022-02-23
Edited by user
taradiddles
[details="R4.x / Windows XXX / QWT XXX "] [details="R4.x / Windows XXX / QWT XXX"]
Windows: Windows
- build/iso (eg. '21H1', 'ameliorated 20H1', ...) - disk space required by the installer (if known) - ram used when installing (doesn't mean it is the required amount) - ram usage after install - if known. - disk space usage after install - if known. - windows update status (eg. enabled, date last updated, ...) - display resolution ? - build/iso [eg. '21H1', 'ameliorated 20H1', ...] - disk space required by the installer [if known] - ram used when installing [doesn't mean it is the required amount] - ram usage after install [if known] - disk space usage after install [if known] - if display resolution was changed, does it work ?
- problems with running the VM ? QWT (optional): - problems running the VM ? QWT [optional]
Note: when installing XEN PV drivers, XEN's drivers setup will ask to restart the system: choose "restart later" to allow QWT installer to complete the installation.
[details="R4.1 / Windows AME 21H1 / QWT (github master / 2022-02-12)"] [details="R4.1 / Windows 21H2 / QWT master 2022-02-12"] @taradiddles; date: 20 Feb 2022 Windows: - installed from scratch - build/iso: 21H2, downloaded from Microsoft - ram used when installing: 4GB - ram usage after install: 1.1GB - disk space usage after install: 12GB QWT: - first installation - installed just after windows' first boot - features selected during installation: Xen PV drivers - features that were tested to work (delete line that aren't relevant/not tested): - copy/paste between qubes - copy files between qubes - attaching devices to the qube - networking - time/clock synchronization - XEN PV disk driver - XEN PV network driver - features that don't work: - user migration from `c:` to the qubes' private volume - attached block devices (USB or loopback devices) don't show up Summary / notes: "vanilla" windows really feels sluggish, it then takes a lot of time and patience to remove bloatware and optimize the vm to make it usable. [/details] [details="R4.1 / Windows AME 21H1 / QWT master 2022-02-12)"]

Revision #11

Edited on
2022-02-23
Edited by user
taradiddles
Simple Windows install (gui based): [community doc](https://github.com/Qubes-Community/Contents/blob/master/docs/os/windows/windows-vm.md#simple-windows-install) Or use @elliotkillick's [qvm-create-windows-qube](https://github.com/elliotkillick/qvm-create-windows-qube) scripts (note: works on Qubes OS R4.0 but [maybe not](https://github.com/elliotkillick/qvm-create-windows-qube/issues/52) on R4.1. Simple Windows install (gui based): follow the steps under "Installation procedure" in this [community guide](https://github.com/Qubes-Community/Contents/blob/master/docs/os/windows/windows-vm.md#simple-windows-install) (TODO: the guide should be updated, the "works"/"doesn't work" sections are outdated because QWT now works on R4.x). Alternatively, on R4.0 you may use @elliotkillick's [qvm-create-windows-qube](https://github.com/elliotkillick/qvm-create-windows-qube) scripts. R4.1 support is unknown (see [this issue](https://github.com/elliotkillick/qvm-create-windows-qube/issues/52)).
Known issues: - Recent versions of Windows won't show the cdrom drive after starting the qube with `qvm-start vm --cdrom ...` (or using the gui). The [solution](https://forum.qubes-os.org/t/win-10-standalone-vm-seems-to-have-no-cdrom-drive/8645/3) is to disable hibernation in Windows with `powercfg -H off` (that command is included in QWT's setup but it's necessary to run it manually in order to be able to open QWT's setup iso/cdrom in Windows).

Revision #10

Edited on
2022-02-22
Edited by user
taradiddles
Unofficial "debloated" ISOs from projects like [reviOS](https://www.revi.cc/revios), [ameliorated](https://ameliorated.info) can be found over the net, although obviously you should consider them even "unsafer" than MS provided ISOs. Alternatively, one could download an official ISO and run scripts/apply patches before installation. Some of the "tweaks" might end up being too much depending on the qube's planned usage though (eg. no appx functionality in ameliorated windows - so the installation of Windows Store apps is impossible, even with powershell). Unofficial "debloated" ISOs from projects like [reviOS](https://www.revi.cc/revios) or [ameliorated](https://ameliorated.info) can be found over the net, although obviously you should consider them even "unsafer" than MS provided ISOs. Alternatively, one could download an official ISO and run scripts/apply patches before installation. Some of the "tweaks" might end up being too much depending on the qube's planned usage though (eg. no appx functionality in ameliorated windows - so the installation of Windows Store apps is impossible, even with powershell).
Getting and installing: QWT works on Qubes OS R4.x thanks to the great work of @jevank et al. There are no binaries yet (though his should [change](https://github.com/QubesOS/qubes-issues/issues/7240)) so it has to be built; the process is straightforward and doesn't take much time - just copy/paste the [instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). Getting and installing: QWT works on Qubes OS R4.x thanks to the great work of @jevank et al. There are no binaries yet (though this should [change](https://github.com/QubesOS/qubes-issues/issues/7240)) so it has to be built; the process is straightforward and doesn't take much time - just copy/paste the [instructions](https://github.com/tabit-pro/qubes-windows-tools-cross).

Revision #9

Edited on
2022-02-22
Edited by user
taradiddles
Detailed, specific notes about a given Windows/QWT combination (eg. very detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page: that way the post's author is free to use whatever layout and amount of information he/she sees fit; this also keeps relevant questions/answers threads contained in a post rather than in more "global" comments here. Detailed, specific notes about a given Windows/QWT combination (eg. very detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page: that way the post's author is free to use whatever layout and amount of information he/she sees fit; this also keeps relevant questions/answers threads contained in a post rather than in more "general" comments here.
- set a solid background - background: set a solid color

Revision #8

Edited on
2022-02-22
Edited by user
taradiddles
Contributing is easy: edit this wiki page (the edit/'pen' icon at the bottom of the post), copy the content of the "Template report" below between the `[details=...]` and `[/details]` tags (including those tags) and paste it in the relevant Windows version sections. :arrow_forward: Detailed, specific notes about a given Windows/QWT combination (eg. very detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page: that way the post's author is free to use whatever layout and amount of information he/she sees fit; this also keeps relevant questions/answers threads contained in a post rather than in more "global" comments here. :arrow_forward: This template is meant to be improved ! It isn't exhaustive by any means and most of the fields aren't mandatory. It's OK to add a bit more "free text" when contributing a report to avoid having to create a dedicated post with only a few lines. :arrow_forward: Please discuss non-trivial changes of the template in the comments section of this page before editing it. Contributing is easy: edit this wiki page (the edit/'pen' icon at the bottom of the post), copy the content of the "Template report" below between the `[details=...]` and `[/details]` tags (including those tags) and paste it in the relevant "Contributed user reports" Windows sections. Detailed, specific notes about a given Windows/QWT combination (eg. very detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page: that way the post's author is free to use whatever layout and amount of information he/she sees fit; this also keeps relevant questions/answers threads contained in a post rather than in more "global" comments here. The template below is meant to be improved ! It isn't exhaustive by any means and most of the fields aren't mandatory. It's OK to add a bit more "free text" when contributing a report to avoid having to create a dedicated post with only a few lines. Please discuss non-trivial changes you'd like to make to the template before editing it.
# Windows 11 ## Windows 11

Revision #7

Edited on
2022-02-22
Edited by user
taradiddles
> :warning: **Please note** > This is a *work in progress guide*, created to crowdsource information, following up on [this github issue](https://github.com/QubesOS/qubes-issues/issues/3585). This post is meant to be a wiki-style page consolidating user experience about using Windows in Qubes, along with Qubes Windows Tools ("QWT"). Contributing is easy: edit this wiki page (the 'pen' icon at the bottom of the post), copy the text of the "Template report" below and paste it in the relevant Windows version sections. :arrow_forward: Detailed, specific notes about a given Windows/QWT combination (eg. detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page: that way the post's author is free to use whatever layout and amount of information he/she sees fit; this also keeps relevant questions/answers threads contained in a post rather than in more "global" comments here. > :warning: **Please note** This is a *work in progress guide*, created to crowdsource user experience about using Windows in Qubes, optionally with Qubes Windows Tools ("QWT"), following up on [this github issue](https://github.com/QubesOS/qubes-issues/issues/3585). Contributing is easy: edit this wiki page (the edit/'pen' icon at the bottom of the post), copy the content of the "Template report" below between the `[details=...]` and `[/details]` tags (including those tags) and paste it in the relevant Windows version sections. :arrow_forward: Detailed, specific notes about a given Windows/QWT combination (eg. very detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page: that way the post's author is free to use whatever layout and amount of information he/she sees fit; this also keeps relevant questions/answers threads contained in a post rather than in more "global" comments here.
``` ```text
Link to a specific post - if any: ... (free form post: it could have detailed instructions, known issues, workarounds, hints/tips, description of the author's workflow, productivity tips, ...) [/details] Link to a specific post - if any: ... (free form post: it could have detailed instructions, known issues, workarounds, hints/tips, description of the author's workflow, productivity tips, ...) [/details]

Revision #6

Edited on
2022-02-22
Edited by user
taradiddles
### R4.x / Windows XXX / QWT XXX / @userxyz [details="R4.x / Windows XXX / QWT XXX "] @userxyz ; date: xx month year
[/details]
### R4.1 / Windows AME 21H1 / QWT (github master / 2022-02-12) / @taradiddles [details="R4.1 / Windows AME 21H1 / QWT (github master / 2022-02-12)"] @taradiddles / 12 Feb 2022
Summary: windows AME is really snappy and works well so far but it lacks features like appx (windows store) that could make it a no-go for some. Summary: windows AME is really snappy and works well so far but it lacks features like appx (windows store) that could make it a no-go for some. [/details]

Revision #5

Edited on
2022-02-22
Edited by user
taradiddles
> :arrow_forward: Detailed, specific notes about a given Windows/QWT combination (eg. detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page: that way the post's author is free to use whatever layout and amount of information he/she sees fit; this also keeps relevant questions/answers threads contained in a post rather than in more "global" comments here. > :arrow_forward: This template is meant to be improved ! It isn't exhaustive by any means and most of the fields aren't mandatory. It's also OK to add terse info when contributing a report. > :arrow_forward: Please discuss any non-trivial changes in the comments section before editing the template. :arrow_forward: Detailed, specific notes about a given Windows/QWT combination (eg. detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page: that way the post's author is free to use whatever layout and amount of information he/she sees fit; this also keeps relevant questions/answers threads contained in a post rather than in more "global" comments here. :arrow_forward: This template is meant to be improved ! It isn't exhaustive by any means and most of the fields aren't mandatory. It's OK to add a bit more "free text" when contributing a report to avoid having to create a dedicated post with only a few lines. :arrow_forward: Please discuss non-trivial changes of the template in the comments section of this page before editing it.
### Windows XXX / QWT XXX / @userxyz ### R4.x / Windows XXX / QWT XXX / @userxyz
Getting and installing: thanks to the great work of @jevank et al., QWT can be used or R4.x. There are no binaries yet (though his should [change](https://github.com/QubesOS/qubes-issues/issues/7240)) so it has to be built; the process is straightforward and doesn't take much time - just copy/paste the [instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). Getting and installing: QWT works on Qubes OS R4.x thanks to the great work of @jevank et al. There are no binaries yet (though his should [change](https://github.com/QubesOS/qubes-issues/issues/7240)) so it has to be built; the process is straightforward and doesn't take much time - just copy/paste the [instructions](https://github.com/tabit-pro/qubes-windows-tools-cross).
### Windows AME 21H1 / QWT (github master / 2022-02-12) / @taradiddles ### R4.1 / Windows AME 21H1 / QWT (github master / 2022-02-12) / @taradiddles

Revision #4

Edited on
2022-02-22
Edited by user
taradiddles
This post is meant to be a wiki-style page consolidating user experience about using Windows in Qubes, most likely with Qubes Windows Tools ("QWT"). Please copy the "Sample template" below and paste it in the relevant Windows version sections. > Specific notes about a given Windows/QWT combination (eg. detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with the "Guide" tag and linked to this wiki page: that way the post's author is free to use whatever layout and amount of information he/she sees fit; this also keep relevant questions/answers threads contained in a post rather than being lost in the wiki page&#39;s comments. > This template is meant to be improved ! (before editing it in the wiki please discuss any non-trivial changes in the comments section first). It isn't exhaustive by any means and most of the fields aren't mandatory. It's OK to add terse info when adding a report to this page. ## [Sample template] Windows XXX / QWT XXX / @userxyz This post is meant to be a wiki-style page consolidating user experience about using Windows in Qubes, along with Qubes Windows Tools ("QWT"). Contributing is easy: edit this wiki page (the 'pen' icon at the bottom of the post), copy the text of the "Template report" below and paste it in the relevant Windows version sections. > :arrow_forward: Detailed, specific notes about a given Windows/QWT combination (eg. detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with a "Guide" tag and linked to this wiki page: that way the post's author is free to use whatever layout and amount of information he/she sees fit; this also keeps relevant questions/answers threads contained in a post rather than in more &quot;global" comments here. > :arrow_forward: This template is meant to be improved ! It isn't exhaustive by any means and most of the fields aren't mandatory. It's also OK to add terse info when contributing a report. > :arrow_forward: Please discuss any non-trivial changes in the comments section before editing the template. # Template report ``` ### Windows XXX / QWT XXX / @userxyz
Link to a specific post - if any: ... (free form post: it could have detailed instructions, known issues, workarounds, hints/tips, description of the author's workflow, productivity tips, ...) Link to a specific post - if any: ... (free form post: it could have detailed instructions, known issues, workarounds, hints/tips, description of the author's workflow, productivity tips, ...) ```
# User reports - Windows 7 # Contributed user reports ## Windows 7
# User reports - Windows 10 ## Windows AME 21H1 / QWT (github master / 2022-02-12) / @taradiddles ## Windows 10 ### Windows AME 21H1 / QWT (github master / 2022-02-12) / @taradiddles
# User reports - Windows 11 # Windows 11

Revision #3

Edited on
2022-02-22
Edited by user
taradiddles
# General notes/resources
To avoid clutter please use the "feedback template" below and put it in the relevant Windows version sections. Specific notes about a given Windows/QWT combination like detailed instructions, workarounds, hints/tips, user workflow, ... should be posted to a a separate post and linked to this page in order to keep potential questions and answers threads in their own post and allowing the post's author to use whatever layout and amount of information he/she sees fit. This template is meant to be improved ! (before editing t please discuss any non-trivial changes in the comments section first). It isn't exhaustive by any means and most of the fields aren't mandatory. It's OK to add terse info when adding a report to this page. Please copy the "Sample template" below and paste it in the relevant Windows version sections. > Specific notes about a given Windows/QWT combination (eg. detailed installation instructions, workarounds, hints/tips, user workflow, ...) should be posted to a separate post with the "Guide" tag and linked to this wiki page: that way the post's author is free to use whatever layout and amount of information he/she sees fit; this also keep relevant questions/answers threads contained in a post rather than being lost in the wiki page's comments. > This template is meant to be improved ! (before editing it in the wiki please discuss any non-trivial changes in the comments section first). It isn't exhaustive by any means and most of the fields aren't mandatory. It's OK to add terse info when adding a report to this page.
- if audio was tested, does it work ?
# General resources
Unofficial "debloated" ISOs from projects like [reviOS](https://www.revi.cc/revios), [ameliorated](https://ameliorated.info) can be found over the net, although obviously you should consider them even "unsafer" than MS provided ISOs. Alternatively, once could download an official ISO and apply patches before installation. Some of the "tweaks" might end up being too much though (eg. for ameliorated, no appx functionality - so no Windows Store apps). Unofficial "debloated" ISOs from projects like [reviOS](https://www.revi.cc/revios), [ameliorated](https://ameliorated.info) can be found over the net, although obviously you should consider them even "unsafer" than MS provided ISOs. Alternatively, one could download an official ISO and run scripts/apply patches before installation. Some of the "tweaks" might end up being too much depending on the qube's planned usage though (eg. no appx functionality in ameliorated windows - so the installation of Windows Store apps is impossible, even with powershell).
Don't forget to `qvm-clone` your qubes from times to times. Windows being Windows, it's easy to do something that makes the qube unusable (BSOD). Don't forget to `qvm-clone` your qubes from times to times. Windows being Windows, it's easy to do something that renders your windows qube unusable (eg. BSOD, boot loop, ...).
Getting and installing: thanks to the great work of @jevank, QWT can be used or R4.x. There are no binaries though (yet - this should [change](https://github.com/QubesOS/qubes-issues/issues/7240)) so it needs to be built; the process is straightforward and doesn't take much time - just copy/paste the [instructions](https://github.com/tabit-pro/qubes-windows-tools-cross). Getting and installing: thanks to the great work of @jevank et al., QWT can be used or R4.x. There are no binaries yet (though his should [change](https://github.com/QubesOS/qubes-issues/issues/7240)) so it has to be built; the process is straightforward and doesn't take much time - just copy/paste the [instructions](https://github.com/tabit-pro/qubes-windows-tools-cross).
## Post install best practices Meant to optimize resources for use in virtual machine as "vanilla" version of Windows are always bloated. Generally, disable/remove stuff you don';t need. Examples: - if possible install QWT with the XEN PV disk and network drivers ticked. ## Post-install best practices Optimize resources for use in virtual machine as "vanilla" version of Windows are bloated; eg:
- investigate "debloat" scripts ; eg. [this](https://github.com/Sycnex/Windows10Debloater), [this](https://community.spiceworks.com/how_to/148624-how-to-clean-up-a-single-windows-10-machine-image-using-decrapifier), [this](https://www.oo-software.com/en/shutup10), etc. - investigate "debloat" scripts ; eg. [this](https://github.com/Sycnex/Windows10Debloater), [this](https://community.spiceworks.com/how_to/148624-how-to-clean-up-a-single-windows-10-machine-image-using-decrapifier), [this](https://www.oo-software.com/en/shutup10), etc. - disable services you don't need - disable networking stuff in the network adapter's setting (eg. link discovery, file and print server, ...) - set a solid background - ... Try to also install QWT with the XEN PV disk and network drivers ticked (again, don't forget to clone your qube before).
- disk space required by the installer: min 16GB - disk space required by the installer: min is 16GB, I've set it to 20GB
- attaching devices to the qube (attached a USB device ; however there is no 'eject' functionality, maybe because of AME tweaks so one has to make sure data was sync'ed before detaching). - attaching devices to the qube (attached a USB device ; however there is no 'eject' functionality, maybe because of AME tweaks, so I have to make sure data is sync'ed before detaching).

Revision #2

Edited on
2022-02-22
Edited by user
deeplow
(temp: pinging @deeplow ; following comments over at [qubes issues](https://github.com/QubesOS/qubes-issues/issues/3585)) > :warning: **Please note** >; This is a *work in progress guide*, created to crowdsource information, following up on [this github issue](https://github.com/QubesOS/qubes-issues/issues/3585).
(placeholder)(placeholder) <div data-theme-toc="true"> </div>