Home Lexicon User Forum Lexicon Products

Lexicon Omega drivers have been replaced by Windows Audio Endpoint drivers.

My - previously working - v2.7 Lexicon Omega drivers have been replaced by Windows Audio Endpoint drivers.

Basic Windows sound works but Cubase and Reaper cannot - now - connect through the Lexicon drivers.

The "Update Drivers" button tells me that "The best drivers for your device are already installed".

The Lexicon is now being treated as a Class-Compliant device that doesn't NEED drivers installed.

I have tried:
Hardware Reset
Uninstalling in Device Manager and reconnecting
Reinstalling the v2.7 drivers, rebooting and reconnecting

Comments

  • HARMAN_EEldeHARMAN_EElde Posts: 1,360

    I personally have tested the Greek Series (Alpha, Lambda, Omega) on Windows 10 latest build 1909 with Reaper, CuBase LE (9 thru 10.5), and S1 latest build (4.6 as of this writing).

    I would recommend uninstalling the Omega Driver with this advanced uninstaller:
    https://www.iobit.com/en/advanceduninstaller.php

    If you are on Windows 10, make sure to disable Driver Signing before reinstalling:

    WINDOWS 10 OPERATING SYSTEM NOTIFICATION
    Windows 10 enforces driver signatures by default. This can be disabled to install drivers that are not digitally signed. Use the following steps to disable driver signature enforcement.

    Click the Start Start menu and select Settings.
    Click Update and Security.
    Click on Recovery.
    Click Restart now under Advanced Startup.
    Click Troubleshoot.
    Click Advanced options.
    Click Startup Settings.
    Click on Restart.
    On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.
    Your computer will restart and you will be able to install non-digitally signed drivers. If you restart your computer again the driver signature enforcement will be re-enabled.

    If it still is trying to install the WDM driver, go into Device Manager and manually select the Omega driver (don't search automatically) and point it to the driver file itself.

    If you're still having problems let me know or contact Tech Support below.

  • elmo7sharp9elmo7sharp9 Posts: 8
    edited April 2020

    Thanks for the rapid response.
    I have tried your suggested fix without success:

    Device Manager "Browse My Computer For Driver Software"...

    Pointed to the v2.7 "OmegaDriverInstaller.exe"

    Next dialog box is "The best drivers have already been installed".

    NOT BEATEN YET...

    Device Manager "Let me pick from a list of available drivers on my computer"...

    Has 2 options: "Audio Endpoint" and "Generic software device".

    NOT WHAT I NEED...

    So, from here, choosing the "Have Disk" option, I navigate to the folder for the v2.7 "OmegaDriverInstaller.exe". The resulting file selector box is looking for "autorun.inf".

    I tried to defeat this by entering . in the filename box, then selecting the v2.7 "OmegaDriverInstaller.exe", but the file selector is hard-coded to only accept "*.inf" files.

    Any clues?

  • Thanks for the rapid response.
    I have tried your suggested fix without success:

    Device Manager "Browse My Computer For Driver Software"...

    Pointed to the v2.7 "OmegaDriverInstaller.exe"

    Next dialog box is "The best drivers have already been installed".

    NOT BEATEN YET...

    Device Manager "Let me pick from a list of available drivers on my computer"...

    Has 2 options: "Audio Endpoint" and "Generic software device".

    NOT WHAT I NEED...

    So, from here, choosing the "Have Disk" option, I navigate to the folder for the v2.7 "OmegaDriverInstaller.exe". The resulting file selector box is looking for "autorun.inf".

    I tried to defeat this by entering the star-dot-star wildcard in the filename box, then selecting the v2.7 "OmegaDriverInstaller.exe", but the file selector is hard-coded to only accept "*.inf" files.

    Any clues?

  • I ran the Device Manager while Windows was in "disable Driver Signing" mode to eliminate as many variables as possible.

    STILL NO SUCCESS...

    The procedure produced the same results as before:
    "The best drivers have already been installed".

    I tried writing my own "autorun.inf" to the same directory as the v2.7 "OmegaDriverInstaller.exe":
    [autorun]
    open=OmegaDriverInstaller.exe
    icon=OmegaDriverInstaller.exe,0
    label=OmegaDriverInstaller

    Choosing the "Have Disk" option, I navigated to the folder for the v2.7 "OmegaDriverInstaller.exe". The resulting file selector box is - again - looking for "autorun.inf", which I pointed to successfully.

    I got a dialog box:
    "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."

    The "Driver Details" button in Device Manager continues to report:
    "No driver files are required or have been loaded for this device".

    I have emailed Tech Support with the story so far...

  • HARMAN_EEldeHARMAN_EElde Posts: 1,360

    You need to install the driver and point it to the .inf file, found at this path: C:\Program Files\Lexicon\Omega

    If you're still having issues let me know. I believe I just replied to your email as well

  • Thanks for your continued support.

    C:\Program Files\Lexicon\Omega has no .inf file.

    There's OmegaAsio.dll and an x64 folder, containing the x64 version of the .dll,
    but no .inf file.

  • HARMAN_EEldeHARMAN_EElde Posts: 1,360

    You're correct, I was mistaken, that is the ASIO.dll

    The driver it needs to use is wdma_usb.inf and it is in the C:\Windows\INF folder.

  • elmo7sharp9elmo7sharp9 Posts: 8
    edited April 2020

    Thanks for persisting with this so far.

    I have followed your advice to the letter, taken the "Have Disk" route, navigated to C:\Windows\INF folder in the dialog box and specified wdma_usb.inf

    On coming out of THAT box, it looks like only the INF directory has been specified as a location, but not the specified wdma_usb.inf file.

    The next message is... "Windows has successfully updated your drivers".

    To "Audio Endpoint".

    Back to square one...

    If I enter C:\Windows\INF\wdma_usb.inf into the "Copy manufacturers files from" box, I get an error message, telling me there are no suitable files in that location (Clearly looking for a directory, not a file...).

    I have also tried right-clicking on the wdma_usb.inf file and selecting the "Install" option - which leads nowhere and changes nothing.

    Anything else I can try?

  • HARMAN_EEldeHARMAN_EElde Posts: 1,360

    That's about all the info I have, like I said it's working on my build just fine. Try to update your motherboard chipset drivers, sound card, etc. Also maybe disable the Windows Audio Endpoint from services.msc.

  • elmo7sharp9elmo7sharp9 Posts: 8
    edited April 2020

    Thanks for your efforts.
    Your support for a discontinued product is a rare thing.

    It looks like "You can't get there from HERE...".

    The Lexicon works well in other situations (Even connected to a Raspberry Pi...),
    but I'll need to retire it .

    Oddly, none of my other interfaces have been affected,
    just the one I use the most...

    This is Microsoft's fault.
    Breaking gear by remote control, for no reason...

  • HARMAN_EEldeHARMAN_EElde Posts: 1,360

    Indeed, yeah sometimes it is a matter of incompatibility and that's that. Well if I find any further information I will share this with you!

  • wolfcaswolfcas Posts: 1

    Hi, I'm having same troubles to get my Lexicon Omega work in Windows10 - Cubase.
    I tried all the steps above. Still doesn't work. Would there been a solution in the meantime?

  • HARMAN_EEldeHARMAN_EElde Posts: 1,360

    @wolfcas said:
    Hi, I'm having same troubles to get my Lexicon Omega work in Windows10 - Cubase.
    I tried all the steps above. Still doesn't work. Would there been a solution in the meantime?

    I have tested all of the Greek Series interfaces (Alpha, Lambda, Omega) on Windows 10 latest build 20H2 and they are all working no problem.

  • DavidWBDavidWB Posts: 1

    Hello.
    Omega was working till Friday, and had been installed since Win 8 new PC and through Win10 upgrades.
    I uninstalled it for troubleshooting other issues, but now am unable to install drivers (2.7 version).
    I have Win10 20H2 build, tried disabling driver signing enforcement, running install as administrator, with compatibility settings, combinations of the above, no luck.
    I get the files installed in Program Files, but in device manager Omega is not recognized., and when I try “update driver” pointing to INF files, I get “no good driver files at location”.
    Perhaps manually pointing to driver files? Any registry hacks anyone could suggest?

  • HARMAN_EEldeHARMAN_EElde Posts: 1,360
    edited April 2021

    @DavidWB said:
    Hello.
    Omega was working till Friday, and had been installed since Win 8 new PC and through Win10 upgrades.
    I uninstalled it for troubleshooting other issues, but now am unable to install drivers (2.7 version).
    I have Win10 20H2 build, tried disabling driver signing enforcement, running install as administrator, with compatibility settings, combinations of the above, no luck.
    I get the files installed in Program Files, but in device manager Omega is not recognized., and when I try “update driver” pointing to INF files, I get “no good driver files at location”.
    Perhaps manually pointing to driver files? Any registry hacks anyone could suggest?

    I have yet to get my hand on an Omega again since the 20H2 update but yes it seems to have broken things with the Greek series lately for some, but my initial tests I was able to get all of the interfaces working. I did have to disable driver signing enforcement was it

    I'll do what I can in the meantime to see if there is fixes for the people having problems, but not being in the office regularly with the equipment hinders that some. I'll post anything new info wise when I get it and if I happen to roll by the office and do some tests with it to see. Of course if anyone else figures anything out please share it with the rest of us.

  • hvemer111hvemer111 Posts: 2
    Hi, I have the same problem as stated above. Are there any fix for this?
  • HARMAN_EEldeHARMAN_EElde Posts: 1,360

    Was able to test the Omega with no problems and the 20H2 update. Cannot be reproduced as of now.

  • hvemer111hvemer111 Posts: 2
    Is it possible that either you try to test it on a new installed Windows 10 or leave a guide (with .INF file to download) since my only option as for now is to get rid of the sound module or downgrade to Windows 7.
    Both options is one step from uacceptable and extreme fustrating.

    BR. Lars
  • HARMAN_EEldeHARMAN_EElde Posts: 1,360

    @hvemer111 said:
    Is it possible that either you try to test it on a new installed Windows 10 or leave a guide (with .INF file to download) since my only option as for now is to get rid of the sound module or downgrade to Windows 7.
    Both options is one step from uacceptable and extreme fustrating.

    BR. Lars

    It's been tested on two different Windows 10 Machines now with actually the latest version 21H1. We do not have a manual driver install method no. Unfortunately since the product is discontinued for several years, no new drivers will be forthcoming.

  • J4dyceJ4dyce Posts: 1

    I think I may have stumbled across some help for this problem. I have been trying to get my lexicon working again. Anyway I was hoping to just plug it in and have it come to life :( soo... I did all the above, reboot ad nauseum which got me thinking "how bad is this screwing up the registry and temp files etc?" I know from experience having done my time in IT that this happens; so I ran a shareware app "CCleaner" to do quick clean of the PC but more importantly I had it scan the registry, back it up and clean the thousands of errors (haven't done it for a while).

    Now I did not have the Lexicon plugged into the USB while I did the clean up so I plugged it in with my same naïve hopefulness. This time however I was a bit more determined so I opened the Windows Administrative Tools and fired up the computer management console. Under system tools is the device manager is where I checked out drivers etc. and when I opened the audio inputs and outputs section, what do you know there was my lexicon just as it should be ;-)

    Upon further examination the driver Is a microsoft driver now however it does identify the device properly and best of all it works. I only have Audacity on this PC but all the ins and outs show in the dropdowns.

  • HARMAN_EEldeHARMAN_EElde Posts: 1,360

    @J4dyce said:
    I think I may have stumbled across some help for this problem. I have been trying to get my lexicon working again. Anyway I was hoping to just plug it in and have it come to life :( soo... I did all the above, reboot ad nauseum which got me thinking "how bad is this screwing up the registry and temp files etc?" I know from experience having done my time in IT that this happens; so I ran a shareware app "CCleaner" to do quick clean of the PC but more importantly I had it scan the registry, back it up and clean the thousands of errors (haven't done it for a while).

    Now I did not have the Lexicon plugged into the USB while I did the clean up so I plugged it in with my same naïve hopefulness. This time however I was a bit more determined so I opened the Windows Administrative Tools and fired up the computer management console. Under system tools is the device manager is where I checked out drivers etc. and when I opened the audio inputs and outputs section, what do you know there was my lexicon just as it should be ;-)

    Upon further examination the driver Is a microsoft driver now however it does identify the device properly and best of all it works. I only have Audacity on this PC but all the ins and outs show in the dropdowns.

    Thanks for your update, as I have said I've tested with the latest build and updates for Windows 10 21H1 and still have not gotten an issue to where I could not use the Greek series interfaces. So I can't recreate the issue to see. Any info anyone else finds is appreciated of course.

  • nergnerg Posts: 5

    My Omega was working fine for years, even after upgrading to win 11, but after a fresh win 11 install I can't get it working again.
    I've downloaded the drivers and followed the instructions, but the Omega drivers v2.7 for Windows doesn't contain any driver!
    I've compared with Lambda and Alpha and both of them contain the WinUSB folder that Omega is missing.

  • nergnerg Posts: 5

  • You have to disable Windows Driver Signature Enforcement to install the driver. Also the Omega driver is different than the Alpha and the Lambda, it does not install the same. That is why you are not seeing the WinUSB folder.

    We have discontinued all development for the Greek series, and as I have said, I have tested the Omega driver up to Windows 10 update even 21H2 the latest. We cannot guarantee it will work with later updates to Windows 10 or an OS like Windows 11

  • nergnerg Posts: 5
    I have disabled Windows Driver Signature Enforcement.
    Please explain how you can install and choose the driver when there's no .inf file
  • nergnerg Posts: 5

    Sorry for my harassment, my Omega has finally been found by Windows. I have no idea how and when. Maybe it just needed a few reboots

Sign In or Register to comment.