If your device fails to show after an update, do the following steps:

1. Unplug device.
2. Uninstall UC, reboot
3. Re-install latest version, reboot after.
4. After boot, plug in device.
4a. On PC, some TB devices need another reboot after hot plug to initialize (device on).

Try that.

Hi,

I also noticed that in Windows 10, the latest Thunderbolt drivers are not compatatble with the Quantum (1 and 2). I was getting static noise and crackles in windows sound and in S1. I tried all version of UC and even back graded the quantum Firewares...

What i found that the older version 16 and 17 intel Thunderbolt drivers worked but the later DCH 1.41 series didn't work... took ages to fault find this.. but i'm happy the older drivers work and windows hasn't tried to force the new drivers on me just yet.

I still have the random pops and CPU spike problems, but that is limited to my Acer and it's CPU.. work around there is to use Throttlestop and turn of speedstep and cpu turbo and lock the clock speed to their maximum non turbo speed (34Ghz in this case)... this seems to work for the most part... but since i've updated to a newer Asus laptop aslo with Thunderbolt, this problems does not persist.

Bottom line is. With the Quantums being older tek now, it's worth experimenting with driver and Universal control versions, to find the best combination that works for you. I wouldn't update UC just because a newer version is realised.

I'm using the latest TB3 drivers with no issues on my PC. I think you have a motherboard issue. Your TB3 chipset probably needs a firmware update to support the latest Intel drivers. Doing a quick google search of that laptop shows that Acer has not updated anything since 2017, which is likely why. It's an Alpine Ridge based chipset which has been replaced by Titan Ridge and now Maple Ridge (Thunderbolt 4).

Laptops go outdated quickly.

Well, something similar on my side. Mojave and latest UC/Firmware.

When I’ve done the update back in September, I noticed that I had to reboot as the Quantum 2626 wasn’t seen. It was available as an audio device but UC lost it. After a reboot, it was there… phew!

No big deal as I thought it was just a glitch… until yesterday when I noticed that after sleep, UC was not seeing the 2626 except after a reboot, again. Repeatable behavior. I didn’t noticed it prior because I haven’t used my DAW a lot in the last month.

My solution for now: back to older Universal Control and obviously, firmware 1.3.91. It now behaves fine and it’s always back after sleep.

Still happening with latest UC. However, 3.5.2.65533 is the latest good version for me. Definitely, powering off the 2626 then sleeping the computer= it won’t be recognized after sleep with 3.6.0.66460 and v3.6.1.84519. I don’t know if it behaves the same under Windows as I have to stay on 3.5.2.65533 on the two OS’ses as higher versions requires a firmware update (1.3.91 to 1.3.95).

Don't know if my experience will help, but I had a similar problem with MacBook Pro M1 Max and Monterey. I tried installing and uninstalling several times. UC worked fine on 3.6.0 but Quantum did not show as an output device with 3.6.1. It would also show device unresponsive if I selected it in UC. I submitted a support request to Presonus. Long story short was, the answer found was that I had to drag UC to trash to make the OS delete the extensions and then go through the install process. During install I had to go to security preferences to allow UC to install the new extensions. Now all is good. This problem was hard to isolate. I have installed new versions of UC many times and never had to do it this way. Hope this might help you find the answer to your problem.

I have found on latest Win 10 setup that UC 3.61(etc) doesn’t recognize my Quantum2 or Atom, although both work fine in Win10 and SO 5. Repeated delete install doesn’t change it. Rolling back to 3.60 (etc) works as expected. I have every driver updated. I haven’t put in a ticket yet, as 3.60 works fine. Maybe I will just wait till the next version. But I do have to keep ignoring the UC ‘new update’ available!

My impression is that one of the latest Win10 quality updates changed something, as I seem to recall UC 3.61 working when it originally came out a few months ago.

bartbalint wroteI have found on latest Win 10 setup that UC 3.61(etc) doesn’t recognize my Quantum2 or Atom, although both work fine in Win10 and SO 5. Repeated delete install doesn’t change it. Rolling back to 3.60 (etc) works as expected. I have every driver updated. I haven’t put in a ticket yet, as 3.60 works fine. Maybe I will just wait till the next version. But I do have to keep ignoring the UC ‘new update’ available!

My impression is that one of the latest Win10 quality updates changed something, as I seem to recall UC 3.61 working when it originally came out a few months ago.

Did you try my steps above? Disconnecting the device and completing a full uninstall/reinstall works for me every time a device fails to load after update. This is usually a driver issue. Reboots are needed between the uninstall and install.

I will follow your steps exactly again in a few days.
When I uninstall/then reinstall UC, all works as expected. Upon reboot the next day the UC window comes up abbreviated and without many of the menu items such as ‘rescan system’ under settings.

Thx. Will let you know.

bartbalint wroteI will follow your steps exactly again in a few days.
When I uninstall/then reinstall UC, all works as expected. Upon reboot the next day the UC window comes up abbreviated and without many of the menu items such as ‘rescan system’ under settings.

Thx. Will let you know.

Good news. I found the cause of the issue I was having with UC working right after install, but not working correctly the next day. Win 10 and StudioOne still recognized Atom and Quantum2 regardless of what UC was doing.

The issue was the sleep function of AVG tumeUp. It was putting a component of UC in a coma. Reinstall of UC corrected this, but just until reboot the next day. Turning off the sleep function cured the issue. Reinstated the sleep function recreates the issue. Good news is that the BIOS on my machine was updated in the whole process.

I cannot understand why people using anything else than Windows defender in 2022

[quote="TerjeNorway"]I cannot understand why people using anything else than Windows defender in 2022.

if you had some references that show Win defender is the absolute in anti malware, anti virus, etc., I would love to read them. Thx!

My point was Windows Defender as of today is better than anything on the marked so why use anything else when it is free and integrated in Windows.....
As for Malware you should use a seperate software like Malwarebytes. I just scan my pc with the free version once a week.
And why argue when AVG created the problem for you. Are you arguing against yourself?
By the way I used AVG years ago until it became a Malware itself with unwanted notification about premium version almost daily.

The issue isn't the Anti-Virus. It's Sleep/Hibernate.

Sleep/Hibernate has NEVER been suggested to use on a Audio Workstation, especially on PC. Mac is more graceful in this manner, but still not recommended.

Don't use that feature. Leave your computer on or just shut it off.

PAE Seth wroteThe issue isn't the Anti-Virus. It's Sleep/Hibernate.

Sleep/Hibernate has NEVER been suggested to use on a Audio Workstation, especially on PC. Mac is more graceful in this manner, but still not recommended.

Don't use that feature. Leave your computer on or just shut it off.

There could be at least 2 separate Sleep/Hibernate issues. Windows has sleep /hibernate options. Anything but ‘off’ always messed with my USB ports.

And AVG TuneUp, which is like CCleaner in some ways, has a sleep function. AVG tuneup is a separate program than AVG antivirus. I have never used AVG antivirus, but I have used TuneUp. It was Avg Tune Up causing the issue.

I do use win defender and scan intermittently with Malwarebytes, just like one of the previous contributors. No problems with either. Presonus support was sure it was just having Malwarebytes on my machine was the issue. It wasn’t, but support was insisting I remove it before they would proceed. I guess they have seen some issues like this caused by Malwarebytes.

I agree… don’t use hibernate sleep from either Win or AVG Tune up.

Just a little precision (or two!):

- same behavior with UC 3.6.2 form February;
- UC « sees » my 2626 if the computer enter sleep and UC stays open. Meaning that the 2626 is detected after sleep in UC. If UC is closed, it won’t detect the Quantum after sleep. A reboot is needed;
- no problems, as I’ve already noted, with 3.5.2.

However, I guess that if someone doesn’t use Universal Control with the 2626, it’s not a big deal as MacOS detects and use the interface correctly.

I know this is old but I want to thank you for saving my gigs... with the one thing that seems to have solved it.
Had some sudden issues after 2 years of stability with the 2626 intermittently not connecting. Reboot usually fixed it but then it unconnected right in the middle of practice. Updated UC and firmware, had some issues with firmware update, finally got it but it wouldn't be recognized at all (on Win 10). i spent an entire day trying to un-brick it. Here's my 2 cents...
yes, definitely reboot after UC uninstall and after install. Tried several UC versions, would sometimes work but then after reboot no joy. However, after clean reinstall of UC, shut down. Disconnect TB and power for 2626. Startup. After PC is fully started (i.e. 30 secs or more depending on PC) reconnect TB, then power 2626. Blue light, yay! Test by restarting without disconnecting TB/power... success! Restarted 3 more times, no issue.

Clearly there's something in the startup of my PC that's preventing recognition, still not sure what. I don't use AVG as others described, I use avast. either way, I always turn off Avast (which stays off even on reboot) and wifi. I think that helps.

As to what caused the issue in the first place, still not sure. Although I try to keep my gig rig off the web, I did do some music software updates a few days earlier, and I saw that Chrome had updated then. Don't know fi that's the issue, but I like to avoid ALL updates on my gig rig... if it ain't broke don't change it.

Good luck, and thanks!

Anyone tried the new UC 4 with Mojave or later on a Mac?

Curious to know if this « bug » is solved.

I could try myself but I’m too lazy