Fix ERROR_INVALID_COLORSPACE (0X000007E1) in Windows

When You'll See This Error

You're editing a photo in Photoshop or GIMP, or maybe you just opened a video file in a media player like VLC or Windows Media Player. The app either crashes outright or throws a dialog with ERROR_INVALID_COLORSPACE and the code 0x000007E1. This happens most often with files that have embedded color profiles — like an Adobe RGB or ProPhoto RGB image that you're trying to display on a monitor set to sRGB.

What's Actually Happening

Windows has a color management system (CMS) that translates color spaces between devices. When you see error 0x000007E1, the system is telling you: “I can't find or use the color space definition you're asking for.” The root cause is almost always a corrupted or missing color profile in the Windows Color System — either the profile file itself got damaged, the registry entry for it is broken, or the application you're using is trying to reference a profile that doesn't exist on your system.

The Fix — Step by Step

Skip the usual nonsense like restarting your PC or running SFC. The real fix is resetting the color management to defaults. Here's how.

Open Color Management
Press Win + R, type colorcpl, and hit Enter. That launches the Color Management applet — the native interface for dealing with color profiles.
Reset to System Default
Go to the Advanced tab. Click Reset to defaults. This clears any custom profile assignments per device and forces Windows back to the basic sRGB profile that's built into the OS. It's the nuclear option, but it works.
Clear the Color Cache
Still in Color Management, go to the All Profiles tab. Click Remove on every profile that looks suspicious — especially third-party ones from monitor manufacturers or printer software. Windows will rebuild the cache on next boot.
Delete Corrupted Profile Files
Open File Explorer and navigate to C:\Windows\System32\spool\drivers\color. If you see any profile files with weird names or zero byte size, delete them. Don't touch the .icc or .icm files that came with Windows — those are safe. I'm talking about files like Monitor_Custom_Profile_v3.icc that you or some app installed.
Re-register the Color System DLLs
Open an admin Command Prompt (right-click Start, select Windows Terminal (Admin)). Run these two commands:
```
regsvr32 /u c:\windows\system32\colorui.dll
regsvr32 c:\windows\system32\colorui.dll
```
The first unregisters the DLL, the second re-registers it. This fixes any broken COM entries that the Color Management app depends on.
Restart the Windows Color System Service
In the same admin terminal, run:
```
net stop ColorService
net start ColorService
```
This forces the service to reload all profile data from scratch.

If It Still Fails

If the error keeps showing up after all that, the problem isn't Windows — it's the file itself. Open the image or video in a tool that lets you strip metadata. I use ExifTool for this. Run:

exiftool -ICC_Profile= -overwrite_original yourfile.jpg

This removes the embedded color profile. The file will fall back to sRGB rendering, which every modern display handles fine. If you need the color profile preserved for professional work, you've got a bad profile — download a fresh copy from the ICC profile registry at color.org and embed it cleanly.

One more thing: check your GPU drivers. I've seen this error on machines where the NVIDIA or AMD driver installed a custom color profile that conflicts with the system one. Update or clean reinstall the driver using DDU in Safe Mode. That's the last resort, but it works when nothing else does.