Hi,
I'm 828ES user for almost a year. Today (probably after Windows Update) the device has lost connection (USB) with the comp: MOTU Discovery can't find it and there's famous yellow sign with warning in the Device Manager ("This Device Cannot Start Code 10 Error"). I tried different ports and cables - nothing helps. But I've tested it with fresh install on my laptop and everything works fine. Also other audio devices work on my PC without problems. So probably the driver is corrupted but I can't get rid of it from my system - deleting the driver from the Device Manager and removing MOTU software also doesn't help. I had a clean install of my Windows two months ago, so I'd like to avoid this way of repairing.
Maybe somebody had similar experience and can offer a solution?
828ES: Device Manager can't start the hardware device
Moderator: James Steele
Forum rules
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
828ES: Device Manager can't start the hardware device
Studio One Professional 5.0 | Windows 10 Home (x64)
i7 8700K | Gigabyte Aorus Gaming 7 | 4x 8GB DDR4
MSi GeForce RTX 2070S | Samsung SSD 960 PRO 512GB
i7 8700K | Gigabyte Aorus Gaming 7 | 4x 8GB DDR4
MSi GeForce RTX 2070S | Samsung SSD 960 PRO 512GB
- HCMarkus
- Posts: 10378
- Joined: Tue Jan 10, 2006 9:01 am
- Primary DAW OS: MacOS
- Location: Rancho Bohemia, California
- Contact:
Re: 828ES: Device Manager can't start the hardware device
I'd read out to MOTU directly. I had a similar issue once with my 828es (macOS) and had to reinstall my system. One reason I now keep a clone of my system drive. Don't want to have to do THAT again.
I seem to recall a post here at MOTUNation with some info re: accessing and deleting low-level driver software, but I think it was aimed a Mac folk.
I seem to recall a post here at MOTUNation with some info re: accessing and deleting low-level driver software, but I think it was aimed a Mac folk.