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

Problems restoring Win AppVMs when the original template used a differently named user account #1178

Open
rootkovska opened this Issue Sep 8, 2015 · 1 comment

Comments

Projects
None yet
5 participants
@rootkovska
Member

rootkovska commented Sep 8, 2015

If the default username as used on the original template (specifically on Qubes R2) was different than the one the current (new) template, the AppVM will not startup correctly, as Windows would be looking for the profile in d:\Users\<new_username>, while the AppVM will have only d:\Users\<old_username>.

A work-around is to switch to raw Windows template (w/o Qubes Windows Tools), create another temp user, log out from the <new_username> user, copy the c:\Users<new_username> onto d:\Users. Then shutdown and switch back to the proper Win template (with Qubes Windows Tools). Some things will not work, notably the shortcuts in SendTo context menu for copying files to other VMs. This is likely a result of old content of d:\Users\Default. One can manually copy files away from such old AppVM using qrexec-client-vm, but we need a better solution here.

@unman

This comment has been minimized.

Show comment
Hide comment
@unman

unman Apr 16, 2017

Member

@andrewdavidwong I Have not been able to test this - please change milestone to 3.2 updates

Member

unman commented Apr 16, 2017

@andrewdavidwong I Have not been able to test this - please change milestone to 3.2 updates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment