HLK for Windows server 2022 issues

%3CLINGO-SUB%20id%3D%22lingo-sub-2594819%22%20slang%3D%22en-US%22%3EHLK%20for%20Windows%20server%202022%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2594819%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%3C%2FP%3E%3CP%3EWe%20are%20runnig%20HLK%20certification%20for%20windows%20server%202022%20with%20our%20storage%20array%2C%20all%20the%20cases%20passed%20except%20two%3A%3C%2FP%3E%3CP%3EDF%20-%20Sleep%20and%20PNP%EF%BC%88disable%20and%20enable%EF%BC%89with%20IO%20Before%20and%20After%20with%20Driver%20Verifier%20Isolation%20rules%20enabled(Reliability)%3CBR%20%2F%3EDF%20-%20Sleep%20and%20PNP%EF%BC%88disable%20and%20enable%EF%BC%89with%20IO%20Before%20and%20After%20with%20Driver%20Verifier%20Isolation%20rules%20enabled(Development%20and%20Integration)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20notice%20they%E2%80%98re%20new%20cases%20in%20HLK%202022%2C%20when%20execute%20this%202%20cases%2C%20the%20test%20client%20will%20goto%20bule%20screen%20and%20the%20Stop%20code%20is%3A%20DRIVER%20VERIFIER%20DETECTED%20VIOLATION%20%2C%20therefore%20the%20case%20will%20failed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20meet%20this%20problem%20too%20and%20have%20some%20ideas%20on%20how%20to%20solve%20this%3F%3CBR%20%2F%3EAny%20suggestion%20will%20be%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDanZhao%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2594819%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2022%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehlk%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2643388%22%20slang%3D%22en-US%22%3ERe%3A%20HLK%20for%20Windows%20server%202022%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2643388%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1115427%22%20target%3D%22_blank%22%3E%40danzhao%3C%2FA%3E%26nbsp%3BSorry%20to%20hear%20you%20are%20having%20trouble.%26nbsp%3B%20The%20Driver%20Isolation%20checks%20are%20indeed%20new%20for%20Server%202022.%26nbsp%3B%20They%20are%20documented%20here%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdevelop%2Fvalidating-windows-drivers%23driver-verifier-driver-isolation-checks%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EValidating%20Universal%20Windows%20drivers%20-%20Windows%20drivers%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E(Scroll%20to%3A%20%22Driver%20Verifier%20Driver%20Isolation%20Checks%22)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20continue%20to%20have%20trouble%2C%20please%20submit%20the%20issue%20to%20use%20through%20MS%20Collaborate%20(under%20your%20company's%20account)%20so%20that%20we%20can%20continue%20this%20discussion%20with%20you%20there.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3CBR%20%2F%3EMichael%20Bernstein%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi All

We are runnig HLK certification for windows server 2022 with our storage array, all the cases passed except two:

DF - Sleep and PNP(disable and enable)with IO Before and After with Driver Verifier Isolation rules enabled(Reliability)
DF - Sleep and PNP(disable and enable)with IO Before and After with Driver Verifier Isolation rules enabled(Development and Integration)

 

We notice they‘re new cases in HLK 2022, when execute this 2 cases, the test client will goto bule screen and the Stop code is: DRIVER VERIFIER DETECTED VIOLATION , therefore the case will failed.

 

Does anyone meet this problem too and have some ideas on how to solve this?
Any suggestion will be appreciated.

 

DanZhao

1 Reply

@danzhao Sorry to hear you are having trouble.  The Driver Isolation checks are indeed new for Server 2022.  They are documented here:
Validating Universal Windows drivers - Windows drivers | Microsoft Docs

 

(Scroll to: "Driver Verifier Driver Isolation Checks")

 

If you continue to have trouble, please submit the issue to use through MS Collaborate (under your company's account) so that we can continue this discussion with you there.

 

Thanks,
Michael Bernstein