Unrelated to NTLite.
Google a bit first.
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)
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. Maybe it's related with the "Allow pinning Store app to taskbar" new NTLite setting since that's the only change I did and I had this issue when before I didn't. What about the other issues?
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" The commonly accepted hypothesis suggests the Defaultuser0 profile is created when something goes wrong during the profile creation phase of the main account, and it should be harmless. " source
people who dont use ntlite are getting this.
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'
View attachment 3499
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
" The commonly accepted hypothesis suggests the Defaultuser0 profile is created when something goes wrong during the profile creation phase of the main account, and it should be harmless. " source
people who dont use ntlite are getting this.
because you will see Defaultuser0.
If you skip OOBE using an autounattend.xml file that user is not created in version 1607.
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 you skip OOBE using an autounattend.xml file that user is not created in version 1607.
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.
But I don't want to skip it and if using different presets (and in all of them I didn't skip OOBE) I may not have this issue.
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.
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 Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CloudExperienceHost\Broker\ElevatedClsids\{2b2cad40-19c1-4794-b32d-397e41d5e8a7}]
"AutoElevationAllowed"=dword:00000001
or Power Run.add it with NSudo in a live system