georgie_n

TLDR Long winded post. Re: Uninstalling HX Edit & Stomp Drivers from a New Windows 11 Laptop and Reenabling Memory Integrity. DISCLAIMER, not responsible for anyone messing up their computers. The following is exactly what I did to thoroughly remove Line 6 Edit and Drivers from a brand new Win11 Laptop. Your results may vary. Sharing only because I could not find a solution online or in the forum I am sure many folks here have discovered that in order to install the latest HX Edit and necessary drivers, you have to disable Core Isolation Memory Integrity. And many of us went ahead and disabled it. And I am sure there are few who installed it and then decided to uninstall but could not reenable Memory Integrity after "Uninstalling" Line 6 Edit and the Driver Packages. If you fall in this camp, read on... First of all, love the Line 6 stuff but was a little worried about this potential security issue. I am sure in good time Line 6 will fix but until then I decided to uninstall the Line 6 stuff of my freshly minted Windows 11 Laptop and keep the Edit software on an Older desktop for Firmware updates...but... When I uninstalled the applications, Windows found a remaining sys file preventing me from enabling Memory Integrity. And furthermore left a HxStomp Control item in my Control Panel. The Fix: After using all the L6 uninstallers, Go to your windows/system32 folder and locate the following and delete. L6Driver2HXStompControlPanel. cpl (this removes the Control Panel Item for HX Stomp) l6HXStomp. sys l6HXStomp_AvsFilter. sys (removing these will let you enable the Memory Integrity in Core Isolation) The Cleanup: Using CCleaner App (Free download) Run the Registry Cleaner, Review and Uncheck all the issues found except ones containing "Line 6" in its description. Select Fix Issues. Reenable Memory Integrity :)

Yep, anything with a big change in gain stages, output levels or impedances can cause a pop when switching presets. That instant change with the differences is essentially acting like a DC spike aka switch pop. The Looper last in chain with 2 identical presets can cause this as well with HX Stomp & Hx Stomp XL. I think that may be a 3.5 bug as it only started since I upgraded to last firmware on both my Stomp and XL units. On separate board builds. Now I always ensure my Looper is not last block and/or before the IR block. Hopefully that is addressed in next firmware build

I ran into this situation when switching presets on both HX Stomp & Stomp XL. After a day or testing presets, I learned it only happened with adjacent presets where the looper block was last in chain, after the Dual IR block. After I modified my presets to have my looper block before my IR block, the problem disappeared on both HX Stomp & Hx Stomp XL. Hope this helps