Logitech Brio stop working after windows 11 build 22581 update (Beta channel)
Hello, I've just installed Windows 11 build 22581 from the Windows Insider Beta channel last night. Since then, my Logitech Brio camera stop working. My Logitech Brio was configured on my computer for Windows Hello facial authentication, so I'm sure it was working just fine before the update since I use it each time I'm logging in. I've tested the camera on antoher compter, it works fine. I've updated the camera to the latest firmware on this other computer just in case, but it doesn't help. Back on my main computer, the camera still appears in the Device Manager, but the device is not accessible from apps like the Camera app. I've tried the uninstall the device, then perform a scan to add it back in. The device is added but is not working... When I try the "Restore driver" option, it says that "the driver is not build for this plateform" Finally, I've tried to switch from the Beta to the Dev channel, just in case a fix was already available. But this seems not to be the case. So here I am Thanks in advance for you help.
Disable "Windows Hello"
I am an admin, and attempting to disable "Windows Hello for Business" also referred to as 2-step authentication. From what I gather, this option is set as "disabled" by default. I confirmed this. However Whenever I join a device to Azure AD, it is always prompted with "Windows Hello" and to create a pin. Where can I find the option that allows me to disable this?How to suspend execution until excel workbook 100% synced with Microsoft forms
I have a PowerShell script that's extracting cell values from a table that's synced to a Microsoft Form. However, when I run the script in the morning it's extracting the cell values before the forms is 100% synced so I'm not getting all of the data from the day before. I can sleep the script for maybe 20 seconds but is there a way to suspend execution of the script until the forms is 100% synced then immediately continue execution because sometimes it's already synced and other times it's not? # create excel instance $excel = new-object -comobject excel.application # open excel workbook try { $workbook = $excel.Workbooks.Open($filePath, $true) } catch { throw "microsoft excel cannot access file -> please run the script again" } # set excel worksheet $worksheet = $workbook.Sheets.Item(1) # set excel table $table = $worksheet.ListObjects.Item("Form") # extract cell values $values = @() for ($i = 9; $i -le 15; $i++) { foreach ($cell in $table.Range.Columns.Item($i).SpecialCells(12).Cells) { $values += $cell.Value2 | Where-Object { $_ -match "^\d" } } }
Windows hello for business for Hybrid Entra Join
Environment: -No UPN matching between onprem AD and Azure, Third party federation and User provisioning . -Hybrid Entra Joined devices -Enrolled to Intune using device credentials as SCCM is setup with co management (Cloud Attach). Question: Whether setting up Windows hello for business (Which was working before enrollment) using GPO / or Intune. An error is returned. Pin: "this sign in option is only available when connected to your organization's network" "Fingerprint and Face" "The option is currently unavailable" Multiple methods to setup WFH was attempted and none worked so far. -Devices -> Win 10 -> Enrollment -> "Configure Windows hello for business" -Using Custom settings as described here(CSP or GPO): https://learn.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/configure -Biometrics devices updated/ Windows updates installed/ All devices and users affected in the organization. -What could be the issue? Any best effort to get the windows hello for business working again?Windows 11 Update error 0x80240067
I am getting Windows Update error. Using Windows 11 24H2. OS Build 26085.1. Already performed troubleshooting steps like Dism and Sfc, resetted Windows components too but nothing is taking any effect. Another issue is also with Windows Hello face recognition is not working. Error message" There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80240067)"
Disabling pin while keeping windows hello enabled
We would like to keep the use of windows hello biometrics but instead of a pin, could I force the Microsoft account password? Due to some security requirements, devices are required to have a 14 alphanumeric password with special characters. This gets pretty annoying when we have our devices lock after a minute of inactivity which is why we keep windows hello enabled. If we have pin enabled, it would have to meet the password requirements of 14 characters yada yada. The problem with that would be confusing the end users by having multiple long passwords. Is there a way to have windows hello enabled but instead of the local pin, have the microsoft account password be used instead?
Feature request: Windows Hello prompts for a fingerprint when the fingerprint reader is unavailable
I'm running Windows 11 on a laptop that is connected to an external monitor. The lid of the laptop remains closed. When Windows Hello activates it defaults to requesting a fingerprint even though the fingerprint reader is inaccessible (again, the lid is closed). If the laptop's lid is closed Windows Hello should default to either a pin or password. I have Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\LidReliablityState set to 1.manage Interactive logon & Windows Hello multi-factor unlock
Hi everyone, We're going step by step on the passwordless strategy from Microsoft. Windows Hello multi-factor unlock is deployed in a Pilot Group but now I have two questions, which I hope someone here can answer. Question 1: disable Windows Hello multi-factor unlock Managed to enable WHMFU over custom OMA-URI Settings. But how can I disable it again? I tried it with a second custom OMA-URI Settings configuration profile which is configured as follows: It works, but it seems, that it isn't disabled correctly. Sometimes I still get a message in the logon process which says something like "additional factor needs to verify" but it displays very quickly, and I verified that I can log on with only one factor again. Disabling the second unlock factor is configured like this as well. Question 2: Enable "Interactive logon: Require Windows Hello for Business or smart card" We want to enable this security option. However, Intune doesn't offer to manage this setting. So, I think that I must enable this over a custom OMA-URI Setting too or PowerShell script. How can I achieve this? Thanks so much for any support ❤️[LTSC] Windows Hello Facial Recognition - Installation OR Repair
Hello Tech Community, Recently, I discovered that Windows Hello Facial Recognition is either disabled or removed from Windows 10 Enterprise LTSC 2021 (21H2), and after a skim of the archives, could not find any method to install Windows Hello to these devices. Q: Are/Is the device(s) in question compatible with Windows Hello Facial Recognition? A: They are by the OEM, claiming that an IR module is specifically installed in each unit with compatibility guaranteed. Q: Are/Is the device(s) in question using the correct Windows Hello Facial Recognition-compatible driver? A: The drivers have been installed in full, and Windows prompts users to set up Windows Hello Facial Recognition rather than reporting that no compatible device is installed. Q: Are/Is the device(s) in question affected by any OEM/user modifications which could inhibit Windows Hello's ability to function properly? A: Microsoft Edge has been uninstalled (using the built-in uninstaller bundled with LTSC 2021) from the device(s), however no non-standard (including Enterprise-specific) settings/programs have been altered outside of that. Q: What issue is occurring when attempting to configure Windows Hello Facial Recognition on the device(s)? A: The introduction to Windows Hello Facial Recognition simply force-stops/crashes when Get Started is pressed, as if an application is not present. This may also be a missing Universal Windows Program (.uwp), as no other UWPs are present in this install, as far as I'm aware. My question to you: Is it possible to install or repair Windows Hello (the combined package, preferably) to this installation of Windows 10 Enterprise LTSC? Thank you, MakeineerWindows Hello Issues after Feature Upgrade
Hello Everyone! I need some ideas and suggestions what I can still check and try to solve the Windows Hello problem. Long-Story-Short After each upgrade to the next Windows 10 feature release, Windows Hello no longer works for some clients of my customer (face recognition / PIN / fingerprint). So far this could always be solved quickly by some workarounds. Since the upgrade to 1903 only a new installation helps. It's extremely frustrating. We have no idea where it comes from and don't know what we can do anymore. So that we need new ideas and experiences from you. The related Event - Application Error ID 1000 Faulting application name: BioEnrollmentHost.exe, version: 10.0.18362.329, time stamp: 0x5d65c2f4 Faulting module name: twinapi.appcore.dll, version: 10.0.18362.1, time stamp: 0x42f071ca Exception code: 0xc000027b Fault offset: 0x00000000000d5cc8 Faulting process id: 0x2ee0 Faulting application start time: 0x01d59ebf5f477f66 Faulting application path: C:\WINDOWS\SystemApps\Microsoft.BioEnrollment_cw5n1h2txyewy\BioEnrollmentHost.exe Faulting module path: C:\Windows\System32\twinapi.appcore.dll Report Id: 4779daff-5de6-4384-b220-bf648b2577fa Faulting package full name: Microsoft.BioEnrollment_10.0.18362.387_neutral__cw5n1h2txyewy Faulting package-relative application ID: App Involved devices #Microsoft Surface Pro 4 / #Surface Pro 6 #Lenovo T470 What helped so far Repair Windows Apps via Powershell Reset and new setup of Windows Hello (PIN and Face or Fingerpint) Reset the Microsoft Passport Container (NgcCtnrSvc) Service and the NGC Folders Firmware and Driver Update What's new after upgrading to 1903 None of the previous solutions/workarounds helps New users who have not yet logged on to the client can use Windows Hello TPM Reset does not help Deleting the affected user profile does not help Deleting the affected user profile in addition search and delete every User-SID related RegKey does not help I can't believe it's just us who have the problem.
