How to Connect to a Remote Registry in Windows 11 and 10

“Connect Network Registry” lets you edit another Windows PC’s registry without leaving your desk, but the connection won’t work until several security requirements are met. If you’re hoping this works quickly, start by enabling the required service on the target PC.

Fix #1: Check the remote computer’s requirements

Remote Registry requires administrator access and a working network connection. Use it only on computers you own or manage.

1. Confirm that the target computer is awake and connected to the same trusted network or business VPN service.

2. Sign in with an account that belongs to the target computer’s Administrators group.

3. Make sure the account has a password. Windows blocks remote administrative access from accounts with blank passwords.

4. Open Settings > Network & internet and confirm the active connection uses the Private network profile when appropriate for your trusted network.

5. Open Windows Security > Firewall & network protection and confirm Windows Firewall allows the required remote administration, RPC, and File and Printer Sharing traffic.

Don’t disable the firewall completely. Firewall rule names and availability can vary by Windows edition and organizational policy.

6. Press Windows + R, type cmd, and press Ctrl + Shift + Enter to open Command Prompt as administrator.

7. Run ping REMOTE-PC, replacing REMOTE-PC with the target computer’s name.

You should receive replies from the target address. If ping is blocked by policy, confirm connectivity through your organization’s approved network-management tools instead.

Fix #2: Start the Remote Registry service

The Remote Registry service is normally stopped or disabled on Windows client PCs. Set it to Manual so it runs only while you need it.

1. On the target computer, press Windows + R.

2. Type services.msc and press Enter.

3. Find and double-click Remote Registry.

4. Change Startup type to Manual.

5. Select Apply.

6. Select Start, then select OK.

The Remote Registry entry should now show Running. So far, so good. The target PC is ready to accept a connection.

If you can’t sit at the target computer, try managing its services remotely:

1. On your administrator PC, press Windows + R.

2. Type services.msc and press Enter.

3. Right-click Services (Local) and select Connect to another computer.

4. Enter the target computer’s name or IP address, then select OK.

5. Open Remote Registry, set Startup type to Manual, and select Start.

This remote method requires working administrative access and firewall rules. If it fails, enable the service locally or use the command method below.

Fix #3: Start Remote Registry with a command

sc.exe can configure and start the service from an elevated Command Prompt. This is useful when the Services console won’t connect.

1. Open Command Prompt as administrator on your administrator PC.

2. Set the remote service to manual startup:

sc \\REMOTE-PC config remoteregistry start= demand

3. Start the service:

sc \\REMOTE-PC start remoteregistry

You should see STATE change to RUNNING. Replace REMOTE-PC with the actual computer name in both commands.

If you need the service to start automatically in a managed environment, use this command:

sc \\REMOTE-PC config remoteregistry start= auto

I’d skip automatic startup unless an endpoint management tool depends on it. Leaving Remote Registry available increases the computer’s remote attack surface.

Fix #4: Connect through Registry Editor

Registry Editor can connect after the target service, network, and credentials are ready.

1. On your administrator PC, press Windows + R.

2. Type regedit and press Ctrl + Shift + Enter.

3. Approve the User Account Control prompt.

4. Select File > Connect Network Registry.

5. Enter the target computer’s DNS or NetBIOS name in the Enter the object name to select box.

6. Select Check Names.

7. Select OK after Windows resolves the computer name.

If Windows asks for credentials, enter an administrator account for the target PC. For a domain account, use DOMAIN\username; for a local account, use REMOTE-PC\username.

8. Expand the remote computer’s node in Registry Editor.

You should see HKEY_LOCAL_MACHINE and HKEY_USERS for the remote computer. Those are the remote hives available through this connection.

Export any key before changing it: right-click the key, select Export, and save the .reg file somewhere secure. Registry changes can break Windows or an installed application immediately.

Fix #5: Find the correct computer name

A short computer name is often more reliable than browsing the network list.

1. On the target computer, open Command Prompt.

2. Run:

hostname

3. Use the displayed name in Registry Editor’s Select Computer dialog.

You can also inspect registered NetBIOS names with the original command:

nbtstat -n

4. If the name doesn’t resolve, enter the target computer’s IP address in Select Computer.

A successful IP connection points to a DNS or name-resolution problem rather than a Registry Editor problem. Check the local DNS configuration, VPN connection, or Wi-Fi router before changing firewall rules.

Fix #6: Use PowerShell Remoting for a specific change

PowerShell Remoting is a better fit when you know the exact key or value to inspect. It also supports repeatable changes and logging without leaving Remote Registry running.

1. On the target computer, open Windows PowerShell as administrator.

2. Enable PowerShell Remoting:

Enable-PSRemoting -Force

3. On your administrator PC, open Windows PowerShell as administrator.

4. Test the remote session:

Invoke-Command -ComputerName REMOTE-PC -ScriptBlock { $env:COMPUTERNAME }

The command should return the target computer’s name.

5. Read a registry key remotely:

Invoke-Command -ComputerName REMOTE-PC -ScriptBlock {
    Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion"
}

6. To change a known value, run the relevant registry command inside the same Invoke-Command block. Test it on one computer before applying it elsewhere.

PowerShell Remoting must already be permitted by the target’s firewall and security policy. In domain environments, Group Policy or a remote monitoring and management platform is usually easier to audit across several PCs.

Fix #7: Resolve “Access is denied”

“Access is denied” means Windows reached the remote computer but rejected the account or its permissions.

1. Confirm the account belongs to the target PC’s Administrators group.

2. If you’re using a domain account, enter it as DOMAIN\username.

3. If you’re using a local account, enter it as REMOTE-PC\username.

4. Confirm both computers can contact the domain controller when domain credentials are involved.

5. Ask your administrator whether User Account Control, firewall policy, or endpoint security software restricts remote administrative access.

Don’t weaken User Account Control or create broad firewall exceptions solely to bypass this error. Use an approved domain administrator account or perform the registry edit through Remote Desktop or Quick Assist.

Fix #8: Check why the registry change reverted

A successful edit can still disappear after a restart, sign-in, Group Policy refresh, or device-management sync.

1. Confirm you edited HKEY_LOCAL_MACHINE for a computer-wide setting.

2. Confirm you edited the intended user’s hive when changing a per-user setting.

3. Restart the affected service or computer if the setting requires it.

4. Run gpresult /r in Command Prompt to check whether Group Policy manages the setting.

5. Check your organization’s device-management console if the computer receives MDM policies.

If policy controls the value, change the policy rather than repeatedly editing the registry. Direct edits will continue to be overwritten.

Fix #9: Disconnect and disable Remote Registry

Stop the service after finishing the edit. This closes an unnecessary remote-management path.

1. In Registry Editor, select the remote computer’s node.

2. Select File > Disconnect Network Registry.

3. On the target computer, open services.msc.

4. Double-click Remote Registry.

5. Select Stop.

6. Set Startup type to Manual or Disabled, based on your organization’s policy.

7. Select OK.

The remote computer should disappear from Registry Editor, and the service should show no running status.

When the connection still doesn’t work

Use Remote Desktop or Quick Assist to make the change locally if Remote Registry remains blocked. For several managed computers, use PowerShell Remoting, Group Policy, or your organization’s device-management platform; these options provide better control and audit records.

Windows 7 can still expose Remote Registry, but it has been unsupported since January 14, 2020. Move any remaining Windows 7 computer off production networks instead of opening additional remote-management access.

Conclusion

Fix #2, which starts Remote Registry locally with Manual startup, usually clears the connection problem and is worth trying first. Remote Registry is a solid choice for an occasional edit, but repeated access failures or settings that revert point to firewall, domain, or device-management policies that need an administrator’s attention.