ebsnvme-id.exe - Analyze and How to Fix Errors

⚠️ Important Notice: exe driver update for optimal performance. Essential for system stability and speed enhancement. Manually replacing system libraries can brick future Windows updates or cause critical system failures.

Architecture:	64-bit (x64)	Compatible with only 64-bit Windows
Creation date	24.06.2021 22:09:41
File version	1.0.0.3
Antivirus scan	✅ Clean	No viruses detected.
Digital signature	✅ Have signed	File have signature, it is original file.
Hash Integrity	✅ MD5: Verified	File Hash protection is missing.
File size	280.8 kb.	287560 bytes.

Hashes:

MD5: 3a0348502d906d473b014aa4c0840ae5 ✅
SHA-1: b51b71a14c46d8d6a46189d8ec593dbe681b246a
SHA-256: 8e680b2b9f991aac2c23130a2c2ff672be9d177838356487697fd39cd6645f2c
SHA-512: 488a2e19297832323c98cbd48a2932c528bf89c5dd0d2e859b9fb652c606dbe94c9ad7ae2a6f618f2ddba3c0e762a21a60a36d499d50fe6ecce9d34f6875fce9

Digital file signature ebsnvme-id.exe ✅

✅ This file is compatible with 64-bit Windows and ❌ will not work on a 32-bit operating system.

What is ebsnvme-id.exe?

ebsnvme-id.exe is a legitimate, official command-line utility provided by Amazon Web Services (AWS). It is specifically used on Windows-based AWS EC2 instances to identify and map Amazon Elastic Block Store (EBS) volumes attached as NVMe block devices. It helps administrators match Windows disk numbers to their corresponding AWS EBS volume IDs.

Standard File Location

On an AWS Windows EC2 instance, the file is natively located within the Amazon NVMe driver or EC2 tools directories. The standard paths are:

• C:\Program Files\Amazon\AwsDiskNVMe\
• C:\Program Data\Amazon\EC2-Windows\Launch\Module\ (depending on your EC2 launch agent version)

How to Fix ebsnvme-id.exe Errors Without Downloading Anything

Errors related to this file usually happen because the file is corrupted, blocked by system permissions, or its environmental path is broken. Since you cannot download files, you must repair it using native Windows utilities.

1. Run System File Checker (SFC)

If the file was modified or corrupted, the Windows system image cache can restore it.

1. Press Win + X and select Terminal (Admin) or Command Prompt (Admin).
2. Type sfc /scannow and press Enter.
3. Wait for the scan to finish and restart your instance.

2. Re-register the Execution Path via PowerShell

If your scripts cannot find the executable, manually invoke it from its absolute path or add it back to your system environment variables.

1. Open PowerShell as an Administrator.
2. Run this command to verify if the file exists locally:

   Test-Path "C:\Program Files\Amazon\AwsDiskNVMe\ebsnvme-id.exe"

3. If it returns True, run the application directly using its full path inside your scripts instead of just calling ebsnvme-id.exe.

3. Restart the AWS Systems Manager / EC2 Launch Services

Sometimes the error pops up because the background service managing AWS utilities has crashed.

1. Press Win + R, type services.msc, and press Enter.
2. Locate Amazon EC2 Launch or AWS Systems Manager Agent.
3. Right-click the service and select Restart.

---

📊 Diagnostics Tool: Verify Your ebsnvme-id.exe File

Worried that the file on your PC has been modified by malware? Drop it into the form below. Our script will verify its file size, cryptographic hash (MD5/SHA-1), and check for a valid Microsoft digital signature.

Connected files:
KERNEL32.dll

Amazon Web Services, Inc.