How to fix temporary profile issue in windows 10 | Server 2016

How to fix the temporary profile issue on any windows operating system, It’s corrupted profile we will discuss to fix and make users to login as expected.

Generally, windows administrator deal with many servers and desktop machines every day as part of their work and they work on user profile issues, end-users report they are getting a temporary profile, as a result, not losing their customization in terms of IE favorites, Mapped drives, and features, when a user is logged in with a temporary profile some may not work as expected too.

This article explains how one can resolve this issue please find the steps mentioned below.

Step 1

The reason behind the temporary profile is the corruption of the user profile, we need clear that corrupted profile on the machine where the user is connected, and we need to clean the user corrupted profile registry entries.

Login to with admin rights on the computer where the temporary user profile is loading and open the registry editor, (use Regedit) shortcut key from run command open registry editor.

• Go path HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ ProfileList and search with a user name that is loading a temporary profile, find the registry SID key with .bak as an extension and delete it, make sure you are deleting the .bak registry and also the user is not currently active or connected on the computer.

See the screenshot of how the corrupted user profile registry key.

Step 2:

Open my computer open C:\users folder and delete all temp profiles if you find anything, see the screenshot, one has to delete these temp profiles on all the affected machines or where temp profile is loading.

Step 3

Open system properties by clicking on MyPC selecting properties and then click on Remote settings, Advanced and click on settings under user profile, delete any temporary profile if notice anything.

This definitely clears the temporary profile issue in windows 10 or window server 2016 or 2012 for any questions and comments please reach out to us.

Thank you for reading this article.