Unknown User

ok, keep digging down on the top most folders on C:\

remove when found

A lot of security is inherited, so it really isn't that much work. It is some work, though.

Wash, rinse, repeat.

You're looking at the security tab on folders starting at the topmost C:\ and D:\
You've done this on other folder (C:\Users\Bob for instance) so I don't need to explain the how.

Then working your way down the folder tree
C:\Program Files
C:\Program Files (86)
C:\ProgramData
C:\Users
C:\Windows

You'll examine the properties of each folder, security tab

If you find that -1004 user, you want to edit the security for that object (folder)
select that mystery user -1004 and remove that entry ( remove button)

Make sure you press the OK button and answer yes to any dialog windows that might pop up

You'll continue doing that same process for each folder I listed above.

The reason I wanted you to go into the advanced properties page is because it's easier to tell ig the descriptor is inherited - it uses the word instead of greyed out check boxes.

Simply put
1) right click a folder
2) select properites
3) select the security tab
4) look for user -1004
5) found? edit and remove
6) not found exit and move on to the next folder

It's easiest if you do it all in one session working down the folder tree, but you don't have to. You can remove the user
-1004 as you come across it.

If the security descriptor comes form the folder above it (inherited), the user will reappear, so you have to work your way up the tree in that case.

Glad to hear you managed to unravel the mystery user.

In case you still want an answer re: two entries: if you look closely - on the right side, there are further definitions
1) this folder and
2) subfolders and

different permissions can be assigned to access objects (folders) based on the hierarchy of the folder (this folder) or (subfolders)

If you observe other folders with the -1004 user defined in the security descriptor, you have good working knowledge on how to fix it.

Thank you for marking the thread solved too.

Regards,

Bill