Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-12-15 07:53:07 -05:00
Code Issues Projects Releases Packages Wiki Activity

Merge remote-tracking branch 'GWeck/master'

Browse source
This commit is contained in:
qubedmaiska 2025-10-25 17:47:19 -04:00
commit 56db515f58
No known key found for this signature in database
GPG key ID: 204BCE0FD52C0501
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
user/templates/windows/qubes-windows-tools.rst
View file

@ -42,7 +42,7 @@ Qubes Windows Tools (QWT) are a set of programs and drivers that provide integra
Due to the security problems described in `QSB-091 <https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-091-2023.txt>`__, installation of Qubes Windows Tools is currently blocked. Instead, a text file containing a warning is displayed. Currently, it is difficult to estimate the severity of the risks posed by the sources of the Xen drivers used in QWT possibly being compromised, so it was decided not to offer direct QWT installation until this problem could be treated properly. While Windows qubes are, in Qubes, generally not regarded as being very trustworthy, a possible compromise of the Xen drivers used in Qubes Windows Tools might create a risk for Xen or `dom0` and thus be dangerous for Qubes itself. This risk may be small or even non-existent, as stated in QSB-091. If you **understand** this risk and are **willing to take it**, you can still install the previous version of Qubes Windows Tools **for Windows 7**, which will work for Windows 7, but not for Windows 10 or 11.
**For Windows 10 or 11**, currently, there is no official, final QWT version available, but for Qubes R4.3, a preliminary testing version has been developed and can be used in Qubes R4.2. This version is not subject to the security problems stated above, but it should be noted that it is not yet in its final, debugged state and so may still show some errors. The new Qubes graphics driver is not yet fully compatible with Windows and should not be installed, as it may cause the Windows installation to break and render it unusable. If the driver is installed despite these risks and is working at least partially, switching to seamless mode and staying there will probably work quite satisfactorily, but switching to and from non-seamless mode is likely to cause trouble, as well as changing the screen resolution will do there. So, usage of the new Qubes graphics driver should be avoided unless a casual reboot of the Windows VM is acceptable, even if it is partially working.
**For Windows 10 or 11**, currently, there is no official, final QWT version available, but for Qubes R4.3, a preliminary testing version has been developed and can be used in Qubes R4.2. This version is not subject to the security problems stated above, but it should be noted that it is not yet in its final, debugged state and so may still show some errors. The new Qubes graphics driver is not yet fully compatible with Windows and should not be installed, as it may cause the Windows installation to break and render it unusable. If the driver is installed, despite these risks, and is working at least partially, switching to seamless mode and staying there will probably work quite satisfactorily, but switching to and from non-seamless mode is likely to cause trouble, as well as changing the screen resolution will do there. So, usage of the new Qubes graphics driver should be avoided unless a casual reboot of the Windows VM is acceptable, even if it is partially working. In Windows 11 25H2, using the Qubes graphics driver has practically no effect amd will not provide seamless mode unless the ``qvm-features`` parameter ``gui`` is set to ``1``.
**Note**: If you choose to move profiles, drive letter ``Q:`` must be assigned to the secondary (private) disk.

4
user/templates/windows/qubes-windows.rst
View file

@ -261,14 +261,14 @@ Start Windows VM
- For version 24H2, the following actions allow you to install Windows 11 with a local account, if the VM is defined, at least temporarily, without a netVM:
- For versions 24H2 and 25H2, the following actions allow you to install Windows 11 with a local account, if the VM is defined, at least temporarily, without a netVM:
- After some reboots, the VM will show a window allowing the selection of an installation country. In this window, type Shift-F10 to open a console window.
- In this window, type ``oobe\bypassnro``. The VM will then reboot and return to the country selection window. The network connection window will now show an option “I don’t have internet”, allowing you to define a local account.
- In new preview builds of Windows (26120 and beyond, and eventually the next release version), the ``oobe\bypassnro`` command has been erased and no longer works. Instead, there’s a new command called start ``ms-chx:localonly`` that does something similar. In this case, proceed as follows:
- In some preview builds of Windows (26120 and beyond, and possibly a release version after 25H2), the ``oobe\bypassnro`` command has been erased and no longer works. Instead, there’s a new command called start ``ms-chx:localonly`` that does something similar. In this case, proceed as follows:
- Follow the Windows 11 install process until you get to the Sign in screen. Here, type Shift-F10 to open a console window.