none
WHCK 2.1 against drivers-under-test on Windows 10 test clients? RRS feed

  • General discussion

  • Community,

    Is anyone using WHCK 2.1 against drivers on Windows 10 Tech Preview?  What mileage are you getting?

    I'm seeing problems seemingly around some of the tests calling/setting (Driver) Verifier from the command line, I was wondering if anyone else is seeing similar, interested if anyone else is specifically not seeing similar.

    For instance, when I delve into (what I think are) the relevant log files, I see:

    "The Execute Task with Commandline

    cmd /c
    cscript.exe "ConfigureDriverVerifier.js" 0x209BB mydrivername.sys wdf01000.sys


    Failed with ExitCode 1"

    and elsewhere, for another test, I see:

    "The Execute Task with Commandline

    cmd /c
    IF /I "mydrivername.sys" NEQ "" (verifier /standard /driver mydrivername.sys >
    EnableDV.txt)


    Failed with ExitCode 2"

    [btw, if I try that command on a Admin-CMD line on the DUT, I get what seems like valid output, and indeed an %errorlevel% of 2:

    C:\WINDOWS\system32>verifier /standard /driver mydrivername.sys

    Verifier Flags: 0x000209bb

      Standard Flags:

        [X] 0x00000001 Special pool.
        [X] 0x00000002 Force IRQL checking.
        [X] 0x00000008 Pool tracking.
        [X] 0x00000010 I/O verification.
        [X] 0x00000020 Deadlock detection.
        [X] 0x00000080 DMA checking.
        [X] 0x00000100 Security checks.
        [X] 0x00000800 Miscellaneous checks.
        [X] 0x00020000 DDI compliance checking.

      Additional Flags:

        [ ] 0x00000004 Randomized low resources simulation.
        [ ] 0x00000200 Force pending I/O requests.
        [ ] 0x00000400 IRP logging.
        [ ] 0x00002000 Invariant MDL checking for stack.
        [ ] 0x00004000 Invariant MDL checking for driver.
        [ ] 0x00008000 Power framework delay fuzzing.
        [ ] 0x00010000 Port/miniport interface checking.
        [ ] 0x00040000 Systematic low resources simulation.
        [ ] 0x00080000 DDI compliance checking (additional).
        [ ] 0x00200000 NDIS/WIFI verification.
        [ ] 0x00800000 Kernel synchronization delay fuzzing.
        [ ] 0x01000000 VM switch verification.
        [ ] 0x02000000 Code integrity checks.

        [X] Indicates flag is enabled.

      Boot Mode:

        Persistent

      Rules:

        All rules are using default settings

      Extensions:

        wdm: rules.default

      Verified Drivers:

        mydrivername.sys

    The system reboot is required for the changes to take effect.

    C:\WINDOWS\system32>echo %errorlevel%
    2

    C:\WINDOWS\system32>

    ]

    Quite possibly/probably a user-error, increasingly likely if no one else is seeing such an issue...

    Thanks,

    Tuesday, February 10, 2015 11:21 PM

All replies

  • What you are seeing is expected behavior at this time, as the Windows HCK 2.1 is not designed to test Windows 10.  Please wait for the Windows 10 appropriate Kit to be released for testing Windows 10.

    Tuesday, February 10, 2015 11:56 PM