Signing DLLs to clear a Windows 10 S audit

Alfonso Crawford 136 Reputation points
2021-01-14T17:51:52.77+00:00

While testing my UWP app for Windows 10 S with the audit mode policy, the only failure/error I'm getting is that some of the DLLs did not meet the Custom 1 signing level requirements or violated code integrity policy (Policy ID:{a244370e-44c9-4c06-b551-f6016e563076}). Every operation of the app works with nothin showing up within the audit, so I assume the program is otherwise fine.

I'm still new to development within a Microsoft environment, so I'm betting this is something super simple. Are the necessary signatures provided by Microsoft once the app is on the store? Am I supposed to sign the DLLs myself before submitting the app?

None of my attempts to articulate this problem within a search engine are coming back with workable results, which I presume is another symptom of my lack of familiarity: I don't even know specifically what I'm looking for. Thank you for your time and consideration.

Universal Windows Platform (UWP)
0 comments No comments
{count} votes

Accepted answer
  1. Roy Li - MSFT 32,466 Reputation points Microsoft Vendor
    2021-01-15T09:34:46.793+00:00

    Hello,

    Welcome to Microsoft Q&A!

    Based on this document: Test your Windows app for Windows 10 in S mode, the Audit mode policy requires Store certificate. Have you associated your app to the store before you package your app? If not, please associate your app with the store and then install the app to test.

    Thank you.


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


1 additional answer

Sort by: Most helpful
  1. EncLock 1 Reputation point
    2021-08-04T12:53:50.567+00:00

    @Alfonso Crawford or anyone who can help: I am having the same issue. When my app (EncLock) is accessing the DLLs it depends on I get the same error you did EncLock.exe attempted to load somedll.dll that did not meet the Custom 1 signing level requirements or violated code integrity policy (Policy ID:{a244370e-44c9-4c06-b551-f6016e563076}). I have the app associated with the Microsoft app store and I do have the StoreKey.pfx which I used to Digitally Sign all the DLLs involved and the EXE. However, when I install the app on my local machine and run it while running the Win 10 S test Audit mode policy I am still getting the ...did not meet the Custom 1 signing level requirements... events in the Event Logger.

    Can you provide some detailed instructions on how you got it to go away?

    Thanks!

    0 comments No comments