none
Windows Driver for x64 and signing

    Question

  • Hello Community,

    I have a windows driver working for Win7 x86.

    I am trying to make it install for Win7 x64 

    Please find the details as :

    http://social.msdn.microsoft.com/Forums/en-US/b4f63a23-055f-4245-97b9-6d5a717d1c3a/windows-driver-for-x64?forum=wdk

    As per the suggestion in the above post, i tried signing it as :

    WARNING: x64 Native compiling isn't supported. Using cross compilers.
    Launching OACR monitor

    C:\WinDDK\7600.16385.1>
    C:\WinDDK\7600.16385.1>
    C:\WinDDK\7600.16385.1>
    C:\WinDDK\7600.16385.1>cd bin

    C:\WinDDK\7600.16385.1\bin>dir
     Volume in drive C has no label.
     Volume Serial Number is 8257-AA39

     Directory of C:\WinDDK\7600.16385.1\bin

    01/10/2014  11:10 AM    <DIR>          .
    01/10/2014  11:10 AM    <DIR>          ..
    01/13/2014  12:17 PM    <DIR>          amd64
    02/08/2010  07:18 PM            15,137 amd64mk.inc
    01/13/2010  10:18 PM                88 BlockDir
    01/13/2010  09:57 PM            54,317 coffbase.txt
    01/13/2010  10:18 PM               419 generic.mac
    02/08/2010  07:18 PM            14,363 i386mk.inc
    01/13/2014  12:25 PM    <DIR>          ia64
    02/08/2010  07:18 PM            14,245 ia64mk.inc
    02/08/2010  07:18 PM               791 makefile.ctrpp
    01/13/2010  10:18 PM             4,031 makefile.def
    02/08/2010  07:18 PM           360,857 makefile.new
    02/08/2010  07:18 PM            19,457 makefile.plt
    01/13/2010  10:23 PM             7,348 oacr_base.ini
    01/13/2010  10:18 PM                 2 projects.inc
    01/10/2014  11:06 AM    <DIR>          selfsign
    01/13/2010  10:18 PM            13,599 setenv.bat
    02/08/2010  06:12 PM               143 setwdf.bat
    02/08/2010  07:18 PM            11,060 verify.src
    01/10/2014  11:06 AM    <DIR>          WppConfig
    01/13/2014  12:30 PM    <DIR>          x86
                  15 File(s)        515,857 bytes
                   7 Dir(s)  20,006,522,880 bytes free

    C:\WinDDK\7600.16385.1\bin>cd amd64

    C:\WinDDK\7600.16385.1\bin\amd64>
    C:\WinDDK\7600.16385.1\bin\amd64>
    C:\WinDDK\7600.16385.1\bin\amd64>
    C:\WinDDK\7600.16385.1\bin\amd64>dir
     Volume in drive C has no label.
     Volume Serial Number is 8257-AA39

     Directory of C:\WinDDK\7600.16385.1\bin\amd64

    01/13/2014  12:17 PM    <DIR>          .
    01/13/2014  12:17 PM    <DIR>          ..
    02/08/2010  08:30 PM            71,168 CertMgr.exe
    01/13/2014  12:33 PM           157,312 CMOSEVAL_ROI1.sys
    02/08/2010  08:30 PM            22,528 MakeCat.exe
    02/08/2010  08:30 PM            54,272 MakeCert.exe
    01/10/2014  11:10 AM    <DIR>          OACR
    02/08/2010  08:30 PM            20,480 pvk2pfx.exe
    02/08/2010  08:30 PM           314,368 SignTool.exe
    01/13/2010  09:54 PM            36,864 stampinf.exe
    01/13/2014  12:17 PM               522 testcert.cer
    02/08/2010  08:56 PM           630,272 wdfkd.dll
    02/08/2010  09:11 PM           193,536 wttlog.dll
    02/08/2010  08:58 PM           127,488 WudfExt.dll
                  11 File(s)      1,628,810 bytes
                   3 Dir(s)  20,006,064,128 bytes free

    C:\WinDDK\7600.16385.1\bin\amd64>
    C:\WinDDK\7600.16385.1\bin\amd64>
    C:\WinDDK\7600.16385.1\bin\amd64>SignTool sign /v /s PrivateCertStore /n contoso
    .com(test) /t http://timestamp.verisign.com/scripts/timstamp.dll CMOSEVAL_ROI1.s
    ys

    The following certificates have been found to be suitable for signing:
        Issued to: Contoso.com(Test)
        Issued by: Contoso.com(Test)
        Expires:   Sun Jan 01 05:29:59 2040
        SHA1 hash: B59A36DACEB68F6EA4B61D5C04AEDD4B453921BF

        Issued to: Contoso.com(Test)
        Issued by: Contoso.com(Test)
        Expires:   Sun Jan 01 05:29:59 2040
        SHA1 hash: 6CDA231549E5DA718796636603D73DFA78916A35

    SignTool Error: Multiple certificates were found that meet all the given
            criteria. Use the /a option to allow SignTool to choose the best
            certificate automatically or use the /sha1 option with the hash of the
            desired certificate.
    The following certificates meet all given criteria:
        Issued to: Contoso.com(Test)
        Issued by: Contoso.com(Test)
        Expires:   Sun Jan 01 05:29:59 2040
        SHA1 hash: B59A36DACEB68F6EA4B61D5C04AEDD4B453921BF

        Issued to: Contoso.com(Test)
        Issued by: Contoso.com(Test)
        Expires:   Sun Jan 01 05:29:59 2040
        SHA1 hash: 6CDA231549E5DA718796636603D73DFA78916A35


    C:\WinDDK\7600.16385.1\bin\amd64>SignTool sign /a /v /s PrivateCertStore /n cont
    oso.com(test) /t http://timestamp.verisign.com/scripts/timstamp.dll CMOSEVAL_ROI
    1.sys

    The following certificates have been found to be suitable for signing:
        Issued to: Contoso.com(Test)
        Issued by: Contoso.com(Test)
        Expires:   Sun Jan 01 05:29:59 2040
        SHA1 hash: B59A36DACEB68F6EA4B61D5C04AEDD4B453921BF

        Issued to: Contoso.com(Test)
        Issued by: Contoso.com(Test)
        Expires:   Sun Jan 01 05:29:59 2040
        SHA1 hash: 6CDA231549E5DA718796636603D73DFA78916A35

    The following certificate was selected:
        Issued to: Contoso.com(Test)
        Issued by: Contoso.com(Test)
        Expires:   Sun Jan 01 05:29:59 2040
        SHA1 hash: B59A36DACEB68F6EA4B61D5C04AEDD4B453921BF

    Done Adding Additional Store
    Successfully signed and timestamped: CMOSEVAL_ROI1.sys

    Number of files successfully Signed: 1
    Number of warnings: 0
    Number of errors: 0

    C:\WinDDK\7600.16385.1\bin\amd64>
    C:\WinDDK\7600.16385.1\bin\amd64>
    C:\WinDDK\7600.16385.1\bin\amd64>
    C:\WinDDK\7600.16385.1\bin\amd64>
    C:\WinDDK\7600.16385.1\bin\amd64>

    But After doing so, i tried to install the driver, but getting the same error.

    And installation fails telling the driver is not supported for x64 based system

    Where is the problem and hot to solve it.

    --- Misbah


    Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com email-misbah.khan@tes-dst.com

    Monday, January 13, 2014 8:35 AM

Answers

All replies

  • As you can see from the log, a "test" certificate was actually used. Test certificates are not good for installation on real user systems. So you need either to get a real certificate, or install your test certificate on target machines (for testing purpose) as described in documentation and enable test-sign in boot config.

    Regards,

     --pa


    • Edited by Pavel A Monday, January 13, 2014 2:40 PM
    Monday, January 13, 2014 2:33 PM
  • What does setupapi.dev.log say?

    d -- This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, January 13, 2014 2:34 PM
    Owner
  • Thanks for your replies, it worked for me.

    I have some questions in continuation as :

     

    If i have to use a commercial license from MS. How shall i get this Certificate ?

    What is the cost of this License and what would be the terms and conditions involved.

    --- Misbah 


    Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com email-misbah.khan@tes-dst.com

    Tuesday, January 14, 2014 7:35 AM
  • what fixed the problem?

    the upload and signing to sysdev is now free. you need to have a company cert whose cost varies depending on the issuer.


    d -- This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, January 14, 2014 8:49 AM
    Owner