You've been signed in with temporary profile error

As it is intermittent ... 3 times only in 2 months, I have a feeling it must occur when I turn my computer on after or during an update perhaps. Not sure.

Squibbler said:

Hmm thanks, do you mean use a Microsoft account? I don't use one at the moment. Prefer not to if I can avoid it.

yes i used a microsoft account to login when using windows 8 and it was migrated to windows 10

hutchy said:

I had this same problem today after upgrading from 8.1 to Windows 10. Manually triggering a windows update check and then a reboot fixed it and made the account migration run correctly.

That worked for me. Thanks!

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.

BruceBon said:

First time I followed instructions for editting registry, making a new profile, copying files back into it, etc, but that was a real pain, so the second time it happened, I looked for a better solution and found it, in the free application ReProfile, downloadable from Source Forge. See IWR Computer Consultancy - Technical Support and advice on IT issues for Small Businesses. : Reprofiler and ReProfiler download | SourceForge.net. There are various warnings, so use at your own risk.

What ReProfiler allows you to do is to re-associate the profile for the account (e.g. C:\Users\JohnDoe) with the account login (JohnDoe). I tried it and it worked, with no problems. In particular, I did:

1. Downloaded and installed ReProfiler in my admin account
2. Restarted Window 10 to make sure that the user account was not logged in or in some wierd state
3. Used the Assign button in ReProfiler to reconnect the user with the profile, and then the Test button to check that it worked.

After that, I logged into the user account, and everything was back to normal. Way easier than the other method!

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.