Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Error calling "C:\Windows\Sysnative\WindowsPowerShell\v1.0\powershell.exe" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Error calling "C:\Windows\Sysnative\WindowsPowerShell\v1.0\powershell.exe"
KB0749654

Error calling "C:\Windows\Sysnative\WindowsPowerShell\v1.0\powershell.exe"


8566 Views Last updated : Apr 7, 2024 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

MID Server will have an error which includes:

C:\Windows\Sysnative\WindowsPowerShell\v1.0\powershell.exe

Example when running upgrade:

Error encountered when invoking PowerShell, the result from running '"C:\Windows\Sysnative\WindowsPowerShell\v1.0\powershell.exe" -noninteractive -nologo -noprofile -command "$ver = if (Test-Path Variable:\PSVersionTable) { $PSVersionTable.PSVersion } else { (get-host).Version }; 'full_version:' + $ver.ToString() + ', major_version:' + $ver.Major"

Example when enabling Credential-less discovery:

"C:\Windows\Sysnative\WindowsPowerShell\v1.0\powershell.exe\" is not recognized as an internal or external command

Release

All currently supported releases

Cause

This error is due to a 64-bit host running a 32-bit MID JRE. Sysnative is a virtual Windows folder, a special alias, that can be used to access the 64-bit System32 folder from a 32-bit application or script.

To confirm the version a MID server is using:

  1. Navigate to the MID server list
  2. Add column "MID Java command directory" to see the location of the JRE being used
  3. On the MID server host navigate to the directory where the JRE is
  4. Run command "java -version"
  5. Example of 64-bit JRE:
    openjdk version "1.8.0_181-sncmid1"
    OpenJDK Runtime Environment (build 1.8.0_181-sncmid1-b13)
    OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
    Notice above the "64-bit" in the version.

Resolution

Use OOB MID server JRE

  1. Stop the MID server service
  2. Move the current MID's JRE folder to another location
  3. In the instance, navigate to "MID Server > Downloads" and download the 64-bit MID package
  4. Move the new 64-bit JRE folder into the directory specified in "MID Java command directory" field of the MID server
  5. Restart the MID server service
  6. Navigate to the MID server record in the instance and wait for the MID server status to change to up
  7. Attempt to reproduce issue in order to confirm resolution

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.