weitzhandler 1 Posted October 9, 2020 Hi, I've installed the "Line 6 Driver2 PodGo v1.95 Installer" driver, following the instructions (device disconnected at installation). When I connect my device, I can see "Line 6 POD Go" in Device Manager (under Sound, video and game controllers), with an exclamation mark on top of it. When I open the device Properties, the Device Status reports the following: Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39) {Bad Image} %hs is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0x The device does not appear in either the playback nor recording devices in the sound mixer. Note: The device does play well with POD Go Edit. Please advise. Best regards, Shimmy Quote Share this post Link to post Share on other sites
cristt 23 Posted October 9, 2020 There's an exact same problem on another recent post in this forum, have a look at that thread. I guess there's no ready solution yet. Quote Share this post Link to post Share on other sites
weitzhandler 1 Posted October 10, 2020 You probably mean this one. Thought it was worth dedicating a new thread to this issue. Quote Share this post Link to post Share on other sites
punkymonkey666 0 Posted November 24, 2020 I also have this issue, on my ancient desktop PC, which is currently running Windows 10, 32 bit. In device manager I can install under Line 6/Pod Go Device but will not install under "Sound, Video and Game controllers" If I try to install from drivers already on PC, I get a Code 10 error - " this device could not be started" or something. Will run Pod Go Edit, although the connectin drops out regularly It installs and works fine, using the same USB cable with my 64 bit Win 10 Notebook but this is not really powerful enough to run Ableton, so I am kind of stuck. Do I need to be running Win 10 64 bit? Quote Share this post Link to post Share on other sites
weitzhandler 1 Posted November 24, 2020 @punkymonkey666 I'm facing the issue on Win10 64bit, so I don't think it's going to resolve anything. I tried completely deleting the driver and this didn't help either. Quote Share this post Link to post Share on other sites
saxatron 4 Posted December 4, 2020 This is happening to me on my new computer. Works fine on all my other computers. Windows10 64bit. I even factory reset my computer, issue still persists. 1 Quote Share this post Link to post Share on other sites
spaceatl 1,975 Posted December 5, 2020 It happened to me when my Windows 10 updated last week...I installed the current driver patch and it came back fine. Make sure you unplug the GO USB from the computer while installing. To be specific, the driver was working with Windows audio, but the ASIO would not initialize in the reaper and was missing. Quote Share this post Link to post Share on other sites
weitzhandler 1 Posted December 5, 2020 15 hours ago, spaceatl said: To be specific, the driver was working with Windows audio, but the ASIO would not initialize in the reaper and was missing. You were then facing a different issue. I've also tried those instructions and reinstalled the latest driver, which didn't seem to help. The yellow exclamation still appears on the driver (see my first post). Quote Share this post Link to post Share on other sites
saxatron 4 Posted December 6, 2020 I've been trying to debug this myself since this is the only thread I can find with this issue. It seems to be either a newer Windows update driver issue or a corrupted registry value, but I am not sure how to fix it. I found details on the error. I have a ticket submitted, hopefully can get more info, I'll share back if I hear anything. Quote Share this post Link to post Share on other sites
saxatron 4 Posted December 6, 2020 @weitzhandler, what kind of computer are you running on? Does it happen to be a Surface Book? Quote Share this post Link to post Share on other sites
weitzhandler 1 Posted December 6, 2020 Looks like our issues are slightly different. I'm on a regular desktop computer. This is what I'm getting: And this one: Quote Share this post Link to post Share on other sites
saxatron 4 Posted December 9, 2020 They are at least sort of similar. Support got back with a cop-out answer that they don't support tablet PCs (I don't see that stated anywhere). Also my Scarlett works flawless, so I don't really think it's a good answer. Maybe you can try to submit a ticket? Maybe you will get further since you are on Desktop. I'm going to try to submit a ticket to Microsoft, my last resort. Quote Share this post Link to post Share on other sites
weitzhandler 1 Posted December 9, 2020 Me too, opened a ticket at Line 6, the response was I should try using a different computer, haven't heard from them yet since my latest reply. Def not a good solution tho, The AvsFilter file exists in the system. Quote Share this post Link to post Share on other sites
saxatron 4 Posted December 9, 2020 I just installed it on my wife's Surface Book and it works flawless. If you `winver` what version do you get? My wife and I are currently on different Win 10s vers (I am on 1909 and she is on 2004), so looking to see if that helps. Quote Share this post Link to post Share on other sites
weitzhandler 1 Posted December 9, 2020 My version is 20H2, but the issue occurred before the update as well. Quote Share this post Link to post Share on other sites
saxatron 4 Posted December 9, 2020 I just upgrade to 20H2, did not help :(. Here is what a good install looks like, (way different) Quote Share this post Link to post Share on other sites
saxatron 4 Posted December 9, 2020 I made a little bit of progress, still getting errors but they are different now, so maybe will help you @weitzhandler. Turns out the driver installer installs both L6 USB and the Pod Go drivers, but the uninstaller only uninstalls the Pod Go drivers. The L6 USB drivers, no matter how many times i installed, were always on the march version instead of june. Windows + I -> Add or remove programs -> Uninstall from here both the Line 6 Pod Go and the Line 6 WinUsb driver. Now I am getting migration issues instead of the previous error, which I am researching now. 1 Quote Share this post Link to post Share on other sites
saxatron 4 Posted December 9, 2020 Sorry for spamming the thread, but want to make sure I keep it up to date with my progress on this. The uninstaller doesn't work properly, its leaving residual files, here is the file list flq: {FILE_QUEUE_COMMIT} 00:14:18.011 flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\l6PodGo.sys' to 'C:\WINDOWS\System32\drivers\l6PodGo.sys'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\l6PodGo_AvsFilter.sys' to 'C:\WINDOWS\System32\drivers\l6PodGo_AvsFilter.sys'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6PodGoAsio_OnInterposer_x64.dll' to 'C:\WINDOWS\System32\L6PodGoAsio_OnInterposer_x64.dll'. cpy: Existing file 'C:\WINDOWS\System32\L6PodGoAsio_OnInterposer_x64.dll' remains unchanged. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6PodGoAsio_OnInterposer.dll' to 'C:\WINDOWS\SysWOW64\L6PodGoAsio_OnInterposer.dll'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\InterposerPodGoBackend64.dll' to 'C:\WINDOWS\System32\InterposerPodGoBackend64.dll'. cpy: Existing file 'C:\WINDOWS\System32\InterposerPodGoBackend64.dll' remains unchanged. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6ConfigPodGo.xml' to 'C:\WINDOWS\System32\L6ConfigPodGo.xml'. cpy: Existing file 'C:\WINDOWS\System32\L6ConfigPodGo.xml' remains unchanged. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\InterposerPodGoBackend.dll' to 'C:\WINDOWS\SysWOW64\InterposerPodGoBackend.dll'. cpy: Existing file 'C:\WINDOWS\SysWOW64\InterposerPodGoBackend.dll' remains unchanged. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6ConfigPodGo.xml' to 'C:\WINDOWS\SysWOW64\L6ConfigPodGo.xml'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6Driver2PodGoControlPanel.cpl' to 'C:\WINDOWS\System32\L6Driver2PodGoControlPanel.cpl'. cpy: Existing file 'C:\WINDOWS\System32\L6Driver2PodGoControlPanel.cpl' remains unchanged. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\WdfCoInstaller01009.dll' to 'C:\WINDOWS\System32\WdfCoInstaller01009.dll'. idb: Last driver package 'l6winusb.inf_amd64_680039b30d9a1455' to copy 'C:\WINDOWS\System32\WdfCoInstaller01009.dll' needs reconfiguration. flq: Hardlinking 'C:\WINDOWS\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_fee724aa691ec5b0\drmk.sys' to 'C:\WINDOWS\System32\drivers\drmk.sys'. cpy: Existing file 'C:\WINDOWS\System32\drivers\drmk.sys' remains unchanged. flq: Hardlinking 'C:\WINDOWS\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_fee724aa691ec5b0\portcls.sys' to 'C:\WINDOWS\System32\drivers\portcls.sys'. cpy: Existing file 'C:\WINDOWS\System32\drivers\portcls.sys' remains unchanged. flq: {FILE_QUEUE_COMMIT - exit(0x00000000)} 00:14:18.256 This is after a clean install, so there shouldn't be any "existing file" flags here. I was able to go through and clean these up by hand. I haven't tried to see if this fixes it yet, I have a feeling no because here is the other issue. dvi: {Configure Device - USB\VID_0E41&PID_4247&MI_01\8&17ba1cfe&1&0001} 00:14:17.768 dvi: Device Status: 0x01802400 [0x12 - 0xc0000493] dvi: Config Flags: 0x00000020 dvi: Parent Device: USB\VID_0E41&PID_4247\___3198677 sto: {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\l6podgo.inf} sto: Source Filter = USB\VID_0E41&PID_4247&MI_01 inf: Class GUID = {4d36e96c-e325-11ce-bfc1-08002be10318} inf: Class Options = Configurable inf: {Configure Driver: Line 6 POD Go} inf: Section Name = l6PodGo.NTamd64 inf: {Add Service: l6PodGo} inf: Start Type = 3 inf: Service Type = 1 inf: Error Control = 1 inf: Image Path = \SystemRoot\System32\Drivers\l6PodGo.sys inf: Display Name = Service Line 6 POD Go inf: Group = Base inf: Updated service 'l6PodGo'. inf: {Add Service: exit(0x00000000)} inf: {Add Service: l6podgo_AvsFilter} inf: Start Type = 3 inf: Service Type = 1 inf: Error Control = 1 inf: Image Path = \SystemRoot\System32\drivers\l6PodGo_AvsFilter.sys inf: Display Name = Line 6 POD Go AVStream Mini Driver inf: Group = PNP Filter inf: Updated service 'l6podgo_AvsFilter'. inf: {Add Service: exit(0x00000000)} inf: Hardware Id = USB\VID_0e41&PID_4247&MI_01 inf: {Configure Driver Configuration: l6PodGo.NTamd64} inf: Service Name = l6PodGo inf: Upper Filters = l6podgo_AvsFilter inf: Included INFs = ks.inf inf: wdmaudio.inf inf: Include Scope = Services inf: Config Flags = 0x00000000 inf: {Configure Driver Configuration: exit(0x00000000)} inf: {Configure Driver: exit(0x00000000)} You can see it says "Updated service" 'l6PodGo' and 'l6podgo_AvsFilter' (the bane). I am still trying to find the reference to this because even after remove the .sys files it still sys updated service. I found them left over in the registry, so I am guessing it has something to do with that, a task for tomorrow: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/l6PodGo.sys Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/l6PodGo_AvsFilter.sys Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/l6PodGo.sys Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/l6PodGo_AvsFilter.sys These logs are in the C:\Windows\INF\setupapi.dev.log file if you are looking. 1 Quote Share this post Link to post Share on other sites
weitzhandler 1 Posted December 9, 2020 Thanks for your input @saxatron, were you then able to run the device from Windows after your experiments? Quote Share this post Link to post Share on other sites
saxatron 4 Posted December 9, 2020 Sadly, still no luck. This is the latest attempt, I seemed to have missed a few on my last cleanup so i am going to try once more. I also didn't touch the registry for this attempt. flq: {FILE_QUEUE_COMMIT} 12:45:53.474 flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\l6PodGo.sys' to 'C:\WINDOWS\System32\drivers\l6PodGo.sys'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\l6PodGo_AvsFilter.sys' to 'C:\WINDOWS\System32\drivers\l6PodGo_AvsFilter.sys'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6PodGoAsio_OnInterposer_x64.dll' to 'C:\WINDOWS\System32\L6PodGoAsio_OnInterposer_x64.dll'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6PodGoAsio_OnInterposer.dll' to 'C:\WINDOWS\SysWOW64\L6PodGoAsio_OnInterposer.dll'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\InterposerPodGoBackend64.dll' to 'C:\WINDOWS\System32\InterposerPodGoBackend64.dll'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6ConfigPodGo.xml' to 'C:\WINDOWS\System32\L6ConfigPodGo.xml'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\InterposerPodGoBackend.dll' to 'C:\WINDOWS\SysWOW64\InterposerPodGoBackend.dll'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6ConfigPodGo.xml' to 'C:\WINDOWS\SysWOW64\L6ConfigPodGo.xml'. cpy: Existing file 'C:\WINDOWS\SysWOW64\L6ConfigPodGo.xml' remains unchanged. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\L6Driver2PodGoControlPanel.cpl' to 'C:\WINDOWS\System32\L6Driver2PodGoControlPanel.cpl'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\l6podgo.inf_amd64_bd193ff778222cfc\WdfCoInstaller01009.dll' to 'C:\WINDOWS\System32\WdfCoInstaller01009.dll'. idb: Last driver package 'l6winusb.inf_amd64_680039b30d9a1455' to copy 'C:\WINDOWS\System32\WdfCoInstaller01009.dll' needs reconfiguration. flq: Hardlinking 'C:\WINDOWS\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_fee724aa691ec5b0\drmk.sys' to 'C:\WINDOWS\System32\drivers\drmk.sys'. cpy: Existing file 'C:\WINDOWS\System32\drivers\drmk.sys' remains unchanged. flq: Hardlinking 'C:\WINDOWS\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_fee724aa691ec5b0\portcls.sys' to 'C:\WINDOWS\System32\drivers\portcls.sys'. cpy: Existing file 'C:\WINDOWS\System32\drivers\portcls.sys' remains unchanged. flq: {FILE_QUEUE_COMMIT - exit(0x00000000)} 12:45:53.538 This line is concerning idb: Last driver package 'l6winusb.inf_amd64_680039b30d9a1455' to copy 'C:\WINDOWS\System32\WdfCoInstaller01009.dll' needs reconfiguration. As this did not show up on my wife's computer. Also this error code: ! dvi: Device 'USB\VID_0E41&PID_4247&MI_01\8&17BA1CFE&1&0001' not started: Device has problem: 0x27 (CM_PROB_DRIVER_FAILED_LOAD), problem status: 0xc000007b. Means that it is trying to use a driver compiled on x86 instead of x64, so that is where my focus is right now. Would be great if you could check you `C:\Windows\INF\setupapi.dev.log` and see if you see something similar. Thanks. 1 Quote Share this post Link to post Share on other sites
weitzhandler 1 Posted December 9, 2020 My issue is different but the l6 files are starring all over the place in the setupapi.dev.log file. Quote Share this post Link to post Share on other sites
saxatron 4 Posted December 11, 2020 Sadly, I'm out of ideas. It appears to be a driver issue on more recent hardware. I full factory reset my computer this time to clean the registry, so that isn't the problem. 2 questions @weitzhandler, are you running Windows Pro? And how new is your desktop? Thanks. Quote Share this post Link to post Share on other sites
saxatron 4 Posted December 12, 2020 Ok. I gave up and am returning my laptop, I literally tried everything I could think of. I had bought the laptop basically to exclusively do music with my Pod Go, so makes me sad. The only real difference between my wife's Surface Book and mine was I was on Windows Pro (which it looks like you are) and I had usb 3.1 instead of usb 3.0. I had read somewhere that the Hypervisor security may be the cause of similar errors, so maybe look into that. Sorry I can't be of more help but I think my journey with this issue ends here. Quote Share this post Link to post Share on other sites
