I'm facing a weird problem and I cannot fix it: Temporary profiles. Few days ago I bought Windows 7 Pro. Installed it, all went well... except I was being logged in with a temporary profile for some reason. I have never seen this. Looking online I was able to see some fixes, and I tried applying a lot of them. None fixed my issue. Basically, I use two accounts: The first account is created right after installing Windows and is called "Admin". This account will be the only Administrator account in the system, and will have a password. I only use this account in the first minutes of using the OS. The other account is "Amarildo", a standard account. UAC is at maximum settings, so everytime I need elevated privileges I need to type the "Admin" password. I re-installed Windows to see if this problem would go away, but it didn't. I've used 7 Home Basic, Home Premium, Enterprise (for over a year), and Ultimate (also for over a year) and never seen this issue, only in Pro. Not only I'm sometimes logged in with a Temporary profile, but when I don't then a temporary Admin profile is created whenever I need elevated privileges. This is annoying because some programs will create shortcuts and other files in the Admin profile that won't be accessible because they're in that "TEMP" folder (which now reads 0 bytes) located at 'C:\Users'. I tried every "fix" I could find, none solved the issue. I created a new admin account, now called "Administrador", and deleted the old "Admin" account. So I know for a fact this new profile wasn't corrupted. Result? The same thing happens. What did help for a moment, though, was deleting the ".bak" profile in registry (the correct profile) and edit the current TEMP profile registry to point it to the admin account. This only solved for one boot, unfortunately, now the problem is back. Does anyone have an insight at this? I'm really tired of this problem. I was really happy to be back to Windows 7, but this is REALLY getting on my nerves.
I was under the impression that the .bak key was the real profile key, and just to remove.bak from the end (by renaming) The other key should be renamed and add .temp to the end of it (this is the temp profile) Does all this still happen without any security software installed?
It was. Removing the other key and then removing the ".bak" at the end of the real key didn't help. Does it make any difference? Interestingly, it's never named that way. See: https://i.imgur.com/PvPmemy.jpg 1000 was the "Admin" account (now removed). 1001 is my "Amarildo" account. 1002 is the current "TEMP" account. 1002.bak is the current "Administrador" account. If it did, then that's an even bigger problem BTW, my security software didn't change. Avira + COMODO (just Firewall + HIPS + Sandbox), Malwarebytes Premium (version 3 instead of v2, that's the only thing that changed), and EMET 5.52 (that changed as well, from 5.51 on Windows 10 to 5.52 now). Do you have a "TEMP" folder in C:\Users, @stapp?
Have not heard anything like that before, but one small piece of advice - do not ever make the account named "Administrator", because all versions of Windows have already such an account by default. It is built in hidden account. Otherwise, it may make serious problems in future. The account named "Administrator" is not enabled by default, but may turn on always be if there is a need Windows to run as root, if personal account is damaged, if you have lost your password, etc. Then it helps to run Windows and make what is needed. By default it has no password.
Thing is amarildojr, I did have a temporary profile issue not so long ago. I did all the .bak stuff in registry which didn't fix it either Turned out it was an issue with Emsisoft Ant-Malware which disappeared when I uninstalled Emsisoft. The devs quickly issued a bug fix and Emsisoft is re-installed again and no temp profile issues anymore. This is why I asked about your security software.
Oh boy I can't imagine having to switch security products. I will try removing them one by one to see if one of them is the cause. However, seeing as this is a fairly recent issue with a lot of people, I believe it's a Microsoft-induced bug, because I didn't see this after a fresh install of Windows with all security software installed (meaning no Windows updates were installed).
If you deinstall a security product and your temp profile issue disappears, you have found the "culprit".
Renamed the "1002" key to "1002.temp" and removed the ".bak" from the real profile, now the real key was again renamed to ".bak", the ".tmp" is still there, and a new "1002" was created, pointing to "C:\Users\TEMP.Admin-PC". AAAAAAAAAAAAAAAAAAARRGH! I'll do that now. Hopefully it's Avira It's the only security software I'm willing to change.
Yup. I strongly believe it was Avira. Did some cleaning in the registry profile keys, removed Avira, rebooted twice, and now it seems everything works correctly. Avast, here I come... you better not disappoint me!
@amarildojr I apologize since I have not read all details of your thread in it's entirety. But immediately what came to mind was when I had a similar issue with Windows 7 going into temporary profiles a few years back. In my case, it ended up being profile corruption. I don't know if that is the same case with yours, however, so always proceed with caution and have backups. But ReProfiler (https://sourceforge.net/projects/reprofiler/) is what worked for me at the time. It's open source software and made by the same devs who make Simple Software Restriction Policy (SSRP). But it does seem that your issue is sorted out for now and hopefully the issue of temporary profiles does not come back again. AV software can often cause more problems than they solve, it seems.
Do not celebrate too early You never know... But after a few more days/reboots without the issue you can be "sure" that it is solved.
Damn Avast is invasive. Suddenly quite a lot of programs that didn't connect to the internet (e.g. VeraCrypt, and Blender) were trying to make ipv6 connections. Not only that, but it's very slow when configured to a high to very-high tight settings, and I feel like it's looking at more things than it's supposed to.
Configured Avast so that it's not scanning every single file completely, didn't install a few of it's programs, and now it's working just fine. Love it. I'm 100% positive the problem has gone away since I've re-installed Windows with Avast. https://i.imgur.com/uEl39E5.jpg
