defaultuser0 folder inside the Users folder
- Thread starter Windows 10 User
- Start date
Although I have not looked at his preset or anything at all, I did talk with nuhi about it when having issues with 1809 x64 and integrating/cleaning cumulative updates - if for some reason the installation process is missing files to access the profile, you get a message that the installation cannot continue, then after a reboot the defaultuser0 profile is created - the reason it's creating the defaultuser0 profile is indeed not ntlite related, but the cause for it could be (i said could be, not saying it is obviously)
Windows 10 User
Active Member
I did but I wasn't having it previously until very recently (only after using latest NTLite version) and supposedly it shouldn't happen on the most recent Windows 10 builds according to what I've searched. What about the other issues I'm having?
Well, I'm not on 1809 but on 2004 (and I've also integrated the latest CU, DU, SSU, CU for .NET Framework and the 20H2 Enablement Package with the same results) and I wasn't having this issue before. Maybe it's related. I didn't have any message stating the install cannot continue, too.
Last edited:
SM03
Active Member
this is the case for me as well, lately, I've also seen 'defaultuser100000' folder under users folder which wasn't there earlier, I don't know from when & how this been created but as Win10 user said, like him, while using earlier NTL, I didn't have this.
Maybe this is something that you can investigate nuhi
EDIT: For me, it is not 'defaultuser0', it's 'defaultuser100000'
Last edited:
SM03
Active Member
yes, after a little bit of googling, I came to know that this bug is there since 2016, & strange enough, no one knows why MSFT didn't patch this up in last four years, in & with 8 different Windows 10 version update released since 2016
Windows 10 User
Active Member
What's weird is that after using different presets on NTLite, sometimes I have this issue and other times I don't.
And how can we know something went wrong during the profile creation phase of the main accoint in the first place?
Last edited:
Windows 10 User
Active Member
I was talking before knowing I even have that folder (like on the OOBE, for instance), obviously. What are the consequences of something going wrong during the profile creation phase of the main account (besides having this defaultuser0 folder, of course)?
Last edited:
Windows 10 User
Active Member
But I don't want to skip it and if using different presets I may not have this issue.
Last edited:
SM03
Active Member
I skip the OOBE by creating a default user profile in NTL, is that the reason for creating that foul folder? I really don't think so as many other users reported the same while they didn't skip anything.
If the behavior is equal to 1607 if you skip OOBE the folder is not created. If you are getting this then 2004 behaves differently.
In 1809 after a period of idle time this folder will be deleted perhaps in 2004 this will also occur. Maybe that's why every hour a different behavior.
Anyway this is a problem in Windows and has nothing to do with NTLite.
Last edited:
Windows 10 User
Active Member
Well, in my case they were never deleted and if using different NTLite presets I may not have it.
francis11
Active Member
As nuhi already stated- not a NTLite issue - i've seen it for years in windows 10 - but maybe this link can put some light on the Defaultuser0 as Kari mentioned it in 2017 first time; It's Windows 10 by design - Thank you.
Windows 10 User
Active Member
It should be automatically removed and it isn't.
EDIT: I have this problem if using a 19041.1 Enterprise x64 pt-pt image with only the latest updates integrated so it isn't NTLite's fault.
Last edited:
I tried to use SetupComplete.cmd to delete the user but the setup is not completed. It seems that this user is required for OOBE.
Abstract
Defaultuser0 account profile is created to support OOBE. The account is supposed to be deleted after reaching the desktop or upon the next logon of any admin user. We are seeing instances where this is not deleted.
Cause
This is a known issue. The API calls from RemoveTempOOBEWork fails because ElevationBrokerManager returns Access is denied - 0x80070005 (2147942405).
Resolution
This issue is fixed in the newer builds of Windows 10.
Workaround:
Change the following regkey to be deleted by the system:
HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows\ CurrentVersion\ CloudExperienceHost\ Broker\ ElevatedClsids\ {2b2cad40-19c1 -
AutoElevationAllowed=1
https://answers.microsoft.com/en-us...f/e2333e94-ef5f-4932-8754-fd4ce27ae33b?page=6
Abstract
Defaultuser0 account profile is created to support OOBE. The account is supposed to be deleted after reaching the desktop or upon the next logon of any admin user. We are seeing instances where this is not deleted.
Cause
This is a known issue. The API calls from RemoveTempOOBEWork fails because ElevationBrokerManager returns Access is denied - 0x80070005 (2147942405).
Resolution
This issue is fixed in the newer builds of Windows 10.
Workaround:
Change the following regkey to be deleted by the system:
HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows\ CurrentVersion\ CloudExperienceHost\ Broker\ ElevatedClsids\ {2b2cad40-19c1 -
AutoElevationAllowed=1
https://answers.microsoft.com/en-us...f/e2333e94-ef5f-4932-8754-fd4ce27ae33b?page=6
So the simplest solution is to add this .reg with NTLite to the image offline or add it with NSudo in a live system (the key is protected and only TrustedInstaller has write permission). If the user is not deleted restart Windows.
I tested this on LTSB 2016 (version 1607) and it worked. After restarting Windows the user was deleted.
I tested this on LTSB 2016 (version 1607) and it worked. After restarting Windows the user was deleted.
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CloudExperienceHost\Broker\ElevatedClsids\{2b2cad40-19c1-4794-b32d-397e41d5e8a7}]
"AutoElevationAllowed"=dword:00000001or Power Run.