Windows 10: Apps confused between username and username.computername

Version 10.0.19041

I originally installed Windows 10 as user username. At some stage, probably with a non-destructive repair, I was changed to username.computername.

Most of the time this is not a problem, but occasionally apps decide to install to username and the there are problems when the app is running under username.computername and wants access to AppData under username.

If I delete Users\username Windows creates it again.

I can't uninstall the apps because the uninstall info is in username.

I can't access the registry under username.

Is there any way I can delete username and prevent Windows from creating it again?

:)

 

Log in with username@computername instead of computername\username

Hi all

On a small network that does not have a domain controller, a Windows 10 pro workstation is sharing a folder over the network.

We used to be able to connect to this network share with username@computername instead of computername\username (e.g. shareuser@pc20 instead of pc20\shareuser).

After this Windows 10 Pro workstation updated to 1903, we cannot connect using the username@computername method
but can connect using the computername\username method.

Does anyone know if there is a reason for this?

Is there a way to re-enable this way of connecting to the share?

TIA

 

MS Info Username

I do not know where you are looking but in several places Windows displays usernames as ComputerName\UserName

Your ComputerName is BobcatGames so, if your UserName is Gaming PC, your UserName might well be displayed in some places as
BobcatGames\Gaming PC.

You can check your UserName in any Command prompt or Windows PowerShell window by entering the command net user.

This will show a list of all user accounts [both the one you created & the ones that the system created during installation].

Denis

 

Log in with username@computername instead of computername\username

Thanks for replying Andre, I appreciate the assist.

Could you please confirm that I should do this on the Win10 pro workstation that hosts the share?

Or should I perform this command on the other Win10 workstations that access the share?

(I have just edited the original post to clarify that the share is accessible using the old login method of computername\username.