Windows 10: Update 20H2 corrupted system, broke windows hello and usb monitor.

An update was installed yesterday on my surface pro running windows 10, the initial issue was that windows hello face recognition stopped working along with an external usb connected monitor. Fingerprint was broken as well but I wasn't using that. After investigation and searching for and trying solutions mentioned in the community, I have the drivers for "windows hello face software device" and "bluetooth low energy GATT compliant HID device" fixedhad code 19 errors. Now the search function in the toolbar does not accept input, and the windows Icon to the left will not acc

:)

 

Windows 20H2 update seems to have broken Windows Hello Face Recognition

With the recent update to Windows 20H2 (version 19042.572), the Windows Hello no longer works with the Logitech BRIO 4K camera. I have uninstalled and reinstalled the drivers, disabled and re-enabled Windows Hello. The BRIO works fine with Teams, Skype,
Windows Camera, Logitech Capture, and Logitech Camera Settings. The problem ONLY occurs with Windows Hello. It had worked fine for years prior to the 20H2 update.

Also, Windows Hello works fine with the fine with PIN and with my fingerprint scanner. Only facial recognition is now broken.

So BRIO works with apps other than Hello and Hello works fine with everything but facial recognition via the BRIO 4K, but the combination of BRIO + Windows Hello broke with the latest Windows update.

Is this working for anyone with the same configuration?

The error message Windows Hello gives is, "Sorry something went wrong. Camera is currently in use by another app. Close the app and try again." But nothing else is using the camera (proven by the fact that all the apps listed above will launch and use
the camera just fine).

One other note, which may be helpful diagnostically: when Hello is trying to scan for my face, the red light on the BRIO does flash for several seconds as if it's working, but no picture ever comes through. There is obviously at least some successful communication
between Hello and the BRIO.

I also tried plugging the BRIO both directly into different USB ports on the computer and into various hubs. Always got exactly the same results.

Any suggestions? Do we need to wait for a patch from MS to fix this defect in 20H2?

Thanks,
Colin

 

20H2 system files corrupted on a clean Windows installation sfc /scannow

Hi,

I have noticed that sfc /scannow corrected system files. I wonder. So I tested again on a clean Windows 10 20H2 installation and run directly after sfc /scannow.

Preparation for testing:

• I used VMware Workstation 16.0.0
• I created a new virtual machine with default Windows 10 profile
• I disabled the Network Adapter, the OS has
  no internet the whole process
• I used the latest official Windows 10 ISO file Win10_20H2_English_x64.iso (md5: e80f6ce987b2bba288469e7379129e12) Build 19042.508
  
• Mounted the ISO in VMware

Installation:

• So I started to install Windows 10
• Install Now, No product key, Windows 10 Home, Language en-us, install on the unformatted 60GB drive etc.
• After reboot, I used "no internet" for local Account, name: admin, no password, disabled all the telemetry trash

After successful start, I started directly cmd.exe with administrator privilegs and run sfc /scannow.

It will found corrupted systems files.





It didn't let me post the log here, so I made a Screenshot.

What is going on here?

I repeated the steps with de_windows_10_business_editions_version_20h2_x64_dvd_ce126f3b.iso (md5: 35df62707e53c2064641ccd5b91acb8d)

Type license: Enterprise

After repeating the steps above, the result is the same.

 

Windows 10 Update broke my computer

Can confirm 20H2 "breaks" the drive where none of the suggested recovery options work whatsoever.

Even a recovery USB and the like.

My wifes desktop (work) and my laptop (work)both died after updating with no recocery availability.

Even the download option doesnt work including every option on this list.