User profile path in windows 7 registry

This has further made most of us depend on the default settings by Windows, either willingly or otherwise. Since, there is always a way out, especially when talking in terms of technical issues. Here are some long followed default settings in Windows that can be changed according to the convenience of each user.

A Windows User profile is the main folder in the system storing user account. That post talks about enumerating a registry key to find the profile information.

The registry location did not change in Windows 7, so the VBScript would still work. Here is the registry location:. The registry location viewed in the Registry Editor appears in the following figure. Using Windows PowerShell, it is really easy to get and to display registry keys. I can enumerate the profile keys in a single command. However, due to the length of registry keys, I am going to do it in two lines.

Next, I use the Get-ChildItem cmdlet dir is an alias to list the registry profile keys:. The following illustrates using these two commands, as well as shows the results on my Windows 7 laptop:.

Now that I have a listing of the profiles on the machine, I need to expand a couple of properties, such as ProfileImagePath and Sid.

This should be a simple matter of using the Get-ItemProperty cmdlet to retrieve the name property from the list above. When I do this, however, an error arises. The command and associated error are shown here.

There are actually two problems going on here. The first is that what is displayed under the Name column in the default output from the Get-Childitem cmdlet is not the actual value stored in the actual name property. I discovered this by piping the results of the Get-ChildItem command to the Format-List cmdlet fl is an alias for Format-List and analyzing the output. The following figure illustrates this process.

From the results discovered via Format-List , I ascertain I need to use the pspath property because it includes the registry provider. I can then pipe the results to the Select-Object cmdlet, and choose the ProfileImagePath property and the Sid property. ProfileImagePath Sid. Don't applies the workaround to computers that are running Windows 10 or a later version of Windows.

It can cause the winget command to stops working. Go to registry and modify the registry value ProfileImagePath to the new path name.

Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly.

Before you modify it, back up the registry for restoration in case problems occur. Log out and log in again by using the user whose name is changed, and the user should use the pervious profile with new path name.