Line 6 Helix/HX Stomp Driver Conflict Following 2022-08 Cumulative Update for Windows 11

[Muiren]

I've opened a ticket about this but want to hear from any other Windows 11 based DAW users who may have ran into the same issue.

The latest Windows 11 Pro 64-bit OS update a couple of days ago caused a hole in security due to Line 6 driver incompatibility on my hardware DAW, a DELL XPS 8940, 11th Gen Intel i9-11900K processor (8-Core, 16M Cache, 3.5GHz to 5.3GHz), with 64GB RAM, running Windows 11 Pro 64-bit. Its a stripped down system optimized for audio production. The OS Memory Integrity switch cannot be toggled to on due to conflicts with these Line 6 drivers. (see screen caps attached)

• I6Helix_AvsFilter.sys
• I6HXStomp_AvsFilter.sys (for some reason has 2 instances)
• I6PodHd2_AvsFilter.sys

I have related problem on a Surface Book 2 laptop that I previously used as a DAW and uninstalled all Line 6 software on but it did not successful remove all Line 6 drivers, specifically the I6HXStomp_AvsFilter.sys file which I cannot find to manually remove. I have parsed through Microsoft documents for deleting unruly drivers but the system still thinks the driver is installed.

[DunedinDragon]

It appears to me given all the reported problems on this update that you might be better off uninstalling this update.

[rd2rk]

Yet another reason to hold off on W11.

[Muiren]

Thank you for responding. I know I can always roll back the update. This is the first and only problem I have had using Win 11 since its release and it has proven better at memory management and stability under load, particularly running multiple instances of DAW plugins in Reaper, Ableton, and Ardour than Win 10.

[rd2rk]

On 8/31/2022 at 3:18 AM, Muiren said:

Its a stripped down system optimized for audio production.

 

Are these standard optimizations or the sort of DEEP optimizations that involve turning off services and registry tweaks?

If DEEP, then might these optimizations be part of the problem? I'm sure MS doesn't take music production tweaks into account in updates.

[DunedinDragon]

From my reading of Microsoft Tech Notes on W11 performance improvements, the only relevant thing they've done is some work on prioritizing the allocation for computing time to active in-use applications over background processes or "sleeping" apps, so there may be some improvement in DAW performance at higher CPU usage levels than what you might have experienced in W10.  That might also equate to improving runtime on longer running processes such as converting a project to a stereo image.  Other than that I didn't see anything particular about sound devices or audio processing specifics that would relate to DAW work.

https://techcommunity.microsoft.com/t5/microsoft-mechanics-blog/windows-11-the-optimization-and-performance-improvements/ba-p/2733299

 

[Muiren]

Although I've been building experimental media machines since not long after MIDI was introduced in the late 1980s, I more recently found Pete Brown's Unofficial Windows 10 Audio Workstation Guide a pretty useful reference, and transferred what I learned from that to Win 11. So yes, it is Win 11 stripped of all non-essential apps and processes, and while the argument could be made there negligible improvements, the fact is Microsoft maintains and patches 10 while focusing development on improving 11.  
https://devblogs.microsoft.com/windows-music-dev/unofficial-windows-10-audio-workstation-build-and-tweak-guide-part-1/

And Sweetwater has a Windows 11 specific is fairly useful too.
https://www.sweetwater.com/sweetcare/articles/windows-11-pc-optimization-for-recording/

Most of my hacking focus right is returning to work on an unique Integral Guitar Controller technology my father and I were working on before he died, with one prototype Windows IoT and the other ELK Audio Linux, basically a purpose-built tablet DAW that thinks its a guitar.

The real point is that apart from stating how I could obviously roll back the update, none of you has shown an inclination to be particularly helpful, so thanks, moving on.

[rd2rk]

On 8/31/2022 at 5:24 PM, Muiren said:

none of you has shown an inclination to be particularly helpful, so thanks, moving on.

 

WOW! So, we couldn't tell you how to fix your personally customized Windows 11 (a pretty new OS) configuration, so we must be jerks.

Don't let the door hit you in the a$$ on the way out and PLEASE don't come back!

You're WAY too advanced for us poor hillbillies!

[BobArctor]

Got that too after the update. I guess it won't be solved unless Line6 publishes a compatible driver.

[datacommando]

On 9/7/2022 at 5:10 PM, BobArctor said:

Got that too after the update. I guess it won't be solved unless Line6 publishes a compatible driver.

Hi,

 

You probably guess right, but as noted in the comments above you could simply uninstall the update. 
 

It appears Microsoft have various issues with this update.

 

https://docs.microsoft.com/en-us/windows/release-health/status-windows-11-21h2

 

I never ceased to be baffled by folks rushing in to complain about Line 6 for issues that have actually been caused by updates to the Windows and Mac OS.

Hope this helps/makes sense.

[codamedia]

Has anybody noticed that Windows 11 just DISABLES the new feature and provides you with a notice... it's not DISABLING the driver. They know they changed the rules and are giving company's time to catch up. There is nothing to get uptight about.... it's the equivalent of a "bump ahead" sign. 

 

 

[MusicLaw]

On 9/8/2022 at 1:28 PM, codamedia said:

Has anybody noticed that Windows 11 just DISABLES the new feature and provides you with a notice... it's not DISABLING the driver. They know they changed the rules and are giving company's time to catch up. There is nothing to get uptight about.... it's the equivalent of a "bump ahead" sign. 

Yes!

 

This is precisely the result of the August '22 Cumulative update installation!

[MusicLaw]

MS Win 11's August '22 Cumulative Update resulted in the same Windows Security - Action Recommendation notification on my Dell XPS 17 9710 Laptop. The Device Security Notification indicates that the Core Isolation Memory Integrity (CIMI) is currently set to: "OFF".

 

I run Check Point Security's Zone Alarm NextGen on my system. It has always been flawless on all my systems over various OS upgrades for decades. When I contacted them yesterday, they acknowledged and confirmed that their software is not compatible with the latest Window's Cumulative Update and that for the time being, CIMI should be left: "OFF". 

[DasBoeseC]

Hi everyone :)

 

thanks for the exchange...I found it to be very helpful.

 

To sum it up there actually is (let's say) "room for improvement" on Line 6's side regarding their drivers and that just became visible by this Windows 11 update.

Besides that nothing bad happened and this is neither a reason to hold back on Windows 11 - as the "room for improvement" is the same on Windows 10...it's just not visible -  nor to get uptight about Line 6 - as they are already working on the issue and will themselves be interested in solving it.

 

Always remember...every software has bugs...always ;)

 

CU

Sebastian

[dcrowell]

I am having the same problem and I can no longer use HX Edit on my Windows 11 machine. Has anyone found a solution or a workaround yet?

 

[datacommando]

On 10/29/2022 at 11:09 PM, dcrowell said:

I am having the same problem and I can no longer use HX Edit on my Windows 11 machine. Has anyone found a solution or a workaround yet?

 

Hi,
 

If you read through the comments above, it seems that this is an issue brought about by the Microsoft Window 11 Cumulative Update.

It would appear that the general consensus is

 

a). Remove the update, or

b). Turn “Off” the Core Isolation Memory Integrity (CIMI)

 

Hope this helps/makes sense.

 

 

[MusicLaw]

Current workaround/remedy/solution: IGNORE Win11's Device Security Notification!

 

Leave the Core Isolation Memory Integrity (CIMI): "OFF".

 

Be sure that you are running a sufficient Malware Protection Product on your system.

[HonestOpinion]

On 10/29/2022 at 6:09 PM, dcrowell said:

I am having the same problem and I can no longer use HX Edit on my Windows 11 machine. Has anyone found a solution or a workaround yet?

 

 

On 10/30/2022 at 7:02 PM, MusicLaw said:

Current workaround/remedy/solution: IGNORE Win11's Device Security Notification!

 

Leave the Core Isolation Memory Integrity (CIMI): "OFF".

 

Be sure that you are running a sufficient Malware Protection Product on your system.

 

This message probably means you already have CIMI set to On. Set it to OFF as @Musiclaw indicated by typing "Windows Security" into the Windows search box under the Windows icon, select the 'Device Security' icon, go to the settings and turn off 'Memory Integrity'. I feel like a disclaimer is required so, as stated here already, this may introduce some vulnerabilities to Windows so have the proper alternative security measures in place. Whatever those may be? Hopefully Microsoft and/or Line6 will get this resolved at some point.

[PierM]

It's pretty much a useless effort to chase Microsoft with Memory Integrity policies. They keeps changing things from time to time, and drivers that were perfectly compliant within a version, they are flagged as unsafe the next OS update. I wouldn't be surprised to know that L6 has no idea what's the problem is exactly.

 

Just turn it off, as it's basically impossible to have all drivers compatible with that Core Isolation.

 

As soon as you don't browse porn 24/7, and download warez, you are gonna be fine.

[DasBoeseC]

On 11/4/2022 at 8:44 AM, PierM said:

It's pretty much a useless effort to chase Microsoft with Memory Integrity policies. They keeps changing things from time to time, and drivers that were perfectly compliant within a version, they are flagged as unsafe the next OS update. I wouldn't be surprised to know that L6 has no idea what's the problem is exactly.

 

Just turn it off, as it's basically impossible to have all drivers compatible with that Core Isolation.

 

As soon as you don't browse porn 24/7, and download warez, you are gonna be fine.

 

Well, I see where you are coming from, but I would disagree...I know that Microsoft isn't always great and did lots, and lots of weird things in the past, but that does not mean it's always at fault.

Just because a legacy driver was not flagged as incompliant for some time, does not mean it does not become incompliant when the grace period has expired.

Core isolation has been around for quite some time and is a security feature that absolutely makes sense.

If Line 6 decided that a machine running their software cannot have core isolation activated, because the software needs direct access to hardware resources or the performance impact is too big, it's their job to clearly state this so the users are aware (...it will also cause issue with newer machines that have CIMI turned on by default).

At least on my machine the only drivers that are NOT compatible with Core Isolation Memory Integrity are the ones from Line 6...is that different for you?

 

...so, at least from my point of view, the responsibility to solve this issue lies with Line 6.

[PierM]

On 11/11/2022 at 8:01 AM, DasBoeseC said:

At least on my machine the only drivers that are NOT compatible with Core Isolation Memory Integrity are the ones from Line 6...is that different for you?

 

...so, at least from my point of view, the responsibility to solve this issue lies with Line 6.

 

60/70% of my drivers are flagged as non compliant with CI, since latest updates. These drivers are mostly related to pro hardware that, for the nature of the products, can't be updated too often (pro grade automotive simulation). No one in the team could work at all if we had to chase these MS bull***. :)

 

So yeah, CI off all day long, forever and ever.

 

 

[usedbyanr]

On 11/11/2022 at 2:01 AM, DasBoeseC said:

...so, at least from my point of view, the responsibility to solve this issue lies with Line 6.

 

I don't think anybody is disputing that the responsibility lies with Line 6. I think what you have to do is look at it from their perspective. They have software that runs on two different operating systems and their variants. When something changes in the driver model you have significant work to do. It sounds simple but driver development is one of the hardest things to do. There's people out there running Windows 7 - 11. Do you maintain a different driver for each operating system? Do you create the new driver and do all the necessary testing to make sure you don't break it for the majority of people not running Windows 11? At the moment it's an incompatibility with a new operating system feature rather than something that doesn't work at all. It may down the road or it may not. I remember when the driver model changed for Windows 7. Hewlett Packard is a pretty large company and they chose to abandon a significant number of legacy printers. It wasn't just a new feature that had to be turned off. You just had to buy a new printer and laser printers weren't cheap back then. I'm not a Microsoft or Apple champion but from a development perspective Microsoft is far more concerned about compatibility for existing software than Apple. Most things just work in the newest operating system without you having to be concerned.

[Marcal]

I have a Surface Pro 8 that came with Windows 11 so there's no rolling back updates. I am unable to turn OFF the core isolation despite being administrator, so I can't use Helix drivers in my DAW.

[HonestOpinion]

On 11/16/2022 at 10:17 PM, Marcal said:

I have a Surface Pro 8 that came with Windows 11 so there's no rolling back updates. I am unable to turn OFF the core isolation despite being administrator, so I can't use Helix drivers in my DAW.

 

Weird that you are not being allowed to turn off 'Memory Integrity'. I wonder if you are not actually in as admin or if it is some kind of group security policy on your Surface. Try booting Windows into safe mode to turn off 'Memory Integrity'. 

 

Btw, are you going to 'Device Security' --> 'Core Isolation' and then clicking on the 'Core Isolation Details' link to turn off 'Memory Integrity'?

[PierM]

On 11/17/2022 at 4:17 AM, Marcal said:

I have a Surface Pro 8 that came with Windows 11 so there's no rolling back updates. I am unable to turn OFF the core isolation despite being administrator, so I can't use Helix drivers in my DAW.

 

You need to turn off Memory Integrity. Hope microsoft didnt locked this function for their PCs as would really be a dumb move...

 

[DasBoeseC]

On 11/11/2022 at 8:30 AM, PierM said:

 

60/70% of my drivers are flagged as non compliant with CI, since latest updates. These drivers are mostly related to pro hardware that, for the nature of the products, can't be updated too often (pro grade automotive simulation). No one in the team could work at all if we had to chase these MS bull***. :)

 

So yeah, CI off all day long, forever and ever.

 

 

 

I have a feeling that 60/70% of all drivers might be a tad exaggerated (remember there is a TON of drivers required just to make your machine boot up in the first place ;-) ), but again...I see where you are coming from and of course the smaller the manufacturer (or more exotic the hardware) the harder it is to play constant catch-up with changes that are required. (What surprises me is that there are drivers for Windows 11 released for the hardware you use at all...)

 

The only thing that I disagree with is the constant and almost automatic "Microsoft-bashing" that I see so often...not to say they don't deserve it at times, but as I work in IT I often come across people that are used to simply blame Microsoft for anything.

...and as I previously wrote...I am myself pretty relaxed regarding this specific situation as the only thing that happened for most of us is that a "deficiency" of the driver, that always was there, has now been flagged and made visual.

 

The biggest issue might be that Microsoft will probably make CIMI mandatory at some point and it looks like they are starting to force the issue as it seems you cannot simply deactivate CIMI on newer Surfaces anymore.

 

@MarcalLooking at this thread it may help to directly get in touch with Microsoft: Can't disable Core Isolation Memory Integrity - Microsoft Community

[bfunk1978]

I uninstalled all the Line6 software from my PC (I can use HX Edit on my Mac) but Windows 11 still shows l6HXStomp_AvsFilter.sys as an incompatible driver, but I can't find the file on my system. It was showing twice, now it only shows once but all software has been uninstalled. I also searched the registry and see no reference to the file. Since Line6's uninstaller didn't finish it, I blame them. 

 

 

[PierM]

On 11/24/2022 at 5:29 PM, bfunk1978 said:

I uninstalled all the Line6 software from my PC (I can use HX Edit on my Mac) but Windows 11 still shows l6HXStomp_AvsFilter.sys as an incompatible driver, but I can't find the file on my system. It was showing twice, now it only shows once but all software has been uninstalled. I also searched the registry and see no reference to the file. Since Line6's uninstaller didn't finish it, I blame them. 

 

 

 

L6 isn't reading your post, so even if you blame them, nobody will ever know of your issue.

 

If you really want L6 to be officially aware of your problem, open a support ticket and describe the issue. This is the only valid way to be listened and to let them know. ;)

 

 

[PierM]

On 11/18/2022 at 11:12 AM, DasBoeseC said:

 

I have a feeling that 60/70% of all drivers might be a tad exaggerated (remember there is a TON of drivers required just to make your machine boot up in the first place ;-)

 

I was obviously referring to drivers that are being used by the specific hardware I do need to do my job. Not the 70% of ALL drivers, that would be impossible to tell, lol. :)

[Marcal]

This is a private device, I am the Administrator. I haven't tried Safe Mode yet.

[PierM]

On 11/26/2022 at 5:17 AM, Marcal said:

This is a private device, I am the Administrator. I haven't tried Safe Mode yet.

 

Try turning Secure Boot off in the bios. After that, if you manage to turn MI off, then you can turn Secure Boot on again and reboot. At that point you should be able to turn on/off from the UI. At least this is what I've got on a machine and solved that way.

 

At the same time, please, open a support ticket and describe your problem. Even I'm totally fine with MI off (that I'm forced to keep off, despite L6 driver), it's also good that L6 knows about HX users facing annoying problems because of their drivers, and maybe they will take action. (the more people report with a ticket, the more the chance to see a new driver).

[wesselg96]

On 11/17/2022 at 2:41 PM, HonestOpinion said:

 

Weird that you are not being allowed to turn off 'Memory Integrity'. I wonder if you are not actually in as admin or if it is some kind of group security policy on your Surface. Try booting Windows into safe mode to turn off 'Memory Integrity'. 

 

Btw, are you going to 'Device Security' --> 'Core Isolation' and then clicking on the 'Core Isolation Details' link to turn off 'Memory Integrity'?

 

On 11/25/2022 at 11:17 PM, Marcal said:

This is a private device, I am the Administrator. I haven't tried Safe Mode yet.

 

I am having this same exact issue with my device and can confirm you cannot turn off memory integrity. My surface is also a personal device. 

[HonestOpinion]

On 12/13/2022 at 10:35 PM, wesselg96 said:

 

 

I am having this same exact issue with my device and can confirm you cannot turn off memory integrity. My surface is also a personal device. 

 

Wondering if users encountering the greyed out 'Memory Integrity' option are having success either with turning it off via safe boot, or more likely via the bios 'Secure Boot' option that @PierMpointed to? Are neither of these procedures working?

 

I agree with PierM, the more Line 6 tickets on this, the better.  Disagreeable as the 'Memory Integrity' issue may be and as much of a burden as it may place on driver developers, I still hate having to turn security features off. It occurs to me that there should be a better way. Some method for an OS to implement a flexible, updateable, but still persistent enough piece of "middleware" or middle layer, it could be software or something like an updateable firmware ROM, for the drivers to talk to, such that device manufacturers don't have to modify their drivers quite so often when the OS changes.

 

Pretty sure this persistent layer is somewhat in place, and methods of improving it have been thought about at length by developers. It just has never been fully realized (yet, never(?)). Just seems crazy for every company with an impacted driver to have to rewrite code rather than one company (the OS provider). Not to speak of the devices that actually become unusable once their manufacturers stop keeping up with OS changes. It is one thing for a device not to be able to take advantage of the latest improvements in an OS or newer computer hardware, it is quite another for it not to be backward compatible and unusable. This challenge involving driver "churn" has been around for decades and we take it for granted, but perhaps there could be a better approach that would extend devices' usable lifespans as well as reducing the driver update scramble drill. 

[sh4rkbyt31]

Added a ticket for this as well. Let's hope they're accumulating enough to get noticed ;). 

[adamaxe]

This is still an issue. I have created a ticket as well.

[mziach]

Do not disable this function, it helps to better protect the system from viruses that could reach the kernel such as ransomware that has already taken privileges on your system. I asked the Microsoft cell that manages this point, and for them it's Line 6 to correct the drivers so that it is compatible with this new Windows function to strengthen the system.

[PierM]

On 3/5/2023 at 10:11 AM, mziach said:

Do not disable this function, it helps to better protect the system from viruses that could reach the kernel such as ransomware that has already taken privileges on your system. I asked the Microsoft cell that manages this point, and for them it's Line 6 to correct the drivers so that it is compatible with this new Windows function to strengthen the system.

 

It's almost 3 years Win 11 is out, and L6 drivers (all of them) are still not compliant with Core Isolation. It's impossible to not turn off that function for W11 users (if they need to use these devices with USB), and telling them is L6 fault isnt helping much. ;)

 

In real life, if you dont download warez hacks and cracks, watch porns 24/7 and open random links on random emails, there'll be no realistic ransomware risk.

[Glenito]

Hey guys,

 

I have a Line6 Pod HD500X and Edirol (Roland) interface and both of these drivers are showing as incompatible with the W11 Memory Integrity security feature.

 

Which to me, as they're both ASIO, is completely normal and expected behaviour.

 

My thinking is, ASIO drivers directly control hardware without having the Windows OS layer (or any virtualisation etc.) in between, so Core Isolation/Memory Integrity will never be able to be switched on.

 

I would assume this would be the same with WASAPI drivers, but I have no experience of them so would be interested in what others have experienced.

 

Can anyone feed into this, as in:

 

1) Do you have ASIO drivers for other audio interfaces that work fine with this W11 security feature?

2) Do you have WASAPI drivers for this or other audio interfaces that work fine with this W11 security feature?

 

Thanks :-)

[PierM]

On 3/31/2023 at 4:19 PM, Glenito said:

My thinking is, ASIO drivers directly control hardware without having the Windows OS layer (or any virtualisation etc.) in between, so Core Isolation/Memory Integrity will never be able to be switched on.

 

I would assume this would be the same with WASAPI drivers, but I have no experience of them so would be interested in what others have experienced.

 

Can anyone feed into this, as in:

 

1) Do you have ASIO drivers for other audio interfaces that work fine with this W11 security feature?

2) Do you have WASAPI drivers for this or other audio interfaces that work fine with this W11 security feature?

 

Thanks :-)

 

Focusrite ASIO are compliant. Motu ASIO are compliant. Ampero Asio are compliant... :)

 

None of the L6 drivers are compliant, not just ASIO. ;) 

[DasBoeseC]

Hi everyone,

 

the support ticket I opened regarding this issue was closed with the following reply by Line 6:
 

Quote

Hi,
please check our FAQ over core protection:

https://line6.com/support/page/kb/effects-controllers/helix/memory-integritycore-isolation-disabling-for-helixhx-and-pod-hd-drivers-on-windows-10-and-11-r1041/

Best regards
Technical Support
Line 6 /Ampeg Support Europe

 

Which to me does not sound as if Line 6 are actively working on a solution...they are instead "monitoring the issue".

I think I'll try to get rid of any Line 6 stuff on my machine then...