Windows thinks kernel fsni32.sys is unsigned (after April 15 update)

NikK

I've never seen this before. The event log Microsoft-Windows-CodeIntegrity/Operational reports this at every Windows start since April 15.

 

9 seconds before these warnings started I got this update:

 

When I check the file the signature look ok. I've also checked with Sigverif and Sigcheck and everything seems fine. So why does my OS think it's unsigned, is there perhaps something wrong with the certificate that I'm missing?

SHA-1: c46f56681cd4144f010a19a550e999b290c51e13

SHA-256: 3336cef2d4f624b370b580f8cb0259bdbfd84b650526e28ecfe72743b2404d68