defaultuser0 folder inside the Users folder

W

Windows 10 User

Active Member
I have a defaultuser0 folder inside the Users folder. I used a Windows 10 Enterprise 19041.1 x64 pt-pt image.

EDIT: Weird, after using different presets on NTLite, sometimes I have this issue and other times I don't.
 

Attachments

  • Captura de Ecrã (1).png
    Captura de Ecrã (1).png
    67.9 KB
  • preset.xml
    30.9 KB
Last edited:
AeonX said:
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
Click to expand...
have you tried adding this reg tweak integrating to the WIN image via NTL? what's the result?
 
SM03 said:
have you tried adding this reg tweak integrating to the WIN image via NTL? what's the result?
Click to expand...

Yes I tested this in 1607 and the key was successfully integrated and when booting the image on the VM the defaultuser0 folder did not exist :)

NTLite since version 1.8.0.7137 can integrate reg files into protected keys see the changelog:

- Registry: REG file integration now can apply to protected keys

https://www.ntlite.com/changelog-2019/
 
I tested the ISO of 19041.1 Enterprise en-US untouched without applying the reg tweak and on the first boot the defaultuser0 folder existed but after a reboot the folder was deleted.
 
AeonX said:
I tested the ISO of 19041.1 Enterprise en-US untouched without applying the reg tweak and on the first boot the defaultuser0 folder existed but after a reboot the folder was deleted.
Click to expand...
So, what does that mean? That bug fixed in the latest v2004?
 
SM03 said:
So, what does that mean? That bug fixed in the latest v2004?
Click to expand...

It seems so at least in a clean installation. In version 1809 this bug does not exist either and there is the same behavior (the folder is deleted after a reboot). In the MDL some commented that this bug appears when doing an in-place upgrade.
 
AeonX said:
It seems so at least in a clean installation. In version 1809 this bug does not exist either and there is the same behavior (the folder is deleted after a reboot). In the MDL some commented that this bug appears when doing an in-place upgrade.
Click to expand...

I reinstalled Windows and this time the default0 folder was deleted by itself and I didn't even had to reboot.

Also, there's a new $WinREAgent folder on the root of the drive that it seems to be related with WU.
 
It looks like the defaultuser0 folder is present when you use a build with the bug present in it and then do an in-place upgrade. Even if the new build installed does not have the bug it will keep the folder (not delete it).

I particularly only do clean installations to avoid this kind of problems and many others. Not even in linux I trust to install a new version on top of an old one.
 
AeonX said:
It looks like the defaultuser0 folder is present when you use a build with the bug present in it and then do an in-place upgrade. Even if the new build installed does not have the bug it will keep the folder (not delete it).

I particularly only do clean installations to avoid this kind of problems and many others. Not even in linux I trust to install a new version on top of an old one.
Click to expand...

I have this bug even if I do clean installs.
 
Am confused, just tell me if anyone noticed this bug i.e. the defaultuser folder after the clean installation of the newest 20xx Windows 10 builds? or not?
 
SM03 said:
Am confused, just tell me if anyone noticed this bug i.e. the defaultuser folder after the clean installation of the newest 20xx Windows 10 builds? or not?
Click to expand...

Yes, I also have this bug after a clean install with the latest build, like I've told. It looks like the folder goes away by itself.
 
Last edited:
SM03 said:
Am confused, just tell me if anyone noticed this bug i.e. the defaultuser folder after the clean installation of the newest 20xx Windows 10 builds? or not?
Click to expand...

I only saw this happen in version 1607. From version 1809 onwards I cannot reproduce this problem here on clean installations. I haven't tested the builds between 1607 and 1809 so I don't know what build exactly that was fixed in.
 
You must log in or register to reply here.
Back
Top