The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
I have been facing a weird issue with HLK HyperVisor Code Integrity Readiness Test. Before running HLK suites I tested against driver verifier and Code integrity did not report me any issue. I am not using any NonPagedPool reference into my driver, too. The point is that when HLK hits HyperVisor Code Integrity Readiness Test at the step "EnableDriverVerifierWaitForShellReady-ProxyClient" it has been failing. Thus with it I have no clue of what can be happen because Logs are only generated when the test actually runs. It seems to be an internal error that only who has automated this stuff could understand. I have updated HLK filters, too. But nothing.
Moreover, I gave a try to DGReadiness Tool. It did not report me any problem with my driver.
The detail is that I have using the evaluation edition image for HLK server (but it is still valid for evaluation).
I would be grateful if someone give me a clue of what could be happen. All other tests seem to be passing and generating their logs normally.
Thanks in advance!
PS: HLK testing process is a pain in the neck! It should be more transparent to the developer, sometimes it looks like a rube goldberg machine, but this is not the case here... The intent seems really good but the way of it is done need to be improved. The HLK Studio interface is a little bit buggy, too...
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Internals & Software Drivers||15 November 2021||Live, Online|
|Writing WDF Drivers||TBD||Live, Online|
|Developing Minifilters||7 February 2022||Live, Online|
|Kernel Debugging||21 March 2022||Live, Online|