-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qubes Windows Tools Uninstallable #146
Comments
@andrewdavidwong, I don't know if this is maybe an R4.1 Beta issue? |
I don't know the answer, but you might want to have a look at these: https://qubes-os.discourse.group/t/windows-support-in-qubes/4288/ |
Hi, I don't think those are the issues...dom0 seem to be unable to find the repository to install the files (I think). If the repo is still up, I don't see why dom0 shouldn't be able to find it (which may be a Qubes R4.1 Beta issue?); if it's not up, I'll close this and ask @ElliotKillick to update qvm-create-windows-qube. I should note that previously I had success deploying the qvm-create-windows-qube tool ( https://github.com/elliotkillick/qvm-create-windows-qube )---which is dependent on Qubes Windows Tools---subsequent to those issues (except 6289). |
Per the above, QWT for 4.1 does not yet exist, so closing for now. |
Hi, Is there any plan to support QWT for Qubes 4.1 (which is currently in Beta)? Thanks! |
On re-read, are you asking if QWT will be supported for 4.1? |
Hi, I kind of got QWT installed via https://github.com/tabit-pro/qubes-windows-tools-cross; however nothing works (moving files to/from VMs, copy and past to/from VMs, attaching devices) |
Please see updated documentation at https://github.com/Qubes-Community/Contents/blob/master/docs/os/windows/windows-tools41.md. |
Hi,
Neither of these following commands work (am currently on the R4.1 Beta):
sudo qubes-dom0-update qubes-windows-tools
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing qubes-windows-tools
I get the following output:
This precludes the excellent tool for managing windows by @ElliotKillick from working.
The text was updated successfully, but these errors were encountered: