Skip to main content

FIX CORRUPT WINDOWS7 TEMPORARY PROFILE

Solutions:


While working with Microsoft’s Windows 7 operating system over the past few months I have noticed that sometimes when working with multiple profiles that they can sometimes get corrupted. The error I would receive says that “You are logged into a Temporary Profile.” This means that anything that user would do under that profile would get wiped immediately upon logging off. This problem seems to happen more frequently when it is a member of a domain. This will show you how to fix the profile error in Windows 7 without having to simply wipe the profile. This can come in very handy sometimes and has saved me hours of backing up and transferring profile data.
STEP 1
Restart your PC to release the locks on your profiles.
STEP 2
Log on with another administrative account.
STEP 3
Delete the following folder: (you could also follow the steps below by simply renaming the bad profile to .bak)
1
C:\Users\%username%
STEP 4
Delete the following folder:
1
C:\Users\TEMP
STEP 5
Browse to
1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList
Find the registry key that has the “ProfileImagePath” entry that matches the username of the account.
Make a note of the GUID entry a few lines above, you will need this later. Now delete the entire registry key from the “ProfileList” folder.

STEP 6
Now in the registry, browse one folder above to
1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileGuid
Delete the registry key (that matches the GUID you made note of in Step 5) from the folder.
STEP 7
Restart once again and then you’re done!

Popular posts from this blog

Oracle forms 11g default configuration file formsweb.cfg

#formsweb.cfg defines parameter values used by the FormsServlet # formsweb.cfg defines parameter values used by the FormsServlet (frmservlet) # This section defines the Default settings. Any of them may be overridden in the # following Named Configuration sections. If they are not overridden, then the # values here will be used. # The default settings comprise two types of parameters: System parameters, # which cannot be overridden in the URL, and User Parameters, which can. # Parameters which are not marked as System parameters are User parameters. # SYSTEM PARAMETERS

AFTER LOGON Trigger not perfectly working

AFTER LOGON not perfectly working.  I have tried it on single instance oracle 12c database it's perfectly work but it's not perfectly working on multi instance Oracle 12c database.

I have submitted this matter in oracle forum but not found any perfect answer.

Do you know why  it's not working ???