Shane. I have a windows 10 pro x64 machine that I use as part of a domain environment, meaning the user account I use is pulled from the domain controller as well. However, I ALSO link my personal microsoft account with my domain joined profile in order to obtain easy access to my onedrive content and have access to advanced features only availbable when microsoft account is synced. This aspect seems to cause issue with Widows AIO repair, as, when I run a reparse point scan when booted into safe mode, it believes that my imported microsoft account is the main user account and it is missing all its reparse points, even though it was imported solely to be integrated with the domain profile. Anyway, so if run the reparse fix (have to run twice since it finds errors twice), I proceed with the fixes and and reboot my computer. Now, when I reboot my computer, it boots noticeable slower than before and certain programs become unresponsive and need to be forcibly closed. Moreover, when I run any tool which contains a registry cleaner to try to return computer to condition prior to the repairs (I know they are useless, they are just a part of the tools I use), They will find numerous registry errors and fragments. Upon applying those fixes, I restart computer and.....Windows hangs when attempting to load any user profile. Could this have somethign to do with joining my microsoft account to my domain account and the mistaken creation of reparse points for the non-existant account?
