求助：PSExec无法在远程PC上启动Regedit.exe

Hey there, I get it—managing 25k workstations means you rely on tools like PsExec to keep things running smoothly, so this sudden failure must be frustrating. Let’s walk through targeted fixes to get your registry imports working again:

1. Verify Basic Connectivity & Permissions #

First, rule out the foundational issues that often break PsExec:

• Test if the remote Win7 machine is reachable and SMB is working: Run ping \\remotecomputer and net view \\remotecomputer from your Win10 PC. If either fails, you’ve got a network or SMB sharing issue to fix first.
• Confirm your domain\adminaccount has local admin rights on the remote PC: Use net user \\remotecomputer domain\adminaccount to check. Group policy changes or permission revokes are a common culprit here.

2. Adjust PsExec Parameters to Bypass UAC & Context Issues #

Win7’s UAC and execution context can block Regedit even with admin rights—try these tweaks:

• Add the -h flag to run with elevated privileges: This ensures PsExec uses your account’s elevated token, which often gets past UAC restrictions for GUI apps like Regedit. Updated command:

  psexec \\remotecomputer -h -u domain\adminaccount regedit.exe /i /s "\\server\..."
  

• Test if the remote PC can access your registry file share: Run this command to verify the share is reachable from the remote context:

  psexec \\remotecomputer -u domain\adminaccount cmd /c dir "\\server\..."
  

  If this fails, check the share’s permissions to make sure your admin account has read access from the remote machine.

3. Swap Regedit for Command-Line Registry Import #

Regedit’s GUI nature can introduce unexpected blocks—switch to the more reliable reg command-line tool instead:

psexec \\remotecomputer -u domain\adminaccount reg import "\\server\..."

This achieves the same registry import without launching the Regedit GUI, avoiding any GUI-related restrictions on the remote Win7 PC.

4. Check for Group Policy or System Restrictions #

• Verify Regedit isn’t blocked via group policy on the remote Win7 PC: Open gpedit.msc on the remote machine, navigate to User Configuration > Administrative Templates > System, and ensure Prevent access to registry editing tools is set to Not Configured or Disabled.
• Update PsExec to the latest version: Old Sysinternals tools can have compatibility gaps with newer Windows 10 builds or patched Win7 systems. Grab the latest PsExec from the official Sysinternals Suite.

5. Debug with Additional PsExec Flags #

If you’re still stuck, use these flags to gather more info:

• -d: Runs the process without waiting for it to exit, which can bypass hang-related issues.
• -e: Skips loading the user’s profile, which fixes problems caused by corrupted or restricted profile settings on the remote PC.

Give these steps a shot—odds are one of them will get your registry updates back up and running.

内容的提问来源于stack exchange，提问作者user3496063