Scott Hanselman

Temporary Fix: Logitech BRIO Camera broken on Windows 10 Insiders 15042

February 25, 2017 Comment on this post [10] Posted in Bugs | Win10
Sponsored By

I just updated my Windows 10 to Insiders Fast Build 15042, and suddenly my glorious new Logitech BRIO 4k webcam doesn't work! Well, it's all beta software, but it turns out the issue is with something in the Logitech INF files for their drivers. I'm assuming they'll figure it out, but the nutshell is that the first install works, but the driver gets messed up on the upgrade. You can't just pull out the camera and put it in again, you need to DELETE the drivers and have them redownloaded by Windows Update/Device Manager.

Here's a temporary fix (either until Logitech fixes it and it shows up in Windows Update or you take another Windows 10 upgrade):

Logitech BRIO stops working on Windows 10 Insiders UPGRADE

Go to device manager and right click the device and Uninstall Driver. If it has the checkbox "Delete this driver" then check it. That's required. IF (like me) you don't have that checkbox (I'm not sure why I don't) then you'll need to delete the Logitech driver from the DriverStore. You can do it manually but it's tricky and messy and hard.

We need to delete this driver so it gets reinstalled cleanly.

Driver 2/31/2017

Unplug your webcam. Then, go get the latest copy of DriverStoreExplorer from here https://github.com/lostindark/DriverStoreExplorer/releases and delete JUST this one driver.

Using the Driver Store Explorer

Now, go back to Device Manager and plug in your Logitech BRIO webcam. Note you'll get some super old 2006 driver. Right click the BRIO in Imaging Devices and Update Driver. This will get you BACK to your original state. You still have a driver that will break when you next take a "major" Windows update or Insiders Build, but at least you have a solution until it magically gets fixed.

Yay!


Sponsor: Big thanks to Progress! They recently published a comprehensive whitepaper on The State of C#, discussing the history of C#, what’s new in C# 7 and whether C# is still a viable language. Check it out!

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Hosting By
Hosted in an Azure App Service
February 25, 2017 13:25
With installation of Build 15042, my Brio disappeared at all and even if i delete the driver manually, unplug the device, reboot, reconnect it, Windows doesn't discover it as a new device.
The entries for Brio as USB Audio Device and Mic will return, but the camera itself does not work at all. The Logitech Settings App says "No camera found" (even after reinstall)
Any idea?
February 25, 2017 16:15
Turns out that that driver isn't actually from 2006, it's just a clever trick to make sure manufacturer/OEM drivers take precedence over MS-provided drivers:

https://blogs.msdn.microsoft.com/oldnewthing/20170208-00/?p=95395
February 25, 2017 19:51
http://www.hanselman.com/blog/EverythingsBrokenAndNobodysUpset.aspx

Sigh.

Fast Build 15042 or not. Software is worse than ever in 2017. And I'm not talking about Beta software - though alpha-level quality is what seems to ship in most final versions these days. Phone apps are even worse.

At least there are blogs like this on public www domains that offer free advice/support/tutorials/help for people, as many software companies don't bother to support their products anymore (except for a silly Twitter "support" feed).

The entire industry needs a major shakeup.
February 26, 2017 5:03
Why are all Windows drivers dated 2006?

Raymond Chen has the answer:

https://blogs.msdn.microsoft.com/oldnewthing/20170208-00/?p=95395

February 28, 2017 12:31
@Chris Lee "Software is worse than ever in 2017". I wholeheartedly agree that some software is worse than ever in 2017 but not all. The software that gets discussed in this blog a lot is definitely worse and imo is going in the wrong directions. Read into that what you will.
Joe
March 06, 2017 14:13
I had the same problem on my Logitech Cam and i cant solve it.

NO MORE Logitech cam for me. Great post tho, if you can help me go PM :/
March 08, 2017 11:45
Thanks very much for sharing I was looking for this information
March 09, 2017 1:37
Thx a lot! Worked fine with build 15048!
Tom
March 09, 2017 21:11
New board room up and running with the Logitec: 4K Ultra HD video calling (up to 4096 x 2160 pixels @ 30 fps) amazing quality. Thanks for the heads up on the Windows10 issue.
March 12, 2017 2:15
Thanks fixed the problem with build 15055

Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.