A big update came in a day ago, and now I find that about a minute after reboot, my audio interface stops working.
Unfortunately this is an old Lexicon Lambda device which is no longer supported by the manufacturer. I had to go though a rather laborious process of disabling windows driver signature checks to get the driver installed in the first place.
But now it looks as if they have upped the ante on unsigned driver checks. I’m guessing that there is some new daemon process which runs after reboot and kills off unsigned drivers?
I realize this is a bit of a folorn cry for help, but if anyone has any knowledge or suggestions I would be very grateful. Otherwise I guess I’m going to have to just capitulate and buy a newer interface…
Ah, I see this has been moved to IMHO.
Fair enough… I only originated it under Cafe Society because the audio interface is one I use for recording original songs etc.
In fact, one might almost call this a Factual Question, but no worries.
So far I have tried disabling the driver signature checks and reinstalling the driver.
Also scanned through the event logs looking for error messages but I don’t see anything obvious.
What is odd is that the interface works for about a minute after reboot, and then drops out.
So the driver is clearly ‘sort of’ there, but some process knocks it off after a minute.
I suspect that if I could identify what that process is, I might be able to disable or modify it?
Any thoughts from Windows experts much appreciated…!
I’ve had a read through, but it doesn’t seem to be the same problem.
This started about one day ago and was definitely caused by a major windows 11 update that came in.
It rather looks as if the Lexicon interface is somehow being kicked off the USB bus at the one minute point: the power light goes out. To be honest I’m a bit worried that if I give in and buy something current like a Focusrite, I might just end up with the same problem?
In other words, maybe it’s not a problem specific to a particular old driver: perhaps they have broken something more generic in the latest Win 11 update?
I guess if that’s the case we’ll soon start hearing about it from other users…
Well, dammit: no. Installed that update, and I still get the same behavior.
The audio interface comes up at boot, but drops off after about a minute.
F-ing Microsoft have certainly broken something.
I don’t know if it’s connected with the fact that my interface & its driver are several years old & the driver is not ‘signed’. But I’m still dead in the water.
I guess I am going to wait a while for more news before I think about buying a new interface.
Begining to suspect that this is something generic, not connected to a particular device or driver?
If so, I’m guessing that howls of complaint will soon be heard…?
FWIW, I was having intermittent trouble with my audio device for several months, on a Windows 10 system. My audio device would just disappear from settings. I tried all kinds of solutions and probably spent several hours in total working on it. Then I discovered that I could get a USB audio dongle for $10. I got one and it worked fine. Life’s too short to waste that much time to save $10.
Well, this is very odd. I find that if I open my DAW (Reaper, which is configured to use the Lexicon interface for IO), immediately after bootup, the audio interface stays active. Presumably because an application has it open so nothing else is allowed to close it?
But if I close Reaper later, within 1 more minute the interface shuts down.
I don’t know what the heck is going on here. Windows is WEIRD.
Just an FYI: I’ve lost my audio on several occasions because of Windows updates. I go to Device Manager and uninstall the audio hardware component, choose “retain drivers”, and restart. Windows detects the “new” audio hardware and installs it. Works perfectly, at least until the next Windows update. LOL
I’m on a bit of a sticky wicket here because my USB audio interface is at least 5 years old, no longer supported, and the driver predates the ‘windows signed’ security business, so I can’t really expect any official support.
Still, I seem to have a workaround for the moment. Who knows how long that will last…?
I wouldn’t really object too much to buying a new interface… after all, 5 years is an eternity in computer gear time. But the old kit does its job perfectly well, and newer interfaces don’t seem to have any feature that I feel I must have. After all, a basic audio interface just needs to do one job properly.
But I’d be REALLY PISSED OFF if I spent money on a new interface and it exhibited the same dropping out problem…
Not really working. It opens, but with a lot of distortion.
The latest Win11 update has definitely broken something for USB audio interfaces.
It may be connected with the fact that mine is older, but BROKEN it is.
I am going to leave the system up with Reaper running in the background for the night.
But this is not good.
Hah! I uninstalled the latest update, and behold, my audio interface is working perfectly again.
So it is DEFINITELY a problem with that update.
I have disabled automatic updates for the moment.
But sooner or later I suppose I will have to let updates run again…
I’ll report the problem to Microsoft of course.
But I don’t have much faith that will accomplish anything…
