Hello,
I noticed I have a defaultuser() folder in my Users folder alongside my main user and the Public folder, is it something that should be there?
**EDIT: It's defaultuser0 (zero)
Ty
Last edited by mibaup; 14 Sep 2016 at 11:58.
Do you have Anniversary Update installed? I also had one such folder but I deleted it manually. Haven't noticed anything strange so far, but I would wait to hear others opinions on this matter before you do anything.
I had the same thing and saw many posts in other forums about the same thing. I uninstalled it by going to lusrmgr.msc and removing it from there just after clean installing the AU when it was made available. I also cleaned it out of the registry and no issues at all. Just make sure you don't remove the normal default user
Do you mean defaultuser0 or defaultuser() ?
The Default user folder is hidden and should be there. DefaultUser0 is a bug and you can delete it (I had it). I've not come across DefaultUser().
When you upgrade you also get a Default.migrated folder in C:\Users and that can also be deleted.
It's a minor bug in Windows. As already said, defaultuser() folder can be safely removed. See this post: Windows 10 Anniversary update Account Unknown and defaultuser0 - Windows 10 Forums
defaultuser() is not the same defaultuser0 though. That is the number 0 not open-close brackets. In the link above the question was about defaultuser0 (as far as my eyes can read the screen prints anyway) and the reply was about defaultuser()
defaultuser0 actually is a user - you can see it in the registry with a SID, you can see it with net user and so on. For some people it is created on clean install and they can't even log on as Windows demands the password and there isn't one. For me it was created on clean install (but I could still create my initial user) so like @shimshom I deleted it but from net user and the registry also - not just deleting the directory in C:\Users.
Is defaultuser() just a folder in C:\Users i.e. a different issue?
The OP's question was and is about defaultuser() (word defaultuser followed by brackets, not digit 0):
There exists no such thing than defaultuser0 account in Windows. I recommend using a screen zoom tool to see how this unnecessary, harmless, risk free to delete user account's name is written.
Already removed one of my posts in this thread :)
OK, checked this a bit more on my machines. Some of them have defaultuser() with brackets, one has defaultuser0 with digit 0. In any case, on all machines the accounts are totally unnecessary and can be removed simply by deleting the folder in main profile folder.
I cannot find any logic why some systems show it as defaultuser() and other as defaultuser0.
The account is shown in Computer Management (#1) and Users folder shows its profile folder (#2), but it's not active user as Advanced User Control Panel shows (#3):
It belongs to no groups:
... and as far as Windows is concerned it has no profile:
It is completely unnecessary to use any drastic methods to delete the user account; it is not active, it has no known profile. Removing the folder is all you have to do.
Did you check net user? Is it the same for both?
Not a big deal as you can't sign on (except for the poor souls who get asked the password when installing). Unlike default.migrated it is an account though.
I got it for all the clean installs I've done for the last few insider builds and the AE - only on my real hardware, not on VM. I recently installed Server 2016 TP5 (which is 10586) and it doesn't happen there. Not sure what that means except it seems recent.
I agree though it isn't terribly important.
Quote
