Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upProblems restoring Win AppVMs when the original template used a differently named user account #1178
Comments
rootkovska
added
bug
C: windows tools
P: major
labels
Sep 8, 2015
rootkovska
assigned
omeg
Sep 8, 2015
rootkovska
added this to the Release 3.1 milestone
Sep 8, 2015
marmarek
modified the milestones:
Release 3.1 updates,
Release 3.1
Feb 8, 2016
andrewdavidwong
added
help wanted
and removed
help wanted
labels
Jan 14, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
unman
Apr 16, 2017
Member
@andrewdavidwong I Have not been able to test this - please change milestone to 3.2 updates
|
@andrewdavidwong I Have not been able to test this - please change milestone to 3.2 updates |
andrewdavidwong
modified the milestones:
Release 3.2 updates,
Release 3.1 updates
Apr 16, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rootkovska commentedSep 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 onlyd:\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.