• Registered: 2019-10-24
  • Posts: 11

Topic: New totalmix installs will not work consistently in Win 10 v 22H2

20 year RME user. this is the first significant issue I've ever had. Just did a brand new complete install of my system based around Cubase 13. Fireface UFX+ (mk1). Same computer build/hardware that has been working perfectly for 4 years, running on built in Thunderbolt (Asus Prime X299-Deluxe II).

The only thing that has changed is Windows 10 is now at v22H2 were previously I had it hovering around 21H__ (can't remember)

I have been uninstalling and reinstalling the RME thunderbolt (and Madiface drivers, even though I don't use them)  in and effort to get my previous functionality back. it has worked for up to a week, then for some reason the Totalmix window will fail to load or the whole driver seems to be unable to function.

Currently I can get the driver to function for Cubase (and thunderbolt connection seems fine) but I can't get the total mix window to come up automatically or otherwise. I have the app in system 32 on a desktop short cut but it won't start the total mix window, running as admin or otherwise. It does appear to be in the startup but not in the current processes under task manager.

I just completely disabled Windows defender features (with regedit so it stays off) under suspicion it was messing with things but now without that running this still won't work.

Currently stumped as to why this wont work now and its severely limiting to not have control over the total mix settings.  Anyone run into this recently?

  • Registered: 2019-10-24
  • Posts: 11

Re: New totalmix installs will not work consistently in Win 10 v 22H2

Just discovered that it now will allow total mix to function on USB3.1 but still not on thunderbolt. Switching to thunderbolt actively turns off the total mix window. would really like to fix this.

  • Registered: 2019-10-24
  • Posts: 11

Re: New totalmix installs will not work consistently in Win 10 v 22H2

And now it doesn't work on USB either. strange

  • waedi
  • DAW Mastermind
  • Offline
  • From: Swiss Zürich
  • Registered: 2020-12-08
  • Posts: 4,839

Re: New totalmix installs will not work consistently in Win 10 v 22H2

Did you try to run the FUT for a firmware update ?

M1-Sequoia, Madiface Pro, Digiface USB, Babyface silver and blue
  • Registered: 2019-10-24
  • Posts: 11

Re: New totalmix installs will not work consistently in Win 10 v 22H2

waedi wrote:

Did you try to run the FUT for a firmware update ?

Yes thanks. the firmware is current.

  • waedi
  • DAW Mastermind
  • Offline
  • From: Swiss Zürich
  • Registered: 2020-12-08
  • Posts: 4,839

Re: New totalmix installs will not work consistently in Win 10 v 22H2

it's more about if the FUT works, means the driver is working. Then Totalmix should work too.
What is the DeviceManager in windows showing ?
Is the UFX listed as audio device correctly ?

M1-Sequoia, Madiface Pro, Digiface USB, Babyface silver and blue

7 Reply by vinark (edited by vinark 2024-12-05 07:58:35)

  • vinark
  • DAW Mastermind
  • Offline
  • Registered: 2009-06-05
  • Posts: 2,834

Re: New totalmix installs will not work consistently in Win 10 v 22H2

Are you sure it is not hidden? Have a look in device manager. There is an age old windows bug in regards to sys tray icons not showing, which has to do with the timing during start up. At this moment my tinywall icon is eratic. Not showing up half of the time. But it is running. I just surrendered and have an shortcut on the desktop for it. In a distant past I had the same issue with totalmix and had to put a shortcut for it on the desktop then. But not currently.
A way to check this hypothesis is to have the ufx disconnected or turned off until windows is fully started. If you then turn it on and totalmix appears you know it it is this issue. It will not help to turn off and on since totalmix is then already running but hidden.
Cheers!

Vincent, Amsterdam
https://soundcloud.com/thesecretworld
BFpro fs, 2X HDSP9652 ADI-8AE, 2X HDSP9632
  • Registered: 2019-10-24
  • Posts: 11

Re: New totalmix installs will not work consistently in Win 10 v 22H2

waedi wrote:

it's more about if the FUT works, means the driver is working. Then Totalmix should work too.
What is the DeviceManager in windows showing ?
Is the UFX listed as audio device correctly ?


Yes the Fireface is showing up in USB and Thunderbolt modes as a working device where it should be.

  • Registered: 2019-10-24
  • Posts: 11

Re: New totalmix installs will not work consistently in Win 10 v 22H2

ramses wrote:

@MikeOlsen: could you please be so kind to remove your double post? Thanks.
https://forum.rme-audio.de/viewtopic.php?id=40644


Ah sorry about that, couldn't find the post perhaps it was removed already? if so good.

  • Registered: 2019-10-24
  • Posts: 11

Re: New totalmix installs will not work consistently in Win 10 v 22H2

vinark wrote:

Are you sure it is not hidden? Have a look in device manager. There is an age old windows bug in regards to sys tray icons not showing, which has to do with the timing during start up. At this moment my tinywall icon is eratic. Not showing up half of the time. But it is running. I just surrendered and have an shortcut on the desktop for it. In a distant past I had the same issue with totalmix and had to put a shortcut for it on the desktop then. But not currently.
A way to check this hypothesis is to have the ufx disconnected or turned off until windows is fully started. If you then turn it on and totalmix appears you know it it is this issue. It will not help to turn off and on since totalmix is then already running but hidden.
Cheers!

Yes pretty sure its not just hidden. Ive got a desktop shortcut from the system 32 folder as well and I've tried to get in to all the places its installed to start it up. Total mix is not showing as a running process either. I was even able to use the USB audio driver to record something last night in a pinch, but I wasn't able to use Total mix to control my monitor mix for instance.

One thing I noticed last night is that it appears to not be completely uninstalling, in that after uninstall there appears to be folders of various drivers left over. Last night I tried to manually erase all of these but had to change the permissions of the c drive to be able to do so. But then after changing the permissions back a fresh thunderbolt driver install fails every time. Eventually I just went back a few days to a previous clone of the c drive because it felt like I may have gotten over zealous and erased  a bit too much. I might try again to just erase the main driver folder left in in system 32 after uninstall. I feel like this might be what is causing the issues. In general I feel like this is a Windows install issue having to do with Windows permissions and Windows defender perhaps.

  • vinark
  • DAW Mastermind
  • Offline
  • Registered: 2009-06-05
  • Posts: 2,834

Re: New totalmix installs will not work consistently in Win 10 v 22H2

Did you try to run TMFX as admin one time? that sometimes helps after windows update breaks things.
Does the rme settings app load?

Vincent, Amsterdam
https://soundcloud.com/thesecretworld
BFpro fs, 2X HDSP9652 ADI-8AE, 2X HDSP9632
  • Registered: 2019-10-24
  • Posts: 11

Re: New totalmix installs will not work consistently in Win 10 v 22H2

vinark wrote:

Did you try to run TMFX as admin one time? that sometimes helps after windows update breaks things.
Does the rme settings app load?

Hi!  thanks for the suggestions smile

I've had it running as admin several times yes. The settings app was loading through most of this , though at one point it wouldn't  after several install reinstalls.

Interestingly I booted up one time a few days ago and it just started working again. Nothing had changed. I scrambled to get some work done but i wonder if the issue is dormant and will strike again.

I will say that the strongest clue was all the windows sys and driver files I found when the software was "uninstalled". I'm not savvy enough to know if this is standard, but the full install folder was still sitting in system 32 with, as far as I could tell, all the files in it. This was not the one called driver store, which perhaps is an archive, they were there too.  But the main driver folder in system 32 was there and yet the computer behaved as if it was not installed, until I installed it again, and then it would work in the half functioning thing I've described.

So if there are files being left by the installer maybe that is the conflict that is  doing this. And since I assume that RME is capable of building a functioning installer I suspect some windows feature, likely in Windows defender or maybe a permissions thing, is messing with the process, (despite the fact I do all these things as admin)

So I dunno, but it seems to work now so Ill watch it for a while. If anyone is having this issue or someone from RME wants to look into it Id certainly like to know why its happening. Ill be doing this whole thing again at some point.