Skip to content

Published: June 30, 2016 | Applies to:

This registry workshop will help you to fix "You've been signed in with a temporary profile" error in Windows 10/8.1/8/7/Vista.

User accounts facilitates personalized experience to different people using same computer. When an user specific account files or configuration are corrupted, the user may start facing its consequences. One of those symptoms is logging into temporary or roaming profile.

When you discover that Windows keep logging you as a temporary user rather than standard/normal user, then there is something wrong with your profile. In such cases, you’ll get following notification as well:

You’ve been signed in with a temporary profile.

You can’t access your files, and files created in this profile will be deleted when you sign out. To fix this, sign out and try signing in later. Please see the event log for more details or contact your system administrator.

You've Been Signed In With A Temporary Profile In Windows 10

Since Windows is logging you as temporary user, the documents you create will be removed after you re-login. The simplified steps mentioned below will help you to fix this weird issue.

FIX : You’ve Been Signed In With A Temporary Profile In Windows 10

1. Right click on W8K and select Command Prompt (Admin). In the administrative Command Prompt window, type following command:

wmic useraccount where name='<USERNAME>' get sid

*Replace <USERNAME> with your actual user account name.

Once command is executed, note down the security identifier (SID), especially last four digits of SID.

You've Been Signed In With A Temporary Profile In Windows 10

Registry Disclaimer: The further steps will involve registry manipulation. Making mistakes while manipulating registry could affect your system adversely. So be careful while editing registry entries and create a System Restore point first.

2. Press W8K + R and put regedit in Run dialog box to open Registry Editor (if you’re not familiar with Registry Editor, then click here). Click OK.

Windows 10 Registry Editor

3. In the left pane of Registry Editor, navigate to following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

You've Been Signed In With A Temporary Profile In Windows 10

4. When you expand ProfileList key, you’ll find SID specific registry keys. Using the SID we noticed in step 1, spot the correct SID registry key for your profile. In the corresponding right pane, you’ll be able to locate ProfileImagePath, which is expandable registry string (REG_EXPAND_SZ). Since you’re facing this issue, the string data might be pointing to C:\Users\TEMP. Double click on the same string to modify its Value data.

You've Been Signed In With A Temporary Profile In Windows 10

5. In the Edit String box, put the Value data as C:\Users\<USERNAME>. You need to substitute C: with your system root drive and <USERNAME> with your user account name. Click OK.

6. Finally, right click the SID registry key with name same as your SID and ending with .bak. Right click on this key and select Delete. You can now close Registry Editor and reboot.

You've Been Signed In With A Temporary Profile In Windows 10

After restarting your machine, you’ll be able to log in your standard or normal user account.

Checkout following video to understand the steps more better:

Hope this helps!

SHARE: Facebook Google+ Twitter

Leave a Reply

Your email address will not be published. Required fields are marked *

What's New

Recent Comments

  • Kapil Arya : ^^ Thanks for your efforts on this!...

    22 hours ago

  • Kapil Arya : ^^ Then that error should not occur, please retry the steps ...

    1 day ago

  • Karl W Schomburg : I tried this recently with my computer Kapil and it didn't w...

    1 day ago

  • Ria : Hi, thanks.. but in my case, SYSTEM is already the owner o...

    2 days ago

  • Kapil Arya : ^^ Go ahead with FIX 2, see if it helps you!...

    2 days ago

  • Tyler : Guys i can't seem to find Intel HD Graphics 4400, please hel...

    2 days ago

Windows Group Policy Troubleshooting