windows app running with system process behaves differently compare to PsExec tool

  • 1 year ago
Comment

1 / 1

When a Windows app is running with the system process, it may behave differently compared to when it's run with the PsExec tool. Here are some possible reasons:

  1. Access to system resources: When an app is running with the system process, it has access to system resources that are not available to other users or processes. This can affect the behavior of the app, especially if it requires access to privileged resources such as system files or network resources.

  2. Permissions and user context: When an app is run with PsExec, it's run in the context of the user who launched PsExec. This may result in different permissions and user context compared to when the app is run with the system process. This can affect the behavior of the app if it relies on certain permissions or user context.

  3. Environment variables: When an app is run with the system process, it may have different environment variables compared to when it's run with PsExec. This can affect the behavior of the app if it relies on certain environment variables.

  4. Interaction with other processes: When an app is run with the system process, it may interact differently with other processes compared to when it's run with PsExec. This can affect the behavior of the app if it relies on certain interactions with other processes.

To troubleshoot the differences in behavior between running an app with the system process and with PsExec, you may need to analyze the specific behavior of the app and the differences in the execution context. You can use tools like Process Monitor or Debugging Tools for Windows to analyze the app's behavior and identify the root cause of the issue.