NVIDIA Profile Inspector error messages: what they mean and how to fix them
Paste or type the start of your error message into the box below to see what it means and the fix. The most common ones are "No compatible NVIDIA Driver was detected" (NPI cannot reach an NVIDIA driver), "The type initializer for 'nspector.Common.DrsServiceLocator' threw an exception" (the same problem in NPI 2.x), and "DRS_SaveSettings failed: NVAPI_ERROR" (the driver refused to save, usually after a driver update).
Runs in your browser. Nothing is uploaded. Paths and user names are never stored.
All NPI error messages
Each entry quotes the message as NPI shows it. “Reproduced” means we saw the exact message on our test PCs; every other entry comes from NPI’s source code or from users’ reports on GitHub, and is labelled so. The list of user-facing strings was extracted from the 3.0.2.3 source.
CODE · NPI 2994194
Start-up
LAB · REPRODUCED · F07, F09, F40, F48, F50NPI 3.x
No compatible NVIDIA Driver was detected on your system. Your NVIDIA GPU might be disabled.
NPI could not start NVIDIA's NVAPI library, so it has no driver database to edit. It shows this one message and stops. NPI 3.0.2.3 takes about ten times longer than 3.0.2.1 to show it.
Before April 2026 the text read: No compatible NVIDIA GPU was detected on your system. (upstream git history, not tested by us).
Likely causes
The PC has no NVIDIA GPU, or Windows is using only integrated or AMD graphics.
The NVIDIA driver is not installed, or the GPU is disabled in Device Manager.
On a laptop, the NVIDIA GPU is switched off by the hybrid graphics mode.
A broken or partial driver install.
What to do
Open Device Manager, Display adapters: if the NVIDIA entry shows a down arrow, enable it.
Install or reinstall the current NVIDIA driver from NVIDIA, then restart.
On a laptop, make Windows use the NVIDIA GPU (graphics settings or the MUX switch) and start NPI again.
If you have AMD or Intel graphics, NPI cannot help you.
The type initializer for 'nspector.Common.DrsServiceLocator' threw an exception.
The same problem as the no-driver message, in NPI 2.x: NPI cannot reach a usable NVIDIA driver. 2.x shows the raw .NET exception and a stack trace instead of a clear sentence.
Likely causes
No NVIDIA GPU or driver on the PC (AMD and Intel users report this).
A very old or damaged NVIDIA driver.
The GPU is disabled or not active (laptop hybrid graphics).
What to do
Check that the PC has an NVIDIA GPU and a working driver (see the requirements page).
Update the NVIDIA driver, then restart.
Use NPI 3.x: it explains the problem instead of throwing an exception.
LAB · REPRODUCED · F04, #131, #345, #368NPI 2.4.0.29 and older Windows
.NET Framework error before any window opens
NPI is a .NET Framework program and cannot start without the right runtime. The last 2.x build, 2.4.0.29, needs .NET Framework 4.8.1; 3.x and 2.4.0.4 need 4.8.
Likely causes
Windows 10 or Server without .NET Framework 4.8 or 4.8.1.
Running 2.4.0.29 on a PC that only has 4.8.
What to do
Install .NET Framework 4.8 from Microsoft, then restart.
Some security products flag rarely seen, unsigned programs. We scanned every official release with Microsoft Defender and ClamAV and both found nothing.
Likely causes
A false positive from a heuristic or a small engine.
COMMUNITY · #298, #297, #303, #305, #349, #402NPI 2.x and 3.x
DRS_SaveSettings failed: NVAPI_ERROR
NPI asked the driver to save your changes and the driver refused. NPI names the failed driver call (DRS_SaveSettings) and NVIDIA's generic error code (NVAPI_ERROR). It is the most-reported NPI problem, and it tends to follow driver updates.
Likely causes
A driver update changed how the profile database is written (users report waves of it, for example driver 572.70).
The database files are damaged or locked by another program.
NPI is out of date for the driver.
A value NPI wrote is not accepted by the driver.
What to do
Update NPI to the newest release (stable first, then the pre-release).
Run NPI as administrator and close the NVIDIA App and any overlay tools, then try again.
Export your profiles, then try the change on a single setting to find the one the driver rejects.
If every save fails, reset the profile database as described on the reset page (this removes your changes, so export first).
The last fix resets settings. Export your profiles first.
The driver or Windows refused NPI permission to write the profile database.
Likely causes
NPI was not started as administrator.
The permissions on the NVIDIA Drs folder are wrong, often after a reinstall.
A security tool is blocking the write.
What to do
Run NPI as administrator and accept the UAC prompt.
Check that your account is an administrator.
If it still fails, users report fixing the permissions of C:\ProgramData\NVIDIA Corporation\Drs or recreating the folder, which resets all NVIDIA settings. Export first.
Recreating the folder resets settings. Export your profiles first.
NPI asked the driver for a setting that the current driver does not have. This happens when an old .nip file or an old NPI refers to a setting NVIDIA removed.
Likely causes
The setting was removed from the driver.
The setting only exists in a newer driver than yours.
A .nip file made on another driver.
What to do
Look the setting up in the Settings Explorer and read its minimum driver.
Remove that setting from the file, or import the rest.
NPI imported what it could and lists the profiles that failed, with a hint for each. A common hint says NVIDIA may have renamed the profile, or that another profile owns an application in the file.
Likely causes
An exe in the file is already in another profile.
NVIDIA renamed a predefined profile.
The file contains values the driver rejects.
What to do
Read the hint under each failed profile.
If the profile name changed, edit ProfileName in the .nip file.
Remove conflicting executables from the other profile first, then try Merge again.
Open the file in NIP Studio to see what it contains.
When NPI crashes it writes %LOCALAPPDATA%\nvidiaProfileInspector\Logs\Crash_<date and time>.log with the NPI version, Windows version, driver version, the exception and its stack.
CODE · NPI 2994194 Paste %LOCALAPPDATA%\nvidiaProfileInspector\Logs into the Explorer address bar to open the folder. To report a crash, attach the newest log, your NPI version (from About) and your driver version to a GitHub issue. The decision tree lists what to collect first.
Errors that are not NPI’s
People search for NPI when the message actually comes from other NVIDIA software. “Failed to apply settings” or “access denied” in the NVIDIA Control Panel is the Control Panel’s own error; see the Control Panel page. Settings that revert on their own are usually the NVIDIA App; see NPI vs the NVIDIA App. Problems with the download or an antivirus warning are on the download page, and the version to pick is on the releases page. If a message names the .NET Framework, start with the requirements.
Questions people ask
What does "DRS_SaveSettings failed: NVAPI_ERROR" mean?
NPI asked the NVIDIA driver to save your changes and the driver refused. NVAPI_ERROR is NVIDIA's generic failure code. It is the most reported NPI problem and it often follows a driver update, so update NPI first, run it as administrator and try one setting at a time.
How do I fix the DrsServiceLocator error?
It is NPI 2.x telling you it cannot reach a usable NVIDIA driver. Check that the PC has an NVIDIA GPU and a working driver, update the driver, or move to NPI 3.x, which shows a clear message instead of an exception.
Why does NPI say no compatible NVIDIA driver was detected?
NPI could not start NVIDIA's NVAPI library. The usual causes are no NVIDIA GPU, a missing driver, a disabled GPU or a laptop running on integrated graphics. We reproduced the exact message on test PCs with no NVIDIA GPU.
Where does NPI save crash logs?
In %LOCALAPPDATA%\nvidiaProfileInspector\Logs, as Crash_ files named with the date and time. They hold the NPI version, Windows version, driver version and the exception.