DRIVER_ISOLATION_VIOLATION to set Comm name to Registry

NTDEV
1

Hi everyone! I am getting in trouble with HLK testing on New Windows11 24H2 about DRIVER_ISOLATION_VIOLATION. I want to create PortName to Registry 'HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM’ in pnp.c (My program same as Window driver example on Github for W11 22H2) I caught the error that

  • "Registry operations should not use absolute paths. Detected creation of unisolated registry key..."

and

  • "Registry operations should only use key handles returned from WDF or WDM APIs. Detected creation of unisolated registry key...".

Does anyone could tell me the way to solve that problems. Thank you!

2

Did you define your driver as "Windows Universal"? Don't do that. That concept is dead. Just make it "Windows Desktop".

1 Like
3

The HLK now treats both static (INF) and runtime writes to the path HKLM\HARDWARE as an error, so they won't be signed. It is still possible to use the 22h2 HLK for as long as that's accepted for signing submissions

4

I ran on 22H2 then install driver on 23H2 and meet BSOD about error of Registry operations should not use absolute paths. Detected creation of unisolated registry key... "

5

Are there any way need to change because we have to release Universal version only. I see the INF file in example change from DIRID 12 to 13.

6

Hi Sir, I see you in the github repository. Could you told me what can i fix in my code to pass this test on W11 24H2. I see the newest example code of "serial" change from DIRID12 to DIRID 13 in INF file, is there the way to fix? Thank you!

7

It sounds like you've got driver verifier enabled, which has a plugin to detect access locations and causes a bugcheck

1 Like
8

Yeah thats right. You mean if I turn it off, I can run the driver normally right?

9

Yes, you should. I also double checked and we're going to be adding a driver verifier exception for this particular path in an OS update soon.

1 Like
10

Sir, in the future if I write value into this registry I can pass HLK test as normal right?

11

Why? I find that very hard to believe, and suspect you might simply have misunderstood. Windows Universal has virtually no use any more. Serial ports are not part of a Windows Universal system.

2 Likes
12

Ah Yeah, I have misunderstood. I understand now!!!