How to fix the service/driver in Windows 10 1903 for F200 camera?

[wma001]

After updated to Windows 10 1903, I found that F200 camera could not be used.

While I'm trying to re-install the driver, it seems like works properly.

As I lunch the Camera app from Start Menu, it shows "Close other apps" with error code "0xA00F4243(0xC00D3704)".

Then I checked the Services, the "Intel(R) RealSense(TM) Depth Camera Manager Service" could not start, the dialog shows "Windows could not start the Intel(R) RealSense(TM) Depth Camera Manager Service on Local Computer. Error 0x80010119: Security must be initialized before any interfaces are marshalled or unmarshalled. It cannot be changed once initialized."

What can I do now?​

[MartyG]

This is the first time that I have heard of this particular error. My research indicates that it occurs when there has been some problem, such as a file corruption, during an update of Windows to a new version. It has been occurring in Windows for some years, at least as far back as Windows 8.

A discussion on the Microsoft support forum offers a couple of methods to try.

https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/build-10074-error-0x80d02002/8ec7e4e5-1f00-4dc7-b441-9d6ad2c6288d

I would first though recommend trying to fix it through the Windows Troubleshoot tool. You can find this by typing 'troubleshoot' into the text box at the bottom of your Windows screen, next to the button where you shut down.

Once the Troubleshoot window appears, select the 'Windows Update' option to begin troubleshooting it. Please left-click on the image below to view it in full size.

[wma001]

I have tried to do a clean install both windows 10 1809 and 1903, the drivers of the camera both installed right. But the "Intel(R) RealSense(TM) Depth Camera Manager Service" does not, it can run in 1809 but can't in 1903.

[MartyG]

The next thing I would look at is whether camera-related apps are being blocked by Windows' "Privacy" settings. Type 'privacy' into the bottom text box to find the Privacy Settings window and select 'Camera' from the side-panel. Check that 'Allow access to the camera on this device' is set to On, and that 'Allow apps to access your camera' is also set to On.

[DOliv23]

I’m seeing the same issue after upgrading to Windows 10 1903. The camera worked without issue in 1809.

[wma001]

I've seen the same problem in Microsoft Community, it happened on 1803 or 1709 whatever.

In that topic, it says that there are several topics about that problem in Intel Community.

I came here and found nothing.

But my camera just cannot work in 1903.​

[MartyG]

Historically, major updates to new Windows builds do unfortunately sometimes render RealSense cameras non-functional. In these cases there may be nothing to be done but to hope that it works again in a subsequent Windows build, as the problem is on Microsoft's side of things and not fixable by Intel. 

The only course of action in these situations where the problem cannot be fixed by the user using methods such as the ones suggested above may be to roll Windows back to the previous version and turn off automatic installation of downloaded updates so that Windows cannot re-update without your permission to the build that breaks the camera.

There is a guide to rolling back Windows at the link below.

https://www.howtogeek.com/235474/how-to-roll-back-builds-and-uninstall-updates-on-windows-10/

[wma001]

Thanks, I know what you mean and I've tried your solution given above.

Troubleshot did not work, it tells me "couldn't identify the problem".

Privacy options are turned ON by default.

So the problem is the problem, nothing changed and nothing effected.

I don't know if you have a realsense camera by yourself, would you please to try this action?

Stop the "Intel(R) RealSense(TM) Depth Camera Manager Service" and see if the Camera App and Windows Hello will work without restart it.

[MartyG]

I reinstalled my F200 camera and tested it in the way that you requested, running on Windows Build 17134 (the version currently installed on my computer, which corresponds to the April 2018 update).

The camera functioned fine in the RealSense 'Camera Explorer' test app (which is installed in addition to the standard Windows 'Camera' app if the '2016 R2' or '2016 R3' RealSense SDK is installed). Stopping the DCM service froze the stream in the Camera Explorer and then caused an error message to appear.

Likewise, the RGB camera of the F200 worked fine in the standard Windows 'Camera' app, froze when the DCM was stopped and re-started when the DCM was set in motion again.

[wma001]

It seems that service is important for the camera to function properly.

And the service runs without any error by my experience before 1903.

Will you install a virtual machine with Windows 10 1903 and connect the camera to the VM and see if the error code mentioned above exists?

[wma001]

Anyway, many thanks to your reply.

You are the ONLY one I've met in these two communities of Wintel Corp whom willing to help others getting problem of realsense settled down.

[asava]

(double post, sorry)

[MartyG]

Thank you for your kind words. I do not have the ability to set up a virtual machine on my PC, unfortunately. I did research the subject further though on the old RealSense forum (there was a RealSense forum on the Intel Developer Zone that existed before this one). I found an F200 case from 2016 on it with the same error that you experienced.

https://software.intel.com/en-us/forums/realsense/topic/611965

[asava]

Hello,

I would like to add, that after upgrading to 1903, exactly the same error (with the same error in Event Viewer), appears also for the RealSense SR300 camera - so this problem is not limited to the RealSense F200 model.

The SR300 camera worked perfectly before in 1809.

I hope a fix will come soon.

Thanks!

[MartyG]

I will link this case in to a couple of the Intel Support support-team agents who work on this forum to draw it to their attention.

@ElizaD_Intel​ @AlexandruO_Intel​ 

[asava]

Here's a method to make Windows Hello work *temporarily* (until reboot):

* Enter Device Manager -> Cameras -> Right click "Intel RealSense Camera <model> RGB" -> Disable device

* Enter Services -> Right click "Intel RealSense Depth Camera Manager Service <model>" -> Start

* Enter Device Manager -> Cameras -> Right click "Intel RealSense Camera <model> RGB" -> Enable device

So, when the RGB camera is disabled, the Depth service starts successfully for my SR300. Then, after re-enabling the RGB camera, Windows Hello is functional (until the next reboot).

This is obviously not a solution, as it is most needed when computer starts. But perhaps it could serve as a hint to developers / staff of what's going on.

wma001, does this work for your F200 also?

[Alexandru_O_Intel · Accepted solution]

Hello wma001, Unfortunately, the Depth Camera Managers for both F200 and SR300 have known issues in Windows 10 that prevent them from being fully functional after each Windows Update and they are no longer supported. Please see some of these troubleshooting articles, which may help: https://www.intel.com/content/www/us/en/support/articles/000026184/emerging-technologies/intel-realsense-technology.html https://www.intel.com/content/www/us/en/support/articles/000023560/emerging-technologies/intel-realsense-technology.html Some more troubleshooting includes to reinstall the camera driver:  https://www.intel.com/content/www/us/en/support/articles/000023694/emerging-technologies/intel-realsense-technology.html   There are many workarounds posted in the RealSense Community but they don't work for all users. https://forums.intel.com/s/question/0D50P0000490MWqSAM/how-to-get-sr300-working-on-windows-10-build-1703-including-sdk-apps-such-as-segmentation-updated-5172017 Best regards, Alexandru

[NTsar2]

Similar problem here, with RealSense D435 camera.

To be honest, it's not practically possible to search for each computer component's compatibility before applying a Windows update. Vice-versa, if one were to roll back to previous version of windows, how would he/she know when it is possible to safely proceed with the update?

I have already reported the issue to Microsoft (Case number: 1476811164).

It would help if all of us who experience this issue opened a Microsoft Support case and complain about Windows Update breaking compatibility with operational software.