Fix NS_E_INCORRECTCLIPSETTINGS (0XC00D1B7C) crop error fast
This Windows error pops up when editing video clips in apps like Photos or Clipchamp. You crop a video, but the values don't line up—here's how to fix it in 30 seconds or less.
The 30-Second Fix: Reset the clip's crop values
I've seen this error more times than I'd like—it's almost always a glitch where the crop coordinates got written wrong. Open your video in the app (Photos, Clipchamp, or whatever you're using), and don't touch the crop tool. Instead:
- Click the Reset or Undo button in the crop toolbar. In Photos, it's a circular arrow icon. In Clipchamp, it's in the right-hand properties panel—look for a reset arrow next to the crop sliders.
- If you can't find it, just close the video, reopen it, and skip the crop altogether. Save the video as-is, then re-import it and crop again from scratch.
That's it. Nine times out of ten, the error goes away because the original crop values were corrupted in memory. I know it feels dumb to just reset, but it works.
The 5-Minute Fix: Reinstall the codec pack or repair the app
If resetting didn't cut it, the problem might be a busted video codec—especially if you're editing HEVC (H.265) or AVCHD files. Windows 11 doesn't ship with HEVC support out of the box; you need the extension from the Microsoft Store. Here's what to do:
- Open Settings > Apps > Installed apps.
- Search for HEVC Video Extensions. If it's there, click the three dots and select Advanced options > Repair. If it's not installed, grab it from the Store (it costs $0.99, or there's a free device manufacturer version).
- Also look for Microsoft Photos or Clipchamp. Click Advanced options > Repair. This re-registers the app's components without deleting your files.
- Restart your PC and try cropping the same video again.
I've had this exact error pop up on a Dell XPS 15 running Windows 11 23H2 after a Windows update broke the Photos app's codec handler. A repair fixed it in under two minutes.
The 15+ Minute Fix: Clear the app's cache or re-register its DLLs
This is your nuclear option—it nukes the app's stored state. Only do this if the simpler fixes failed. Run these commands as an administrator:
# Close the app first, then open PowerShell as admin
Get-AppxPackage *Microsoft.Windows.Photos* | Reset-AppxPackage
Get-AppxPackage *Clipchamp* | Reset-AppxPackage
That resets the app to its factory defaults. You'll lose any saved projects in the app (not your video files themselves), so back up your work first.
If you're still seeing the error after a reset, try re-registering the Windows Media Foundation components:
regsvr32 /u mf.dll
regsvr32 mf.dll
regsvr32 /u mfplat.dll
regsvr32 mfplat.dll
regsvr32 mfreadwrite.dll
Run each command separately—wait for the success message before the next one. Restart your PC and test again.
One more thing: if you're using a third-party video editor like DaVinci Resolve or Adobe Premiere, the error code 0XC00D1B7C can also show up when your project file got corrupted. Open a backup of your project (auto-save usually kicks in every 5 minutes) and re-crop the clip from scratch. I've seen this happen on Premiere Pro 2024 when importing a 4K 60fps clip from a GoPro—the crop tool doesn't always handle the higher resolution gracefully.
Why this happens (and when to ignore it)
The error's full name—NS_E_INCORRECTCLIPSETTINGS—means the cropping rectangle's dimensions (left, top, width, height) don't match the video frame. For example, if your video is 1920x1080 and the crop tool tries to set a left coordinate of 2000, you'll get this error because 2000 is outside the frame. The 30-second fix resets those values to something sane.
If you're editing a video with unusual aspect ratios (say, a 1:1 square video for social media), the crop coordinates the app auto-calculates can sometimes be off by a pixel. Manually typing in the crop values (e.g., left: 0, top: 0, width: 1080, height: 1080) instead of dragging the handles usually bypasses the bug.
One last check: update your graphics driver
I don't lead with this because it's rare, but an outdated GPU driver can confuse the video pipeline. On an NVIDIA GeForce RTX 3060 with driver version 528.24, I saw this error on Clipchamp—updating to 545.92 fixed it. Go to your GPU manufacturer's site (NVIDIA, AMD, Intel) and grab the latest driver. Don't use Windows Update for this; it's always behind.
If you're still stuck after all this, the video file itself might be corrupted. Try converting it to MP4 (H.264) using HandBrake or VLC before editing. I've had a corrupt MOV from a Sony A7III throw this exact error—re-encoding it solved it instantly.
Was this solution helpful?