I have created a standalone window11 qube.
I want to transfer files from other VM to windows qube but i can’t. i can’
t even connect USB or SD card.
Please let me know the solution.
If you have not installed the windows tools, then vm file transfer won’t work.
To be able to attach usb devices including storage devices, you need to run
qvm-features windows-qube-name stubdom-qrexec 1
In the dom0 terminal
Yes, I have not installed the Windows tools. I have already created a Windows-11qube, but is it possible to install them now?
I’m afraid this (all) isn’t possible with a “standalone” installed Windows cube. (others here should) correct me, if I’m wrong, but for my understanding, you have to install and setup a Windows cube in the way, described here.
But please follow these instructions there with all the updated infos here in the forums from the last couple of days (in the specific Windows topics). There are currently made some new and updated versions of windows-tools and updated steps for installing Windows 10/11 here, which aren’t yet changed on the official Qubes documentations.
A windows cube which is setup in this kind of view will have all features you want.
It is. I’m assuming that you are on 4.2.x, so you have two options. You can install the potentially compromised ones as detailed on this page: Qubes Windows Tools (QWT) | Qubes OS
These ones are the ones mentioned in qsb-091
They also do not have gui drivers for windows 10/11
Your other option is to install the new ones currently in the 4.3 testing repositories:
You would need to copy the rpm file to dom0 and install it, or extract the iso and copy it to the windows qube, and mount it to install the .exe
The first link details commands in dom0 that need to be run no matter what windows tools you install, that inculdes
qvm-features windows-qube stubdom-qrexec 1
You will also need to set the default user so that files copied to the windows qube show up in the right place with
qvm-prefs windows-qube default-user username-here
Testsigning needs to be on to install the new tools, so, if you choose to install them, make sure you look through the thread I linked for instructions.
I have already installed qubes-windows-tools-4.1.70-1.fc37.noarch in dom0. If I install qubes-windows-tools-4.2.0-1.fc41.noarch.rpm, will the old version be overwritten?
I believe it will. They are both using the name qubes windows tools, so it should just be upgrading the package.
If you want to go back to 4.1.70 for whatever reason, you can just reinstall it normally as it is in the 4.2 repository
Caution: QWT 4.1.70-1 is only a dummy! The last usable version is 4.1.69-1, which works on both Qubes R4.2.4 and R4.3 but does not provide seamless mode. See the discussion about QSB-091, especially in Qubes OS and Windows 11 Pro as a functional qube under 4.2 possible?.
If you are courageous, you might also try the field test version of QWT 4.2.0, which runs under Windows 10 and 11 but still has some problems with its graphics driver.
I read QSB-091, but it was difficult and I couldn’t understand it.
Even though I intended to install QWT 4.1.70-1 on dom0, it is a fake, so I actually haven’t installed anything.
In reality, 4.1.69-1 is the latest version, but it has vulnerabilities, so installing it is dangerous.
Version 4.2.0 is still incomplete and has issues.
Is this understanding correct?
Even if is it dangerous not to give the Windows qube a net qube?
Telling us what your actual goal with this is could make it easier for you to be helped by the community.
My goals are to set up a Windows Server within Qubes and to transfer files from other VMs to a Windows 11 VM.
Absent a working QWT, you could set
qvm-features QUBE stubdom-qrexec 1.
This will allow you to use a USB device as intermediary for transfer.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
I was able to copy the file. Thank you. Creating a Windows Qube is a hassle