Re:High CPU use by taskhost.exe when Windows 8.1 user name c...
by ygra on Tuesday May 17, 2016 @10:40AM
(#11714019)
This shouldn't happen. The directory is still there, but it also should still be your profile directory. Changing a user name shouldn't change the SID and make your files inaccessible.
[ Parent
| on HN ]
Re:High CPU use by taskhost.exe when Windows 8.1 user name c...
by JustSomeNobody on Tuesday May 17, 2016 @11:19AM
(#11714358)
Lots of things with Windows should not happen, but they do. It shouldn't forget that I have bluetooth hardware installed, but it does. Windows just (in)conveniently forgets things. Or, conversely, remembers things that should be forgotten.
Re:High CPU use by taskhost.exe when Windows 8.1 user name c...
by nommm-nommm on Tuesday May 17, 2016 @12:04PM
(#11714728)
A lot of weird things happen when you violate Windows' core assumptions about the file system.
Re:High CPU use by taskhost.exe when Windows 8.1 user name c...
by jboles on Tuesday May 17, 2016 @07:37PM
(#11718524)
Not really. Renaming the username-part of the user's home folder has all kinds of data loss potential (apps not being able to find documents, documents linked to each other etc.). Therefore Windows takes the perfectly appropriate approach of leaving the user's files named as they were. Permissions etc. all remain unchanged and allow the same renamed user access. Just the folder on disk shows the old name.