Is there a way to get JetCreateDatabaseA() to work on a Server 2025/Win11 development system?

Question

Maintaining a product that uses ESE (Extensible Storage Engine) to create databases. Calling JetCreateDatabaseA() hangs on Windows 11 and Server 2025 if the binary isn't signed and timestamped.

If the binary is unsigned or signed with valid certificate but not timestamped/countersigned, there doesn't seem to be an error but the call never returns. If the binary is fully signed and timestamped, everything works normally. I've tried turning off every bit of security I can find to work around this, but nothing seems to work.

Is there an option that doesn't require full code signing?

Thanks

Answer 1

Hello,

Thank you for posting in Microsoft Q&A.

Based on the description, I understand your question is related to get JetCreateDatabaseA() to work on a Server 2025/Win11 development system.

As you can see if the binary is fully signed and timestamped, everything works normally. This is because Windows 11 and Server 2025 have stricter security policies that require binaries to be signed and timestamped to ensure their integrity and authenticity.

Check that your policies allow unsigned binaries if that's an option for your environment. Check for any group policies that might enforce code signing requirements.

If you are in a development environment, you might consider using a test signing certificate. This allows you to sign your binaries without needing a full code signing certificate. However, this is not recommended for production environments.

https://learn.microsoft.com/en-us/windows/win32/extensible-storage-engine/jetcreatedatabase-function

Have a nice day.

Best Regards,

Molly

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it