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.
Resolving "Unable to verify Nmap installed version" errors - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Resolving "Unable to verify Nmap installed version" errors
KB0694618

Resolving "Unable to verify Nmap installed version" errors


3284 Views Last updated : Jul 25, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

Nmap automatic installation fails and when attempting to install manually using Nmapinstallation.ps1, you observe the following error:[MID Server file path]\agent\nmap\nmap.exe ready
Verifying Nmap installation
Unable to verify Nmap installed version, waiting 2 seconds......verify-nmap : Timeout: Unable to verify Nmap installed version

Release

Kingston 

Resolution

This is caused by the script being unable to execute the following command:
& "[File path to nmap.exe]" --version

  1. Verify that Nmap.org can be accessed by the MID server
    1. If not, either follow manual installation instructions from Docs (https://docs.servicenow.com/csh?topicname=install-nmap-on-mid-server.html&version=latest) or resolve connectivity issues
  2. When doing the installation, observe that the Nmapinstaller.exe is being unpacked
    1. If not, verify that installer package is not corrupted by trying to manually run
  3. If previous steps are possible, manually install Nmap
    1. If not possible, download a new package. It's likely this one is corrupted.
  4. Attempt to launch & "[File path to nmap.exe]" --version command from Powershell
    1. If this works, attempt manual installation outlined in above Docs again. There may be permissions errors or pieces missing from command execution path.
  5. If step 4 returns null, attempt to run Nmap.exe
    1. If nmap.exe launches, try manual installation again and check permissions/file path/etc

The most common cause is an "MSCVR120.dll is missing" error when attempting to launch nmap.exe.

This can be caused by Antivirus blocking the installation of the package. Alternatively the wrong version of the package may be installed (x64 instead of x84 for older servers).

Related Links

May also be caused by PRB1292511, which is caused by an existing installation of npcap on the system.


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.