Windows Hardware Compatibility Program for Windows 11, version 22H2

Hello
A manufacturer's workstation that appears Certified for Microsoft Windows Hardware Compatibility Program – Client family version 21H2, x64 may mean that it is Microsoft Windows 11 Hardware Compatibility Lis

Hello Everyone,

I hope this message finds you well.

I have recently assumed responsibility for the Windows hardware certification process of a driver developed by our company. I am striving to grasp some finer details pertinent to our unique case, relating to deploying the WHQL infrastructure, conducting driver tests, and submitting our driver

for certification. I would greatly appreciate any assistance or insights you could provide regarding the queries listed below:

We possess a Windows driver functioning as a service driver. Its primary role is to enable our client agent/connector to operate as a service, albeit in kernel mode. This service caters to ioctl requests coupled with a process ID, forwarded to our client agent/connector. Upon receiving this request, the service driver injects the process with our libintcore dll library. Essentially, the inception of this driver aimed to overcome a security limitation in earlier Windows versions that barred our client agent from process injection.

The previous certification of our Windows driver utilized an older certification method. However, I comprehend that the current approach necessitates deploying the WHQL infrastructure (comprising controller, studio, and test Windows clients). Despite having partial understanding of the new process, there are specific aspects I am still uncertain about:

1. Windows Versions Supported: Our software is compatible with all versions of Windows still receiving support from Microsoft, covering Windows Server, Windows 10, and 11. Is it obligatory to test and certify the driver for each individual build of Windows (e.g., Windows 10: 21H1, 21H2, etc.), or is certifying for the latest build of each OS version sufficient?

2. Category of Tests: Given that our Windows driver is of a software driver type, which category of tests should I administer?

3. Automation through CI/CD Pipeline: Has anyone here successfully implemented a CI/CD pipeline to automate the Windows Hardware Certification Process? If so, could you share your experiences or insights on whether or not this is feasible?

I am eager to learn from your experiences and would be thankful for any guidance or suggestions you can offer to assist me in navigating through this process efficiently and effectively.

Thank you for considering my queries. Looking forward to your valuable responses.

Warm Regards,

Bruno

Hi,

We found "Windows Driver Project" checkbox is different in Win11 22H2 build 22621 and build 22000.

 

Target device select a USB smart card reader which installed UMDF2 driver. 

Steps to repro: Go to Project menu  → Click Create project →Windows Driver Project checkbox should stay unticked unless you are testing WDF drivers.

Question 1: Can Windows Driver Project checkbox used for UMDF2 driver? 

Question 2: this option can for IHV to do "Windows driver" engineering and development test. Check INF driver can meet Windows Driver Requirements https://learn.microsoft.com/en-us/windows-hardware/drivers/develop/driver-isolation

Thanks

Kelly

*Edit: I was able to download the Microsoft.Diagnostics.Tracing.EventSource.dll from here: https://nuget.info/packages/Microsoft.Diagnostics.Tracing.EventSource.Redist/1.1.28

I copied it to C:\Program Files (x86)\Windows Kits\10\Hardware Lab Kit\Studio and that seemed to fix the issue

I'm trying to create a DUA for a driver package and the new HLK (10.0.22621.1) fails with this error:

Is this something that was left out of the build or is it something we need to install separately?