Page 1 of 1

UltraStudio Monitor 3G not recognized by Desktop Video

PostPosted: Wed Sep 22, 2021 7:02 pm
by amcmhc
I am using Windows 10
I have tried:
Desktop Video 12.1
Desktop Video 12.0
Desktop Video 11.7

I did restarts after each install/uninstall

I tried 9 different USB-C to USB-C cables
I tried USB-C to USB

I updated my Windows 10 + "non essential" updates

The Mini Monitor shows up in my device manager. But not in the Black magic software (including Resolve)
also the white light on it does NOT turn on (My assumption is that it is not getting enough power?)

I tried right clicking it in the device manager, I tried disabling/enabling it
I tried "updating driver" for it but that just takes me to BM's website or something.

I have a big project I am starting tomorrow, this will make that very difficult!

PC INFO

Edition Windows 10 Home
Version 21H1
Installed on ‎7/‎25/‎2021
OS build 19043.1237
Experience Windows Feature Experience Pack 120.2212.3530.0

Processor Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz 3.70 GHz
Installed RAM 48.0 GB
System type 64-bit operating system, x64-based processor

Gigabyte Z370 AORUS Gaming 7 (rev. 1.0) ATX LGA1151 Motherboard

Re: UltraStudio Monitor 3G not recognized by Desktop Video

PostPosted: Mon Sep 27, 2021 6:32 pm
by Ed Stradling
I've just bought one and plugged it into my Thunderbolt Windows 10 laptop, which doesn't recognize it either. Will post back if I find a solution.

Re: UltraStudio Monitor 3G not recognized by Desktop Video

PostPosted: Tue Sep 28, 2021 8:17 am
by Uli Plank
It's working fine here on a Mac mini, but only if plugged directly into the machine. It doesn't work over any hub.

Re: UltraStudio Monitor 3G not recognized by Desktop Video

PostPosted: Sun Nov 21, 2021 10:56 pm
by cestlefou
Hi there,

Recently I had the same problem on Windows 10 and I found a possible solution:

Go to the bios system and change the thunderbolt's security level,
in my case, it's on "No Security."

And if you can't get into the bios system, unplug the thunderbolt cable and try again.

Hope this would help anyone to resolve the problem in the future.