title: Windows 10: Error code 52 in device manager with correct signature in cross-signed driver
body: <p>we developed a driver and signed the cat and sys file with our company's Verisign signature (SHA1 + SHA256, including certificate chain). We tested it under Windows 7 and 10 both 32 and 64 bit versions. Now we have some random customers that report that our device is not recognized correctly in device manager and that error 52 shows up:</p>
  
  <blockquote>
    <p>Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)</p>
  </blockquote>
  
  <p>Setupapi.dev.log shows this error:</p>
  
  <blockquote>
    <p>_!!! dvi:                     Device not started: Device has problem: 0x34 (CM_PROB_UNSIGNED_DRIVER), problem status: 0xc0000428</p>
  </blockquote>
  
  <p>But this message in Setupapi.dev.log is also present at working installations.</p>
  
  <p>Sign tool shows that the signature is valid, same does the properties page on windows explorer.</p>
  
  <p>What is the reason for this behavior?</p>