USB Volume Mixer Down 25/11/24

[Watcher590]

Just had a Windows Update for Win 11 that stopped my mixer from working. The update was "wch.cn - Ports - 3.9.2024.9" .

Had to rollback the CH340 driver to make the mixer work.

[Jeffreyjelly]

I didn't have the option of roll back. Had a similar issue on the latest update of windows breaking mine also.

However, Uninstalling the driver and restarting when prompted fixed the issue as the driver reinstall on boot up fixed it also.

Thanks!

[khalen56]

I had the same issue as well. Rolling back the driver seems to have fixed the problem on my side too.
I was also experiencing BSODs since this morning caused by "CH341S64.SYS," which could be related.

[lalexfrank]

Rolling back the driver to version 3.8.2023.2 worked for me as well.

[duckstin]

One more checking in on the driver rollback.

[SpoddyCoder]

Rollback wasn't an option for me (greyed out) - managed to find the 3.8.203.2 version here...

https://oemdrivers.com/usb-serial-ch340-driver-windows-7-64bit

All good after a manual install of the "WIN 1X" directory (not using the bundled installer).

[CartonWaff1e]

It stopped working for me last night as well. Does anyone know if an update to the deej software is going to roll out?

[TheL0ki]

+1 on the driver rollback

[Jeffreyjelly]

It stopped working for me last night as well. Does anyone know if an update to the deej software is going to roll out?

Try this:

#127 (comment)

[Boerny41]

Driver can be rolled back in device manager (i searched in windows update history...). There you can also select why you want to use the old driver, potentially giving feedback to the devs.

[Nichsen]

Rollback didn't work, I had to completely uninstall the device (with forced removal of the driver) and then reinstall this version:

Rollback wasn't an option for me (greyed out) - managed to find the 3.8.203.2 version here...

https://oemdrivers.com/usb-serial-ch340-driver-windows-7-64bit

All good after a manual install of the "WIN 1X" directory (not using the bundled installer).

[andysmithfal]

Rollback worked for me too - don't ignore the reboot prompt, you need to do that for it to apply.

[CardinalFangIsHere]

Rollback not working for me on windows 10

[jakesampson]

https://github.com/SHWotever/FakeCH340DriverFixer

Just installed this patch for my Fake Arduino chip and its working again.

[CardinalFangIsHere]

https://github.com/SHWotever/FakeCH340DriverFixer

Just installed this patch for my Fake Arduino chip and its working again.

Zero results for me, the deej app still starts and auto closes. Arduino ide app still reciving signals normally as before.

[Waffleer]

I went to device manager and rolled back my ch340 from 3.9.2024.9 to 3.5.2019.1 and it seems to be working again. Running windows 10. That said I never had deej.exe crash so that may be a different issue.

[CardinalFangIsHere]

I went to device manager and rolled back my ch340 from 3.9.2024.9 to 3.5.2019.1 and it seems to be working again. Running windows 10. That said I never had deej.exe crash so that may be a different issue.

The issue started when this did
EDIT: my issue was caused by a change in COM port. Finally found the log and saw that was the issue.

[Calomi]

https://github.com/SHWotever/FakeCH340DriverFixer worked flawless on windows 11 and as FakeCH340DriverFixer states: worked on a definitely counterfeit cheaper chip from aliexpress 🤣

Rollback wasn't an option for me (greyed out) - managed to find the 3.8.203.2 version here...

https://oemdrivers.com/usb-serial-ch340-driver-windows-7-64bit

All good after a manual install of the "WIN 1X" directory (not using the bundled installer).

[Gabe-H]

I was running into the same driver issue periodically. I was able to do a manual reinstall (#127-comment) one time, but having trouble now. This fork (not mine) updated lib dependencies and released a bin.

It worked perfectly for me, and still running driver 3.9.2024.9.

[Dr-Michl]

All these things above unfortunately didn't work for me. But I got it running again.

The solution for me was:

1. start deej-debug.exe
2. record the window with the slow-motion capture of my iPhone, because the window immediately closes again
3. look at the frames of the video and then find out that it creates audio session instances for every audio device
4. deactivate audio devices not needed in windows settings (in my case, my monitors)
5. start deej.exe and look at it working perfectly

In my case, after an update from Windows and/or Realtek Audio drivers it stopped working but it added my monitors as an audio device. I disabled them both and now it works again.

Just FYI, the log was saying the following before I got it running again:

deej-latest-run.log

Just as I'm writing this comment and looking at the log and the video frames from the deej-debug.exe again, I noticed that it registered my main monitor (Acer Predator XB271HUA) as device ID 2, so this most likely caused the problem, as the log says "Failed to enumerate and add process sessions for device {"deviceIdx": 2,[...]"