STATUS_BAD_FILE_TYPE 0XC0000903 – blocked file format fix
Your system or app blocked the file type. The usual culprit is a security policy or a corrupted file association. Here's how to unblock it.
You're staring at 0XC0000903 and it's annoying as hell.
I get it. You're trying to save or open a file and Windows just slams the door. The error says the file type is blocked. Let's fix it. Skip the rest of the internet's fluff — here's the real fix that works 90% of the time.
The fix: check your file association first
This error almost never happens because of a malware or a corrupted file. It's usually a broken file association or a security setting that's too aggressive.
- Right-click the file causing the error. Choose Open with > Choose another app.
- Pick the correct program from the list. If it's not there, click More apps and scroll down.
- Check the box Always use this app to open .[extension] files.
- Hit OK.
If that doesn't work, we go deeper.
Reset the file association via command line
Open Command Prompt as Administrator. Replace .ext with your actual extension, like .pdf or .docx.
assoc .ext=That clears the current association. Then re-associate it with the right program using ftype or by right-clicking and choosing a default app again. For example, for PDFs:
assoc .pdf=AcroExch.Document.7You might need to look up the correct ProgID for your app. Quick way: create a small .reg file that sets the association, or just reinstall the app.
Why this works
The error 0XC0000903 gets thrown when Windows can't figure out what program owns the file type, or when the security subsystem (like AppLocker or Windows Defender Application Guard) flags the extension as unsafe. Resetting the association fixes the first case. The second case requires a different approach — keep reading.
When the fix above doesn't work – Group Policy or blocking software
If resetting the association does nothing, the problem is a policy. This usually happens in corporate environments, but sometimes on a home PC if you've tweaked security settings.
Check Group Policy (Windows Pro/Enterprise)
- Press
Win + R, typegpedit.msc, hit Enter. - Go to Computer Configuration > Administrative Templates &strong; Windows Components > File Explorer.
- Look for Do not allow storage of files with blocked extensions. Double-click it.
- Set it to Not Configured or Disabled. Click OK.
Reboot. That policy is the #1 reason for this error on domain-joined machines.
AppLocker or Windows Defender Application Control
If you're on Windows 10/11 Enterprise, AppLocker might block file types by publisher rule. Check Event Viewer under Applications and Services Logs > Microsoft > Windows > AppLocker. Look for event ID 8004 or 8005. If you see your file extension there, you need to modify the AppLocker rule, not the file association.
For home users: Windows Security's Controlled folder access can also trigger this. Go to Virus & threat protection > Ransomware protection. Turn off Controlled folder access temporarily to test. If the file opens, add the app to the allowed list instead.
Less common causes and their fixes
| Trigger | Fix |
|---|---|
| File downloaded from the internet – Windows Mark of the Web | Right-click file, go to Properties, check Unblock at the bottom. Click OK. |
| NTFS alternate data stream blocking | Open PowerShell as Admin, run Unblock-File -Path "C:\path\to\file.ext" |
| Corrupted user profile | Create a new local user account. If the error goes away, migrate data from the old profile. |
| Third-party antivirus (besides Defender) | Temporarily disable the AV. If the file opens, add the folder or file extension to the AV's exclusions. |
Prevention – stop it from coming back
Three things will keep this error from haunting you again:
- Keep file associations clean – Don't let random apps hijack your extensions. Use
assocandftypeto monitor them. - Don't download executables or scripts from sketchy sites – Windows marks them as blocked from the web, which can trigger this error even for legitimate files.
- On corporate machines, talk to your IT team – They probably pushed a Group Policy that blocks .exe, .msi, or .vbs files. Ask for an exception for your work files.
That's it. 0XC0000903 is annoying but it's rarely a deep system problem. Reset the association first, check Group Policy second, then look at AppLocker. Anything else is a waste of time.
Was this solution helpful?