Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Registry mapping differs between paexec and psexec #29

Open
deajan opened this issue May 21, 2018 · 3 comments
Open

Registry mapping differs between paexec and psexec #29

deajan opened this issue May 21, 2018 · 3 comments

Comments

@deajan
Copy link

deajan commented May 21, 2018

Hello,

Using Windows 10 (latest 1803 build up to date) x64, paexec does not correctly map HKLM\Software key between normal and system accounts.

Exemple:
paexec -i -s reg add HKLM\Software\Test /v Some /t REG_SZ /d Value /f will create the TEST key in WOW6432Node subkey.
Hence,
paexec -i -s reg query HKLM\Software\Test will work.
reg query HKLM\Software\Test will return an error since it won't find the Test key.

Running the same commands with psexec will work.

Best regards.

@deajan
Copy link
Author

deajan commented May 31, 2018

Playing a bit further with that bug, I can confirm that even running regedit as system with paexec won't show the the registry key created with PSExec.

@n-mam
Copy link

n-mam commented Nov 22, 2020

add /reg:64 switch at the end.

reg query HKLM\Software\Test /reg:64

@poweradminllc
Copy link
Owner

Are you using the 64-bit version of PsExec when you test?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants