For me, application launch works with Windows 10, but not with Windows 7. I just use the standard XFCE menu coming with Qubes, nothing special. What are disposable launchers, by the way?
ALT + right click does nothing in my environment. Just left clicking on the window menu button at the left end of the window title shows the window manipulation menu, but with the size change command greyed out (for both W7 and W10).
Changing the window size from the Windows cotrol panel function works for W10 for the few sizes that are supported. For Windows 7, just the large size (1920 x 1024) seems to be supported. Trying to select the other size (800 x 600) gives a warning, and then the system is unresponsive until a timeout occurs, and the size then stays at the larger value.
I mean launcher to start disposable vm when you mark qube as template_for_dispvms.
Could you try remove all application from selected in Qubes Settings Tab and than add it again. Perhaps you have some old files from previous tests.
I have been looking at Qubes for over a year now and recently started using as my daily driver only because I was able to get Windows 10 working (without video/audio/microphone support) to be able to fall back onto some applications that are not available in Linux.
Obviously a better integration of Windows 10 will increase our privacy and attract consciously aware users will be more inclined to start migration journey into world of Linux.
No, I don’t use a disposable VM when trying to execute a command in a Windows VM from the XFCE menu. My last tests with newly created VMs got different results: For Windows 10, the command was executed in the VM, but for Windows 7, where this is more needed, nothing happens.
I tried now to resize the windows via Alt + Right Drag, but, for both W7 and W10, the windows just moved but did not change their sizes, and the W7 window just popped nack to its old location afterwards. For W7 in seamless mode, the application windows behave normally and can be resized.
I tried qvm-create-windows-qube with R4.1 and QWT-cross and it works quite well.
At now it needs to allow file copying in deprecated policy file, so first we have to create it
Then all works as usual except QWT installation, which is need to be done manual in opened window. This is because of MSI package instead of exe file, but I think it will not be a problem to automate.
Second manual action is choosing target on Filecopy operation to copy files to windows qube at one of last stages.
@GWeck application launch from menu didn’t get any problem. Could you try this commands to recreate menu items with your case qvm-appmenus --remove [windows-qube] qvm-sync-appmenus [windows-qube]
If it not helps show output of manual starting application qvm-run -p --service [windows-qube] qubes.StartApp+Accessories-Paint
FWIW: In the recent surveys we’ve run, we’ve gotten MANY requests for Windows 10 support. I don’t think there’s anyone who does not want it, tbh.
Resourcing is the 100% issue. Short of a community contribution coming in that can be fully tested and fully resiliant and fully functional. Which is how this designer is trying to say “works!” but isn’t quite sure how to in this world I understand to be absudly complicated—but for good reasons.
Please do not let my assertions above, interfere with folks trying to crack this tough nut. Just wanted to chime-in that it IS a desired feature by many, and that the only reason the core team has not “prioritized it” (BIG air-quotes) is because it is but a toilet in the bathroom that is Qubes OS… and the core team is all 100% right now on keeping the water running and draining well.
Recreating the menu item via qvm-appmenus --remove and qvm-sync-appmenus did the trick: Now Windows 7 applications can be started from the XFCE menu, too.
By the way, I am using Windows 7 SP1 Professional, fully updated.
To make long story short, did anyone manage to create a script for single-click win10 template deployment with modern QWT that would not require any manual trickery in the middle?
You can build it with instructions and copy to dom0 after that qvm-run -p dispXXX -- cat /home/user/qubes-builder/qubes-packages-mirror-repo/dom0-fc32/rpm/qubes-windows-tools*.noarch.rpm > qubes-windows-tool.rpm
