Client not working - error 1359 in logs

Hello! 

I have a Windows 10 device that was showing up in the "unidentified devices" list in the NextDNS portal despite having the client installed with report hostname enabled and being pointed to the correct configuration ID.  I found this in the logs - 

2024/02/03 12:40:43 ERROR engine start err: code 1359: Cannot start driver: GetOverlappedResult failed with error 1359
2024/02/03 12:40:43 ERROR Engine DNS error message: 348:Error at NfeEvtIoDeviceControl, code = 3221227288, param = 1179652

I performed a bunch of testing and found that disabling MalwareBytes Premium web filter instantly resulted in the traffic being labeled correctly. I saw in another thread that the client now uses a kernel driver rather than a tap adapter. Is there a way to get both of these tools to play nice with one another, or is that an impossibility due to them both trying to control a kernel driver? 

Thank you, 

Jon