For those of you who are still having problems... (Skip to the bottom paragraph if you like)
I'm a beginner and I'm interested in Line6 products. I don't currently own any but I have started the Helix Native trial on 1.92 (mistaken download even though 1.93 was available). It worked fine. I upgraded to 1.93 and it would crash in Reaper with an "executed illegal instruction" error. I googled it and ended up in this thread. I also installed PodGo Edit a couple of weeks ago and it would crash immediately before showing the interface leaving an application error in the windows event log. I just wanted to see the interface but had no idea the PodGo had to be connected to see that. I have a ThinkPad with a Samsung EVO SSD (boot and OS drive), a 16 GB M.2 (formatted and used as backup, not bootable) and a Samsung 256 GB MicroSD. After reading this thread I took a look at my drive order and the SSD is 0, the M.2 is 1 and the MicroSD is 2 so not the same problem described in this thread. I decided to eject the MicroSD and try Helix Native again. It worked. This got me thinking that maybe PodGo Edit suffered from the same problem. I ran it and it worked as well. (That's when I found out that it just shows a device not connected screen.)
I believe Line6 uses the serial number of your boot drive as the encryption key (this is common) but the software seems to choke on drives that don't have a serial number like a removable MicroSD (They do have one but Windows won't show it to you). You can tell by entering "wmic diskdrive get serialnumber" at a command prompt. You will see all of your drive serial numbers listed below the header "SerialNumber". In my case I have a blank line as the first entry because the MicroSD doesn't have a serial number. When I eject it, I don't have a blank line and see only the serial numbers from the other two drives. It seems like it's probably a NULL pointer crash. The other odd thing is that it may only fail for people that have that drive first in their wmic list even though it's not disk 0. You can probably plug the MicroSD back in after the software is running and authenticated.