I’m stuck by trying to install the new qubes tools.
I startet a disp.VM and made there all the steps from jevank (1-3).
The 4th step stucks and show me: file not found by glob: qubes-packages-mirror-repo/dom0-fc32/rpm/qubes-windows-tools*.noarch.rpm
the rpm folder is empty
best regards
qun
I’ve just rebuilt QWT and it works fine (although on a fedora-35 build vm, not fedora-34). Are you sure there was no error during building and that you pasted the right instructions ? (it’s easy to mess up copy/pasting - maybe you pasted the same instructions twice ?).
If you’re sure you did everything right, maybe file an issue ?
Ok, I just did not look at the errors after the step 3 
[MIRROR] wine-core-6.3-1.fc32.x86_64.rpm: Curl error (23): Failed writing received data to disk/application for https://mirrors.xtom.de/fedora/updates/32/Everything/x86_64/Packages/w/wine-core-6.3-1.fc32.x86_64.rpm [Failure writing output to destination] [FAILED] wine-core-6.3-1.fc32.x86_64.rpm: Curl error (23): Failed writing received data to disk/application for https://mirrors.xtom.de/fedora/updates/32/Everything/x86_64/Packages/w/wine-core-6.3-1.fc32.x86_64.rpm [Failure writing output to destination] Error: Error downloading packages: Curl error (23): Failed writing received data to disk/application for https://mirrors.xtom.de/fedora/updates/32/Everything/x86_64/Packages/w/wine-core-6.3-1.fc32.x86_64.rpm [Failure writing output to destination] make[2]: *** [/home/user/qubes-builder/qubes-src/builder-rpm/Makefile-mock.rpmbuilder:93: dist-package-build] Error 30 make[2]: Leaving directory '/home/user/qubes-builder' make[1]: *** [Makefile.generic:197: packages] Error 1 make[1]: Leaving directory '/home/user/qubes-builder' make: *** [Makefile:273: windows-tools-cross-dom0] Error 1
You need to increase VM private volume size I guess.
ok, thanks! That was the point.
The thing is, after I installed it in Windows10, it has no effect no anything.
Maby it’s because I had there the old version of qubes tools?
Or maby it’s because I restored Win10 from the backup made in Qubes 4.0?
Anyway Windows10 crushes after some time (but I think, thats another problem).
Windows VMs in Qubes R4.1 tend to crash when they are restored from an R4.0 backup. See Migrate backups of Windows VMs created under Qubes R4.0 to R4.1 for a discussion and some hints on how to fix the problems from changing the disk drivers.
Ok, Thanks!
But what about the installation of the qubes tools? They had no effect on my Win10. Is also because of the problem of restoring from the 4.0-backup?
You will need QWT 4.1.67 - the old QWT 4.0.1.3 probably will not work under Qubes R4.1. See tabit-pro / qubes-windows-tools-cross
I’ve made all the steps below and installed it… but no effect.
@ all : fyi I’ve made quite a few edits/additions to the wiki (most important addition is the link to @jevank’s binary releases).
What do you mean by “no effect”: none of QWT’s features work, or just a subset ?
can not copy to other VMs for example. So I think that the futures do not work.
Is there any update on qvm-create-windows-qube and QWT being integrated directly into the qubes repos?
I haven’t used either as, last time I checked, you have to manually build QWT on 4.1
qvm-create-windows-qube: no feedback from the author about 4.1 (see the related issue).No need to build QWT, just download the binary release.
I just created a new issue Provide information on integrating Windows into Qubes R4.1 #7381pointing to 2 pull requests for instructions about installing a Windows qube and installing QWT 4.1.67, as well as on migrating Windows VMs from Qubes R4.0 to R4.1.
The instructions in these pull requests are just a first draft - any comments and improvements are highly welcome!
jevank 7 hours ago
Audio … will work with features enabled (stubdom-qrexec and audio-model)
… if audiovm is dom0. If audiovm is sys-audio so far it doesn’t work, or I am not aware of it. I think this is not irrelevant since we are talking about 4.1 and sys-gui and sys-audio are 2 of the biggest changes and innovations and, more important, trends.
Fair enough, I hope we can work it out. But sys-audio and sys-gui are more of a tech preview as I understand it
I patched qemu-stubdom-linux-full-rootfs and changed the domid of module-vchan-sink from 0 to the xid of sys-audio, this is more of a workaround than a solution but at least I have working audio on Windows.
The docs note" An unofficial, third-party tool for automating this process is available here. (Please note that this tool has not been reviewed by the Qubes OS Project. Use it at your own risk.) However, if you are an expert or want to do it manually you may continue below."
I would love to have a better understanding of the difference between these approaches. Is it simply a question of ease of install, or does the qvm-create-windows-qube project provide any features that would not be present with such a manual install? My use case would be a single Windows 10 offline qube that needs QWT.
Relatedly, is qvm-create-windows-qube working on 4.1? This issue gives me the impression it isn’t.