Win 11 Core Isolation Incompatible Drivers

Gary NC3Z

Installed SSDR v3.3.32 on a new Win 11 Install and Windows Security started to balk. Getting errors on compatibility for Core Isolation.

Funny that the only other device giving me issues is the $20 chinese RTL-SDR dongle, but I will toss that.

KD0RC

Hi Gary, I would submit a helpdesk ticket for this one.

Gary NC3Z

OK, but was hoping the Community would be of some help.

Erika - KØDD

I've been really busy this last week or I would have mentioned this exact same thing on my new Windows 11 Pro X64 computer. What caused the Blue or green screen of death regularly with page faults on the windows 10 workstations is causing the memory security protection to flake out on the new computer. I found it the same way, noticed the flags on the windows security application. While not a cure by any means selecting the dismiss button will turn off the alert. Suspect it is going to take a lot of driver rewriting to finally fix these issues.

Sincerely,

Erika Ostlund K0DD

Larry _ NY8T

Not sure if you are aware of this or not but you can turn Core Isolation memory Integrity off.

Gary NC3Z

Yes perfectly aware, but why would I want to do this?

Rex K0KP

Having the exact same problem here. Filed a trouble ticket on August 28 but no response from Flex. Emailed a few days later as a reminder and still no response on this issue. Not sure what is going on.

The "lost" trouble ticket was nr 53683 sent August 28, 2022. Not a word back even after reminder email. :-)

Thanks

Rex K0KP

Gary NC3Z

The response I received from Flex this week is:

"There is a known software issue (J8210) with compatibility between the DAX drivers and the Core Isolation / Memory Integrity preventing the DAX Drivers from properly installing, or properly running."

AA0KM

Are we waiting on new software to fix this?

It is broken on windows 11 22H2 Sept 2022 upgrade.

John Mikucki

@AA0KM Almost surely waiting on new software from Flex. Much like the NEC, Windows' 'building code' continues to evolve to improve reliability, security, etc. A bit out of my depth here, but I think of it like better/more-provable bounds checking and enforcement (Windows prevents driver from painting outside its lines). This will likely require at least a recompile, and more likely rewriting some parts depending on what sort of clever-and/or-quick'n'dirty things Flex did when they wrote it. Not to ding Flex, I haven't seen their driver source nor would I be qualified to opine on it. Just tech debt that comes along with sustaining a software system over a longer period of time, and the ongoing tension between paying it down and building new product/features.

AA0KM

10-03-2022 ALMOST THERE with V3.3.33 only driver issue so far.

AA0KM

KD0RC

@AA0KM I would submit a helpdesk ticket. Flex support has probably seen this before and should be able to guide you to a solution.

AA0KM

Once Core Isolation is turned off you can not go back. It protects the drivers into VM.

It will flag if turned off and back on again. I have a clean install. Had fingers crossed but it didnt work.

VE7ATJ_Don

I just got the same message re: Memory Integrity on all the DAX, etc. drivers -- running 2.8.1 so I don't think the problem has been resolved.

John K0TG

I had the same problem loading DAX on a new WIN 11 PC. I contacted Windows Tech and they found a registry change that turns that off. In my case, even though I had Admon rights, it would not let me toggle that.

Look here for my post for the details: SmartSDR installations on Windows 11 — FlexRadio Community

73, John K0TG

Christopher Platt

Is there a fix for this (As at late Jan 2023) or is the current solution to turn Core Isolation off?

Gary NC3Z

The only solution I was given is to turn off the core isolation protection.

David Otto

The micaudiodax.sys driver from SmartSDR 3.3.33 will not load with "memory integrity" toggled on in Windows 11 Security settings. There may be other drivers too. This is a defect in the Flex software, and I've reported the problem directly to Flex. It's supposedly a high priority problem that will be corrected in the next version. We'll see, but I see it as a problem, since I'd like to keep 'memory integrity' toggled on.