topic Cannot Uninstall RealSense in Software Archive

Cannot Uninstall RealSense

Roger_C_ — Sun, 17 Jan 2016 09:58:54 GMT

Hi,

I have a brand new Asus Zen Aio Z240ic, which comes with an integrated RealSense camera identifying itself as an F200. The camera doesn't work. In an attempt to troubleshoot the problem I wish to uninstall the full software set and reapply the drivers. This is because there are numerous (apparently conflicting) installation entries in Device Manager:

Amongst these, you'll note that the version number of one (52404) is higher than any generally available release. As an aside, if I try to install/update the drivers with the Asus or Intel latest release the installation fails, telling me that a newer version is installed.

Anyway, my uninstallation attempts always fail (whichever package I try to uninstall) with an error dialog that states that integrity checking has failed - illustrated below. How can I manually remove this software?

I gather you're on Windows 10

Colleen_C_Intel — Mon, 18 Jan 2016 00:37:20 GMT

I gather you're on Windows 10? I've seen others with 2 versions of the DCM and found if there were issues, to uninstall both versions (or do you get that error message on both?) and then let Windows update add the driver back in. If it continues to fail, go to Local Services and make sure both sets of the DCM are stopped if they are listed there (under Intel Real Sense Depth........)

You should also be able to at least disable the cameras (should have 3 entries) under Device Manager - Imaging Devices. Try to uninstall from there, or at least disable and reboot.

Thanks - all of the entries

Roger_C_ — Thu, 21 Jan 2016 14:30:26 GMT

Thanks - all of the entries in the Control panel gave the same validation error that was preventing uninstallation. Luckily, as this was a newly purchased machine this issue added to a list of things that I was unhappy with about the Asus software build and so I came to the conclusion that I would have to rebuild the machine using a plain Windows 10 from MSDN.

Other posts on this forum forewarned me to use a build that had the November update baked in and doing so has pulled down a clean set of drivers.