> ⚠️ 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.
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.
[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.
- windows update status (eg. enabled, date last updated, ...)
- display resolution ?
- if audio was tested, does it work ?
- problems with 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: ... (free form post: it could have detailed instructions, known issues, workarounds, hints/tips, description of the author's workflow, productivity tips, ...)
[/details]
Windows ISOs can be downloaded directly from Microsoft (eg. here for Win10).
Unofficial "debloated" ISOs from projects like reviOS, ameliorated 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).
Simple Windows install (gui based): community doc
Or use @elliotkillick's qvm-create-windows-qube scripts (note: works on Qubes OS R4.0 but maybe not on R4.1.
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: 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) so it has to be built; the process is straightforward and doesn't take much time - just copy/paste the instructions.
QWT main features:
- copy/paste between qubes
- copy files between qubes
- attaching devices to the qube
- 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).
QWT changelog/commits are here
Optimize resources for use in virtual machine as "vanilla" version of Windows are bloated; eg:
Try to also install QWT with the XEN PV disk and network drivers ticked (again, don't forget to clone your qube before).
(placeholder)
[details="R4.1 / Windows AME 21H1 / QWT (github master / 2022-02-12)"] @taradiddles / 12 Feb 2022
Windows: - installed from scratch - build/iso: ameliorated 21H1 (downloaded ISO). - disk space required by the installer: min is 16GB, I've set it to 20GB - ram usage after install: <1GB - windows update status: disabled
QWT:
- first installation
- installed just after windows' first boot (windows AME has windows update disabled anyway).
- features selected during installation: Xen PV drivers
- features that were tested to work:
- copy/paste between qubes
- copy files between qubes
- 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).
- networking
- time/clock synchronization
- XEN PV drivers
- features that don't work (possibly with workarounds): ...
- user migration: the profile on c: wasn't migrated (again, maybe because of AME tweaks).
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]
(placeholder)