If you login a server via RDP and you get this error this usually means there is something wrong with your profile, which in turn means any data you save will be saved in a temporary profile, so when you logoff you will loose all your data:
Annoying, to say the least so to fix this there are a couple of steps lets get cracking people.
Check the ProfileList Key
If you navigate to this path below:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
Which will look like this, you are looking for the values that end in .bak here:
That will look like this, so you can see the ProfileImagePath is wrong and the State is 772, the correct valid state is 256 for reference:
This will then show you the wrong profile in the C:\Users folder where the profiles are stored:
Right so to fix this ensure the user is logged off the server and then delete that key and the folder, then get the user to login and all should be back to normal.
If you are getting this for all new users of the server since a point in time then you will need to find the folder called Default in C:\Users
This is a hidden folder so ensure you have the option to show hidden folder enabled
The best way to fix this is to find another server running the same operating system and then copy it from there after deleting this version on the server that is corrupt - I always have a backup of this for each server version so I can restore immediately.
Desktop "not available"
This is usually because the user needs another log off and login again, however sometimes this does not fix the issue, that looks like this:
If you visit the folder as outlined which is C:\Windows\System32\config\systemprofile as below, you will notice you have no Desktop folder as below:
Simple fix, create one, like a ninja and you are done:
If the issues is still there a swift logoff and login is required.
If you visit the folder as outlined which is C:\Windows\System32\config\systemprofile as below, you will notice you have no Desktop folder as below:
Simple fix, create one, like a ninja and you are done:
If the issues is still there a swift logoff and login is required.