Certification errors

NXCheck, DBCheck, SafeSEHCheck, AppContainerCheck or WXCheck Test failed

The Windows App Certification Kit reports these under the Windows security features test, which runs the BinScope Binary Analyzer on your binaries. Microsoft lists it for UWP apps.

What it means

Each check looks for a compiler or linker setting that makes a binary harder to attack. The message names the check that failed.

MessageWhat it checksFix
NXCheck Test failedData Execution PreventionLink with /NXCOMPAT.
DBCheck Test failedAddress Space Layout Randomization, for C and C++ binariesLink with /DYNAMICBASE, in your app and every module it uses.
SafeSEHCheck Test failedSafe exception handlers, 32-bit onlyLink with /SAFESEH. It’s on by default in Visual Studio Release builds.
AppContainerCheck Test failedThe appcontainer bit on every .exe and unmanaged DLLBuild with the latest compiler and linker and the /appcontainer linker flag.
WXCheck Test failedNo pages that are both writable and executableTurn off Edit and Continue (/ZI) and keep SectionAlignment at least the page size.
ExecutableImportsCheck Test failedThe import table isn’t in a code sectionDon’t merge .rdata into .text with the /merge linker flag.
SharedSectionsCheck Test failed.No shared writable sectionsRemove shared sections and use CreateFileMapping or MapViewOfFile with proper security.
APTCACheck Test failedAllowPartiallyTrustedCallersAttribute on .NET assembliesDon’t use APTCA on strong-named assemblies unless you need it.

How to fix it

  1. Find the binary named in the kit's report and the check it failed in the table above.
  2. Change the linker setting in that binary's project, or in the build of the third-party library it came from, and rebuild it.
  3. Rebuild the package and run the kit again.

Sending the fixed update with StoreFast

StoreFast can send your next update to Partner Center from a dashboard, CI or a coding agent.

Sources

Facts about Microsoft's tools were checked against these pages on October 16, 2026.