Intel RealSense F200 Not Working with Windows Hello on Windows 24H2

I will follow the steps you mentioned if my PC forces me to update to 24H2, which I doubt will happen. For now, I prefer to cancel the update. Honestly, it would be better if Microsoft made a major announcement allowing users on 23H2 to pause the update until they provide better fixes before upgrading to 24H2. This situation is a serious mess.

My 2 pcs Intel RealSense F200 is currently using the drivers shown in the screenshot on 23H2. This camera has been discontinued by Intel. This camera was custom made and due to its size and side-mounted USB 3.0 port, it is best suited for desktop setups, particularly with multiple monitors. However, after upgrading to Windows 24H2, these drivers no longer seem to work with Windows facial recognition. Windows should ensure that existing functionality remains intact in future updates, rather than breaking previously working features. Intel Driver & Assistant Support can not see the F200 in my computer. Until today both my Desktop still using 23H2.

Hi,

I’m sorry, but I can’t reproduce the issue using the guide you mentioned. As I already followed the instructions from this URL (https://os.click/en) the guide was from (****blog/create-windows-11-bootable-usb-23h2/) to revert to the Windows 11 23H2 ISO and created the bootable USB using Rufus. Everything worked fine.

I’ve been troubleshooting this issue for weeks now, but I still haven’t found a good solution.

To clarify:

• The camera is detected normally in Device Manager, and no apps are using or locking the camera.
• After installing Windows, I immediately opened the Camera app or tried signing in using facial recognition, but neither worked.
• I’m not using an administrator account. I created and signed in using either a local account or my Microsoft account.

This clearly indicates an issue with facial recognition not the camera itself and also probabbly 24H2 not working with many existed 3D camera.

My PCs are mini PCs from Beelink (GTR5) and Minisforum (HX99G), both using the USB3.0 connect to Intel RealSense F200 camera not just using regular USB2.0.

These aren’t branded PCs or laptops that Microsoft typically focuses on, but they are still valid devices on the market. The development team for the 24H2 update seems to have overlooked proper testing for existing hardware, which is frustrating for users.

Hi Kirito,

Thank you for your detailed response. However, the issue does not appear to be with the camera driver itself. The camera is detected as normal in Device Manager with no errors.

The problem lies with Windows Hello's facial recognition. I am unable to set up a PIN during the facial recognition setup. The Camera app is also unable to open my camera, showing the error code: "0xA00F4243 (0xC00D3704)".

I have already attempted to remove and reinstall the Camera app via PowerShell with the following commands:

This problem started occurring around November or December when the Windows update 24H2 was requested. I have two computers using the same camera. When I rolled back to 23H2 using a USB media creation tool (MediaCreationTool_Win11_23H2.exe) (https://go.microsoft.com/fwlink/?linkid=872132) provided by your colleague in Feedback Hub, there were no issues. The first computer has been running 23H2 without any camera problems.

However, when I recreated the USB media creation tool this month to the same USB pendrive and applied it to the second computer, it seemed to force the installation of 24H2 rather than 23H2. Even though I skipped the entire setup using unattended installation (Ctrl+Shift+F3) during initial setup, the Windows version under "About" shows 24H2, not 23H2. Consequently, the second computer's facial recognition no longer works with the camera.

Windows should maintain backward compatibility with existing hardware. However, it seems that the 24H2 update has caused multiple functionalities that previously worked to break.

No matter what I tried, when I recreated the USB creation image from the provided URL, it seems the USB creation was forced to install 24H2 instead of 23H2. During the installation, Windows becomes 24H2, not 23H2. I don't want to use 24H2 because many things lost my computer capabilities.

The developer engineering of this 24H2 has failed to understand what is already existed to carry forward intead making all mess up.

I appreciate your assistance and look forward to resolving this issue.

Feel free to adjust any part of this message as needed! 😊

Hello Frenky Tan1 and welcome to the Microsoft Community!

Based on your feedback, you are experiencing an issue with the Intel RealSense F200 camera not working with Windows Hello on Windows 24H2.

We're happy to help.

Sometimes system updates can overwrite the drivers for certain devices

Click on the windows key > search and open Device Manager > find the camera driver > Update

See if the problem is fixed

If it still doesn't work, you can uninstall the webcam driver in the device manager.

Reboot your computer

Then click on the URL below:

Intel® Driver & Support Assistant

Disclaimer: Microsoft provides no implied or other warranties and/or guarantees, and is not responsible for the information you obtain from third-party linked sites or for any technology-related support.

At this URL they will automatically detect the device's drivers and update them!

See if it solves your problem

If the above solutions don't solve your problem

You can try uninstalling the update first

Click on windows key > settings > windows update > update history > uninstall update

and see if it solves your problem.

If the problem is solved, you can disable the automatic update of the driver by the following method

Method 1: Using the Control Panel

1. Open the Control Panel.
2. Select System and Security > System.
3. Click Advanced System Settings on the left.
4. On the Hardware tab, click Device Installation Settings.
5. Select No (your device may not work as expected), and then click Save Changes.

Method 2: Using the Group Policy Editor

1. Press Win + R to open the Run dialog box, type gpedit.msc and press Enter.
2. Go to Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions.
3. Double-click Disable installation of devices not described by another policy, select Enabled, and then click OK.
4. Go to Computer Configuration > Administrative Templates > Windows Components > Windows Update.
5. Double-click Windows Update excluding drivers, select Enabled, and then click OK.

Method 3: Use Registry Editor

1. Press Win + R to open the Run dialog box, type regedit and press Enter.
2. Navigate to the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching. 3. Double-click SearchOrdering.
3. Double-click SearchOrderConfig, change its value to 0, and then click OK.

Disclaimer: Modifying the registry or workgroups is usually geared towards advanced users, administrators, and IT professionals, and it can help to fix some problems, however, improper registry modifications can lead to serious problems. Therefore, please make sure to follow the steps below strictly. For further protection, make a backup of the registry before modifying it. For more information on how to backup and restore the registry ref:https://support.microsoft.com/en-us/topic/how-to-back-up-and-restore-the-registry-in-windows-855140ad-e318-2a13-2829-d428a2ab0692

After disabling the update system from automatically updating the driver, see if you still have the problem after the update

We look forward to hearing from you.

Kirito|Microsoft Community Support Specialist