Windows 10: You've been signed in with temporary profile error

Thanks for this thread, everyone. I used this and also the advice here to fix a problem I must have created. I was recovering some data for a friend who had deleted an important folder accidentally and then emptied the recycle bin. I got the files by plugging the drive in as a secondary drive in my system and using a recovery utility, and gave him back his laptop put back together. However, he definitely had some issues after that since his setup looked different, kind of like a fresh install, and he couldn't run his programs. I found out his login was using a temporary profile, and so I researched that and came to this thread. Somehow running his drive as a secondary drive in my system had made some changes. Great, I made more work for myself.

I believe it was the ReProfiler program that did the trick. Several reboots and Windows Updates did not help. Check Disk found no problems and neither did SFC /scannow. ReProfiler did show the profile (user folder) was connected with the correct login, but I did the Assign command anyway since it said on IWR's site that it can fix some things and that must have corrected the problems.

 

I won't start a new thread but I have had something like this happen twice this week. I am on a fresh install of Win 10, so no upgrade here. I have not had this error before., I installed Win 10 in February so it only randomly started this week.

I have auto logon set up and two times this week on start it has taken me to a blue screen that tells me how great PIN are and offers two choices, make PIN now or skip this. If I skip it, it logs me into this temporary profile and only fix I have found is a restart. I made a post on Microsoft forums and they denied it could happen...

I turned auto logon off just now, I would prefer not to have to do it but it beats being locked out of my own pc. I haven't made any changes to registry as I try to avoid doing that.

I don't know why it started doing it though.

 

Wifes work laptop locked her out and gave temporary login. Could not access work files and both pulling our hair out. Tried ReProfiler and it worked first time. Thanks forum members.

 

Despite numerous web searches suggesting various complex fixes for our issue with Roaming Profiles the solution was remarkably simple. I'd like to say we found the answer by doing a deep and complex troll through help files and technical books - but we didn't my colleague and I stumbled on it by chance!
When setting up profile paths there is a data field named Local path, it seems an entry in this field prevents Roaming Profiles from working, we've just upgraded a Local Community Centre's I.T. suite from Windows 7 with Server 2003 to Windows 10 with Server 2012 Essentials R2 took us about 3 weeks to do 10 PC's + server having the Profile issue took a lot of time to resolve.