How to fix INF verification error “Specified DIRID '10' not allowed” on Windows 11 25H2?

Question

I’m running Windows 11 25H2 and encountered the following error while verifying a driver INF file with InfVerif:

Error 12/2/2025 3:37:20.498 PM Code 1340,

C:\Windows\System32\DriverStore\FileRepository\s0gkt49a.inf_amd64_3559ddf2648f6594\s0gkt49a.inf line 20: Specified DIRID '10' not allowed.

WexTraceInfo ThreadId=15368 ProcessId=17644 TimeStamp=1012942261 LogSessionId=1 SessionTraceCount=87

File: Line: -1

Error Type:

Error Code: 0x0

Error Text: Error 0x00000000

End Test 12/2/2025 3:37:20.489 PM InfVerif::RunInfVerif

Result: Fail

• The INF file fails verification with Code 1340.
• The error points to line 20 in the INF file, where DIRID '10' is specified.
• From Microsoft documentation, certain DIRIDs are restricted depending on context, but I’m not sure why this one is invalid.
• Environment: Windows 11 25H2, driver package located in DriverStore\FileRepository.

Question: What causes the “Specified DIRID '10' not allowed” error during INF verification on Windows 11 25H2, and how can I modify the INF file or driver package to resolve it?

Answer 1

Hi @Joe Liao ,

Thanks for your details!

From my understanding, DIRID 10 in an INF file maps to %SystemRoot% (the Windows folder, usually C:\Windows). Historically, drivers could copy files into system-wide folders like %SystemRoot% or %System32.

However, starting with Windows 10 (1709) and enforced in Windows 11, Microsoft introduced driver package isolation. This rule prevents drivers from placing files in OS directories because it can break servicing, complicate updates, and create security risks. Instead, all driver files must be staged and serviced from the Driver Store (represented by DIRID 13) which is why I think certain DIRIDs might be restricted.

You can check these out for more information if you'd like:

• Using Dirids
• Driver package isolation

---

What causes the “Specified DIRID '10' not allowed” error during INF verification on Windows 11 25H2?

I think the error occurs because your INF file references DIRID 10 in sections like [DestinationDirs], CopyFiles, or ServiceBinary. On Windows 11 25H2, InfVerif enforces isolation rules and flags this as Code 1340.

How can I modify the INF file or driver package to resolve it?

Maybe you could simply try changing any destination from 10 to 13. For example, open your INF file:

[DestinationDirs]
DefaultDestDir = 13
MyDriver.Files = 13

• Update ServiceBinary and CopyFiles paths to %13% instead of %10%.
• Ensure subdirectories in SourceDisksFiles match the Driver Store layout.
• Re-run infverif.exe /path your.inf to confirm if the error is gone.

I highly recommend you read these documents for better clarification:

• INF DestinationDirs section
• Run From Driver Store

---

I hope this helps! If you have any other questions, please feel free to ask. I'll be happy to help!