Windows 10: Updated to 20H2, now Windows Hello does not work. Searching the error returns only scammer...

submitted by /u/dicktuck
[link] [comments]

:)

 

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

 

Error: No work available to process

Hmm. Either it's put out errors and WCG is limiting the work units available, or the project list may not be set to supply other WU when one runs out. (if the problem lies here and not on your end)

On the options to your left, if you go into Results Status, select the computer from Device Name and then look through results see if either they were returned late, errors or any other kind of issue that would stop the servers supplying WU from that perspective.

If there are no errors then it's maybe down to your project list. So selecting Device Manager from the left menu and then clicking on the profile assigned to that computer and make sure that it's assigned to receive WU for other projects if they run out.

At least those steps will rule out problems from the WCG end.

 

windows 20h2 update issue

Hi, I'm Israel M., I'm an independent consultant and I'm happy to help you.

The update of Windows 20h2 is carried out cumulatively, correcting errors the focus was to correct problems seen until then, being made available by Microsoft an extensive list (almost 50 items cited by the company), thus showing that this update promises to
regularize a good part of the image that reaches users of the distribution. Therefore, these constant updates are corrections.

I hope I helped, I await your return.

Best regards,

Israel M.

Outside consultant