Helix Asio Driver doesn't work anymore after update to v3.80

[Slish76]

Hi All, this is the first time I have an issue with the Helix update since 2019.

It seems like Asio driver won't work anymore (ex. Ableton ) on Windows 10

 

While Usb connection still works well (ex. HX Edit)

 

I usually solve this problem uninstalling and reinstalling again Line6 audio driver for Helix but this time it doesn't solve the issue.

 

Any idea?

 

[rd2rk]

No problem here. Running LIVE 12.1 and Reaper 7.27.

Maybe try uninstall/reinstall HX Edit? That will get you the latest ASIO version.

[jiml6]

Go to your local C drive/Program Files (x86)/Line6/Tools... and uninstall any Helix drivers in the Driver2 Archive. Run those uninstallers. Reinstall HX Edit. See if this works. The latest Driver2 drivers are core isolation supported. Is your system core isolated? 

[Slish76]

Already done the step of uninstalling drivers in that way, then I installed those I downloaded from Line6 page with the name "Line 6 Driver2_5 Helix v2.00.0.0 Installer"

I don't know what is a "core isolated" system, I must check out... 

I see that it's something which uses virtualization technology, right? At the moment I don't remember if it's enabled or not in the UEFI BIOS. Are you suggesting that if I enable/disable intel virtualization I could solve the problem?

 

[limansky]

I've found that my Helix LT works fine in Reaper 7.27, but doesn't work in yousician anymore. In the list of ASIO drivers yousician shows only HX stomp (which I don't have), and LT cannot be connected.

[Pony-Rider]

I had the same issue, it was because of core isolation drivers. If you update Hx edit i think it install the 2.0 driver wich require core isolation and memory integrity to work. 
As i couldn't activate memory integrity here is what i did. 
Check device manager for Helix audio driver (should probably show a yellow sign ) : right click and uninstall device, check the box for uninstalling associated driver. 
Reboot and install 1.97 driver, the yellow sign should diseapear and sound should be back.

[rd2rk]

OP specified that they are using Windows 10. 

The "Core Isolation" problem is a Windows 11 bugaboo and if you search the forum you'll find many discussions and workarounds.

BUT... it is not what is causing the ASIO problem in Win10, which I did not have on either of my Win10 boxes.

[Slish76]

Unfortunately 1.97 drivers don't work too. And I can't activate isolated core too.

 

( I didn't have the yellow sign on previous device driver and neither on this )

 

At the moment I can anyway record straight to PC thanks to VB Audio Matrix even if I have to use KS driver.

 

Will wait for a system update , maybe it will solve the problem.

Thank you all 

 

[eddievang]

Unfortunately another user who’s reaper daw is not able to load audio device, Asio configuration button does nothing and input output fields are blank(Helix LT or Podgo)

Both were working fine with reaper until large windows update a few weeks back.

 

Both are still able to work with HX edit and pod go edit and the usb cables all work  fine, audio will pass through helix and route to speakers including YouTube etc

gone through everything others have tried on here, managed to bring core isolation up after going through bios and memory integrity switch then showed.

Then I was able to see the line 6 drivers causing the issues, had to remove all files and reboot.

after reboot memory integrity scan stated it would not engage due to corrupted drivers but the scan showed no drivers.

obviously like many others spending far too much time on this and going down too many rabbit holes.

Ive tried the driver for the memory integrity issue but obviously it needs the switch on!

Any Ideas, I wouldn’t have thought it would be the line 6 hardware as both stopped working with reaper after the windows update.

Thanks in advance

E

system HP laptop 8 gig ram over 1T storage and never had any performance issues

 

[datacommando]

On 4/18/2025 at 12:59 PM, eddievang said:

 

Both were working fine with reaper until large windows update a few weeks back.

 

Any Ideas, I wouldn’t have thought it would be the line 6 hardware as both stopped working with reaper after the windows update.

 

 

Hi,

 

Well, it looks to me as if you have discovered the cause of the problem on your own.

 

The general rule of figuring this stuff out is - It was working, now it ain't - what changed?

 

I would suggest this an issue for either the MS Windows, or Reason, forums.

 

Hope this helps/makes sense.