have you tried adding this reg tweak integrating to the WIN image via NTL? what's the result?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
have you tried adding this reg tweak integrating to the WIN image via NTL? what's the result?
So, what does that mean? That bug fixed in the latest v2004?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.
So, what does that mean? That bug fixed in the latest v2004?
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.
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.
I have this bug even if I do clean installs.
Maybe a bug for a specific CU? With 19041.1 I did not have this problem.
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?
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?