What I posted in #10, 5 days ago, has worked as the problem has not occurred again.
All I can add is that the UWP Apps are being updated in preparation for the 1803 SCU version update feature of Timeline.
Whilst the guides on here are useful they won't be taking in to account the new feature updates of the UWPs.
Same problem here also !
Random , sometimes all goes well and suddenly , WHAM, again this nasty login-problem .
Brinks fix seems not so easy to me , so Im searching for the cullprit or/and waiting for next Windows 10-upgrade . There must be a reason , but its hard to discover , I see lots of people with the same problem , so MS has to fix it someday.............!!
Maybe next upgrade will solve this annoying bug , though I will install with accounts and software in place ( no clean install , costs me too much time for installing all my software again !) Will see...............
Thanks,
The UWP Apps and Store do seem to be the cause of the problem, atleast for the most part.
Instead of updating them, I went ahead and removed all apps and the store entirely(we never use). Tried 150 reboots and the issue did present itself once, but this is atleast much better than before.
For anyone curious on how, there are a lot of guides/scripts out there on selectively removing the apps but I just used in powershell:
Get-AppxPackage -AllUsers | Remove-AppxPackage
**Beware** This removes everything and the store as well.
I only use a local account (Win 10 Pro 1709 Build 16299.248) and have never used the store (knowingly) but am still experiencing the problem. It happened again earlier this evening after I decided to carry out a restart.Nutype said:
It took me a second restart and and then a sign out/sign in before I got back to 'my' local account rather than a temporary profile.
We never used it either. But apparently it does its own thing.I only use a local account (Win 10 Pro 1709 Build 16299.248) and have never used the store (knowingly) but am still experiencing the problem. It happened again earlier this evening after I decided to carry out a restart.
It took me a second restart and and then a sign out/sign in before I got back to 'my' local account rather than a temporary profile.
Try updating and removing unused apps, or removing everything alltogether.
FWIW we are having the same problem on about 12 different Windows 10 and 7 pro computers, it first appeared April 5th so i'm wondering if it was a recent MS update. We are using local user accounts, no domain. The problem seems exacerbated by 3rd party software LogMeIn where the issue happens during a remote session within about 5 minutes of the connection, usually prior to logging off. However it also happens during a regular reboot without any remote sessions. We have seen the issue on a few PCs even without LogMeIn at boot time.
It seems the USERPROFILE environment variable is set to the System Profile user instead of the usual login user, the solution was to change it back to recover, but it keeps reoccurring.
Was wondering if this is due to an issue with fast user switching.
The logs look like this:
76298,Application,Microsoft-Windows-User Profiles Service,ERROR,PC-208829,4/17/2018 2:59:18 AM,1508,SYSTEM\NT AUTHORITY,"Windows was unable to load the registry. This problem is often caused by insufficient memory or insufficient security rights. DETAIL - The process cannot access the file because it is being used by another process. for C:\Users\Admin\ntuser.dat "
76299,Application,Microsoft-Windows-User Profiles Service,ERROR,PC-208829,4/17/2018 2:59:18 AM,1502,Admin\PC-208829,"Windows cannot load the locally stored profile. Possible causes of this error include insufficient security rights or a corrupt local profile. DETAIL - The process cannot access the file because it is being used by another process. "
76300,Application,Microsoft-Windows-User Profiles Service,ERROR,PC-208829,4/17/2018 2:59:18 AM,1515,Admin\PC-208829,"Windows has backed up this user profile. Windows will automatically try to use the backup profile the next time this user logs on. "
76301,Application,Microsoft-Windows-User Profiles Service,ERROR,PC-208829,4/17/2018 2:59:18 AM,1511,Admin\PC-208829,"Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off. "
76302,Application,Microsoft-Windows-User Profiles Service,ERROR,PC-208829,4/17/2018 2:59:19 AM,1508,SYSTEM\NT AUTHORITY,"Windows was unable to load the registry. This problem is often caused by insufficient memory or insufficient security rights. DETAIL - The system cannot find the file specified. for C:\Users\TEMP\ntuser.dat "
76303,Application,Microsoft-Windows-User Profiles Service,ERROR,PC-208829,4/17/2018 2:59:19 AM,1505,Admin\PC-208829,"Windows cannot load the user's profile but has logged you on with the default profile for the system. DETAIL - The system cannot find the file specified. "
Yes, I have seen exactly the same errors in the eventviewer .
It happens random , you never know before , when it happens again , very,very nasty bug !!
Im almost sure its a Win10-update ...........
Question remains ; WHAT can we do about it , will next Win10-upgrade solve this problem................????
This week 6 machines started suffer temp profile error. As the others described, computers lag a bit on loading then enter srtaight in temporary profile with corresponding warning message about main profile being corrupted. Logging off and back on loads the main profile in most cases.
5 of the machines are Win7 and 1 is Win10 all latest versions, some not updated since December 2017 and some regularly updated.
The common thing I spotted all of them have recently Skype 8 installed. Most of them using windows Defender and two using Avast Free. Despite these (Skype, Antivirus, windows updates) nothing else is updated/installed in a long period. Removing Skype or changing the AV program doesn't solve the issue in general, but similar computers with older skype 7/updates are working fine. HDD's are tested with scan disc and surface scan programs, so no issue there.
Has this suddenly stopped happening this week for anyone else? I didn't do anything.
It seems like Microsoft finally fixed whatever was causing the problem.....remotely? It certainly wasn't through any update or KB.
I don't like the feeling though that were completely under the whims of Microsoft, and they can break this again anytime they wish.
Quote