none
Kinect SDK Windows 10 SETUP FAILED Error - NEED HELP RRS feed

  • Question

  • Hi, i upgraded my windows 7 to windows 10 using the free upgrade online.  I setup my kinect 2.0 downloaded the SDK 2.0 (Both run time and SDK). When trying to install, it keeps on giving me an error.  It says 'Setup Failed an error occurred. Please check log files blah blah...' It just does not INSTALL. I am an animator and i really want this to install so i can use it for animation.

    Guys...I am soo frustrated, it's taking the mick! I did everything to my knowledge, deleted everything, fresh install, it just don't make sense.  Only once i got the Kinect Configuration verifier to install, after that it failed to work and i uninstalled it, tried re-installing it again but did not work.  Keeps giving me an error.  Why Is it SUCH A PAIN IN THE BUTT to install this?! Come on Microsoft! I have three Installation files - 1)  'KinectRuntime-v2.0_1409-Setup.exe'  2) 'KinectSDK-v2.0_1409-Setup.exe' and 3) 'KinectConfigurationVerifierSetup.exe'

    Can somebody plz help me, i can send the log files, I hope Microsoft makes this easy to install because it is driving me crazy.

    Thanks for your time guys!

    Jay

    Monday, June 5, 2017 12:26 AM

All replies

  • Does the setup mention the error code?
    Monday, June 5, 2017 6:28 PM
  • Hey! Sorry for the late reply, unfortunately it does not mention the error code 'Just says SetUp Failed an error occurred' With Plenty of Log files that I don't have a clue what it means.
    • Edited by Jamil1985 Sunday, June 11, 2017 12:21 PM
    Sunday, June 11, 2017 12:20 PM
  • Could you post those log files? We should be able to find out the error code there.

    If you cannot get those logs, create a .bat file beside the Kinect runtime/sdk setup file and paste the following inside it(you can edit it as a text file).

    <write_setup_file_name_with_.exe_here> -l log.txt

    After replacing the <> part with the setup filename, double click it to execute and proceed with the installation as you would. After it fails and closes, you will see a log.txt in the same folder. Post that one here.

    Sunday, June 11, 2017 1:34 PM
  • [3FF0:2F68][2017-06-05T01:03:26]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: G:\Downloads\KinectSDK-v2.0_1409-Setup.exe, cmdline: '-burn.unelevated BurnPipe.{4723939E-02BB-498E-9AE7-7C40FD78A33B} {22BECE7B-50D4-402E-854C-539ACC656D43} 10704'
    [3FF0:2F68][2017-06-05T01:03:26]i000: Setting string variable 'WixBundleLog' to value 'G:\TEMP\Kinect_for_Windows_SDK_v2.0_1409_20170605010326.log'
    [3FF0:2F68][2017-06-05T01:03:26]i000: Setting string variable 'WixBundleOriginalSource' to value 'G:\Downloads\KinectSDK-v2.0_1409-Setup.exe'
    [3FF0:2F68][2017-06-05T01:03:26]w055: Could not load or read state file: C:\ProgramData\Package Cache\{2f7f3dc4-de9a-4605-821f-b686f26392d8}\state.rsm, error: 0x80070003.
    [3FF0:2F68][2017-06-05T01:03:26]i000: Setting string variable 'WixBundleName' to value 'Kinect for Windows SDK v2.0_1409'
    [3FF0:2F68][2017-06-05T01:03:26]i000: Loading managed bootstrapper application.
    [3FF0:2F68][2017-06-05T01:03:26]i000: Creating BA thread to run asynchronously.
    [3FF0:2F68][2017-06-05T01:03:27]i100: Detect begin, 5 packages
    [3FF0:2F68][2017-06-05T01:03:27]i000: Setting string variable 'VCRTx64Installed' to value '1'
    [3FF0:2F68][2017-06-05T01:03:27]i000: Setting string variable 'VCRTx86Installed' to value '1'
    [3FF0:2F68][2017-06-05T01:03:27]i052: Condition 'VCRTx86Installed' evaluates to true.
    [3FF0:2F68][2017-06-05T01:03:27]i052: Condition 'VCRTx64Installed' evaluates to true.
    [3FF0:2F68][2017-06-05T01:03:27]i101: Detected package: VCRTx86, state: Present, cached: None
    [3FF0:2F68][2017-06-05T01:03:27]i101: Detected package: VCRTx64, state: Present, cached: None
    [3FF0:2F68][2017-06-05T01:03:27]i101: Detected package: x64Runtime, state: Present, cached: None
    [3FF0:2F68][2017-06-05T01:03:27]i101: Detected package: x64SDK, state: Absent, cached: None
    [3FF0:2F68][2017-06-05T01:03:27]i101: Detected package: x64Drivers, state: Present, cached: None
    [3FF0:2F68][2017-06-05T01:03:27]i199: Detect complete, result: 0x0
    [3FF0:2F68][2017-06-05T01:03:29]i200: Plan begin, 5 packages, action: Install
    [3FF0:2F68][2017-06-05T01:03:29]w321: Skipping dependency registration on package with no dependency providers: VCRTx86
    [3FF0:2F68][2017-06-05T01:03:29]i052: Condition 'VersionNT64' evaluates to true.
    [3FF0:2F68][2017-06-05T01:03:29]w321: Skipping dependency registration on package with no dependency providers: VCRTx64
    [3FF0:2F68][2017-06-05T01:03:29]i052: Condition 'VersionNT64' evaluates to true.
    [3FF0:2F68][2017-06-05T01:03:29]i052: Condition 'VersionNT64' evaluates to true.
    [3FF0:2F68][2017-06-05T01:03:29]i000: Setting string variable 'WixBundleRollbackLog_x64SDK' to value 'G:\TEMP\Kinect_for_Windows_SDK_v2.0_1409_20170605010326_0_x64SDK_rollback.log'
    [3FF0:2F68][2017-06-05T01:03:29]i000: Setting string variable 'WixBundleLog_x64SDK' to value 'G:\TEMP\Kinect_for_Windows_SDK_v2.0_1409_20170605010326_0_x64SDK.log'
    [3FF0:2F68][2017-06-05T01:03:29]i052: Condition 'VersionNT64' evaluates to true.
    [3FF0:2F68][2017-06-05T01:03:29]i201: Planned package: VCRTx86, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
    [3FF0:2F68][2017-06-05T01:03:29]i201: Planned package: VCRTx64, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
    [3FF0:2F68][2017-06-05T01:03:29]i201: Planned package: x64Runtime, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: Register
    [3FF0:2F68][2017-06-05T01:03:29]i201: Planned package: x64SDK, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: Yes, dependency: Register
    [3FF0:2F68][2017-06-05T01:03:29]i201: Planned package: x64Drivers, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: Register
    [3FF0:2F68][2017-06-05T01:03:31]i299: Plan complete, result: 0x0
    [3FF0:2F68][2017-06-05T01:03:31]i300: Apply begin
    [29D0:24B0][2017-06-05T01:03:31]i360: Creating a system restore point.
    [29D0:24B0][2017-06-05T01:03:31]i362: System restore disabled, system restore point not created.
    [29D0:2ADC][2017-06-05T01:03:33]i305: Verified acquired payload: x64SDK at path: C:\ProgramData\Package Cache\.unverified\x64SDK, moving to: C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\KinectSDK-v2.0_1409-x64.msi.
    [29D0:24B0][2017-06-05T01:03:33]i323: Registering package dependency provider: {5045CFA2-C173-4678-82AD-02BFD77ED26A}, version: 2.0.1410.18000, package: x64Runtime
    [29D0:24B0][2017-06-05T01:03:33]i325: Registering dependency: {2f7f3dc4-de9a-4605-821f-b686f26392d8} on package provider: {5045CFA2-C173-4678-82AD-02BFD77ED26A}, package: x64Runtime
    [29D0:24B0][2017-06-05T01:03:33]i323: Registering package dependency provider: {77FBF502-4136-4BC8-B754-6A01C02598C9}, version: 2.0.1410.19000, package: x64SDK
    [29D0:24B0][2017-06-05T01:03:33]i301: Applying execute package: x64SDK, action: Install, path: C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\KinectSDK-v2.0_1409-x64.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
    [29D0:24B0][2017-06-05T01:03:34]e000: Error 0x8007064a: Failed to install MSI package.
    [29D0:24B0][2017-06-05T01:03:34]e000: Error 0x8007064a: Failed to execute MSI package.
    [3FF0:2F68][2017-06-05T01:03:34]e000: Error 0x8007064a: Failed to configure per-machine MSI package.
    [3FF0:2F68][2017-06-05T01:03:34]i319: Applied execute package: x64SDK, result: 0x8007064a, restart: None
    [3FF0:2F68][2017-06-05T01:03:34]e000: Error 0x8007064a: Failed to execute MSI package.
    [29D0:24B0][2017-06-05T01:03:34]i318: Skipped rollback of package: x64SDK, action: Uninstall, already: Absent
    [3FF0:2F68][2017-06-05T01:03:34]i319: Applied rollback package: x64SDK, result: 0x0, restart: None
    [29D0:24B0][2017-06-05T01:03:34]i329: Removed package dependency provider: {77FBF502-4136-4BC8-B754-6A01C02598C9}, package: x64SDK
    [29D0:24B0][2017-06-05T01:03:34]i351: Removing cached package: x64SDK, from path: C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\
    [29D0:24B0][2017-06-05T01:03:34]i326: Removed dependency: {2f7f3dc4-de9a-4605-821f-b686f26392d8} on package provider: {5045CFA2-C173-4678-82AD-02BFD77ED26A}, package x64Runtime
    [29D0:24B0][2017-06-05T01:03:34]i329: Removed package dependency provider: {5045CFA2-C173-4678-82AD-02BFD77ED26A}, package: x64Runtime
    [3FF0:2F68][2017-06-05T01:03:35]i399: Apply complete, result: 0x8007064a, restart: None, ba requested restart:  No
    [3FF0:2F68][2017-06-05T01:27:57]i500: Shutting down, exit code: 0x8007064a
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: VCRTx64Installed = 1
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: VCRTx86Installed = 1
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: VersionNT64 = 6.2.0.0
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: WixBundleAction = 4
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: WixBundleElevated = 1
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: WixBundleInstalled = 1
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: WixBundleLog = G:\TEMP\Kinect_for_Windows_SDK_v2.0_1409_20170605010326.log
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: WixBundleLog_x64SDK = G:\TEMP\Kinect_for_Windows_SDK_v2.0_1409_20170605010326_0_x64SDK.log
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: WixBundleManufacturer = Microsoft Corporation
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: WixBundleName = Kinect for Windows SDK v2.0_1409
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: WixBundleOriginalSource = G:\Downloads\KinectSDK-v2.0_1409-Setup.exe
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: WixBundleProviderKey = {2f7f3dc4-de9a-4605-821f-b686f26392d8}
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: WixBundleRollbackLog_x64SDK = G:\TEMP\Kinect_for_Windows_SDK_v2.0_1409_20170605010326_0_x64SDK_rollback.log
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: WixBundleTag = 
    [3FF0:2F68][2017-06-05T01:27:57]i410: Variable: WixBundleVersion = 2.0.1410.19000
    [3FF0:2F68][2017-06-05T01:27:57]i007: Exit code: 0x8007064a, restarting: No
    Sunday, June 11, 2017 2:02 PM
  • Second Log File:

    === Verbose logging started: 6/5/2017  1:03:33  Build type: SHIP UNICODE 5.00.10011.00  Calling process: G:\Downloads\KinectSDK-v2.0_1409-Setup.exe ===
    MSI (c) (D0:C4) [01:03:33:959]: Resetting cached policy values
    MSI (c) (D0:C4) [01:03:33:959]: Machine policy value 'Debug' is 0
    MSI (c) (D0:C4) [01:03:33:959]: ******* RunEngine:
               ******* Product: C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\KinectSDK-v2.0_1409-x64.msi
               ******* Action: 
               ******* CommandLine: **********
    MSI (c) (D0:C4) [01:03:33:959]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (D0:C4) [01:03:33:959]: Grabbed execution mutex.
    MSI (c) (D0:C4) [01:03:33:962]: Cloaking enabled.
    MSI (c) (D0:C4) [01:03:33:962]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (D0:C4) [01:03:33:965]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (5C:40) [01:03:33:968]: Running installation inside multi-package transaction C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\KinectSDK-v2.0_1409-x64.msi
    MSI (s) (5C:40) [01:03:33:968]: Grabbed execution mutex.
    MSI (s) (5C:C4) [01:03:33:974]: Resetting cached policy values
    MSI (s) (5C:C4) [01:03:33:974]: Machine policy value 'Debug' is 0
    MSI (s) (5C:C4) [01:03:33:975]: ******* RunEngine:
               ******* Product: C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\KinectSDK-v2.0_1409-x64.msi
               ******* Action: 
               ******* CommandLine: **********
    MSI (s) (5C:C4) [01:03:34:138]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (5C:C4) [01:03:34:142]: Unexpected or missing value (name: 'PackageName', value: '') in key 'HKLM\Software\Classes\Installer\Products\205FBF7763148CB47B45A6100C52899C\SourceList'

    MSI (s) (5C:C4) [01:03:34:143]: MainEngineThread is returning 1610
    MSI (s) (5C:40) [01:03:34:144]: User policy value 'DisableRollback' is 0
    MSI (s) (5C:40) [01:03:34:144]: Machine policy value 'DisableRollback' is 0
    MSI (s) (5C:40) [01:03:34:144]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (5C:40) [01:03:34:144]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (5C:40) [01:03:34:144]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (5C:40) [01:03:34:145]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (D0:C4) [01:03:34:146]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (D0:C4) [01:03:34:146]: MainEngineThread is returning 1610
    === Verbose logging stopped: 6/5/2017  1:03:34 ===

    Sunday, June 11, 2017 2:03 PM
  • Not entirely sure but I think in between the install/uninstall attempts, something has been left in the registry and blocks subsequent attempts.

    Can you post a screenshot of the keys under the "HKLM\Software\Classes\Installer\Products\205FBF7763148CB47B45A6100C52899C\SourceList" tree in the registry? Or tell us whether anything relating to Kinect exists among them?


    Sunday, June 11, 2017 2:47 PM
  • In The '....Source-list' there are Two folders. One called 'Media' and the other is named 'Net'.  The 'Net' folder contains two items 'Default' and '1' and same applies to the 'media folder'.  I tried print screening and uploading an image but the forum goes apparently i have to verify? So i cannot upload.
    • Edited by Jamil1985 Sunday, June 11, 2017 4:33 PM
    Sunday, June 11, 2017 4:32 PM
  • Yeah you'd have to post it to Dropbox or Google Drive or somthing.

    Aren't there any keys when Source is selected?

    Sunday, June 11, 2017 9:21 PM
  • Hi, sorry for my late reply, im juggling between work and only get to reply when I get some time in-between.  I really do appreciate your help.

    Okay, yes, when i select the SourceList folder there are two items that show up in the right panel. One is called 'Default' and the other is 'LastUsedSource' with a long combination of ---------  n;1;C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\ 

    Thanks.

    Monday, June 12, 2017 9:10 AM
  • Can you check whether that directory exists and if there are files in there?(PackageCache is hidden so paste the full path in the FileExplorer and wait for the admin rights prompt to enter that directory).

    If there is an msi there whose modification date is older than your last attempt to install the SDK,you will probably have to empty that LastUsedSource value. Or even delete it entirely, leaving Default alone.

    LastUsedSource looks like it has garbage values prior to that full path. You could export the "Source" tree node to a .reg file and then try to delete LastUsedSource, so that if something goes wrong you can return it to that state by running that .reg file which will write that key again.

    But my guess is that if you remove that key it will probably fix itself. For good measure you should remove that {77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\  as well from PackageCache.

    PackageCache is the folder where all installation packages are stored by Windows, which Add & Remove displays in the list of uninstallable applications.Somewhere along the installation/uninstallation attempts the process was probably aborted/cancelled and that corrupted the installation registry. You can't see the application in the list to uninstall it manually, but it's still registered as installed. So the new installation attempts get blocked by that. At least that's my guess. I once did this in my dev machine, trying to do something on the uninstallation part of an installer(msi based) and had to manually remove stuff, but it's been long since and not sure if it was the same kind of mess.


    Monday, June 12, 2017 9:23 AM
  • Hi, The folder was not hidden, i located the folder 'C:\ProgramData\Package Cache'.  Inside the folder 'Package cache' there is a folder named with a Long number: {050d4fc8-5d48-4b8f-8972-47c82c46020f}

    Inside the folder there are two items:

    'state.rsm' and 'vcredist_x64.exe'

    Monday, June 12, 2017 9:41 AM
  • Ok, then the absence must be the problem.Like I said, the registry value says there is an uncompressed version of the msi in the PackageCache which was last used so the setup tries to use that but it doesn't exist in reality so it fails.

    Export "Source" node to .reg file somewhere. Then empty the value "---------  n;1;C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\" and retry the SDK setup.

    In case that fails, double click the reg file to rewrite the "---------  n;1;C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\" and instead of emptying it just remove ";C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\" from the end. And then retry the setup.

    I have another speculation. The second log says Unexpected or missing value PackageName. So I'm guessing there should be a PackageName = "KinectSDK-v2.0_1409-x64.msi" as well as the {77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\KinectSDK-v2.0_1409-x64.msi folder and file existing for the setup to proceed properly. And the fact that "HKLM\Software\Classes\Installer\Products\205FBF7763148CB47B45A6100C52899C\SourceList" exists might mean that 205FBF7763148CB47B45A6100C52899C is an identifier for the SDK. It might be a good idea to delete that tree altogether(again taking precautions by exporting the tree to a .reg to be able to revert the changes later).

    PS: My experience with installers and msi creation is rather fresh. Been developing them for a few months now but have only had one fail case similar to yours.

    Monday, June 12, 2017 12:56 PM
  • I'm going to follow your method after work, very grateful for your kind support. i'll keep you updated.


    Monday, June 12, 2017 1:28 PM
  • Hi! Okay there has been some progress, The first two methods did not work - 

    "Export "Source" node to .reg file somewhere. Then empty the value "---------  n;1;C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\" and retry the SDK setup.

    In case that fails, double click the reg file to rewrite the "---------  n;1;C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\" and instead of emptying it just remove ";C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\" from the end. And then retry the setup."

    I tried you 3rd method where i deleted the tree altogether.  I clicked the Kinect SDK 2.0 installer and it installed good without showing any error. Now referring to 'C:\ProgramData\Package Cache' there are no "KinectSDK-v2.0_1409-x64.msi" as well as the {77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\KinectSDK-v2.0_1409-x64.msi" In the folder.

    I ran the 'Kinect Studio 2.0' program and tried to connect, but it gives an error stating 'Cannot connect to the Kinect Host Service. Check the service status and try again'.

    Then I ran the 'SDK Browser 2.0' and ran 'Kinect Configuration Verifier' Most of the list in the verifier is ticked green, however the last 3 came up with error flags.  It recognised and gave it a green tick that Kinect is connected.  But the bottom two has red cross stating 'Verify Kinect Software Installed' and 'Verify Kinect Depth and color Streams' both resulted stating 'Required Kinect Software Not Detected'.

    Lastly the 'USB Controller' section has a Orange exclamation mark sign.  The Result is 'Unknown USB 3.0 port detected. Your USB configuration MAY support Kinect for Windows.'   

    Thanks for your help and sorry for the later reply.

      

    Saturday, June 17, 2017 4:10 PM
  • So the service is either down or not even installed.

    Checking my own registry, there's not just one Kinect related package there.There are several.

    You could try going to "HKLM\Software\Classes\Installer\Products" and locating any Kinect related stuff under it.

    Again, backup the reg trees and delete them. Remember you want to delete the parent of SourceList because that's the unique identifier given to that package.

    Also my assumption for the garbage values was half true.

    Mine is like "n;1;C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\ "

    instead of

    "---------  n;1;C:\ProgramData\Package Cache\{77FBF502-4136-4BC8-B754-6A01C02598C9}v2.0.1410.19000\ "

    I'd suggest a cleanup of any installed Kinect stuff as well as the registry and then retry.

    PS: You have my sympathy going through this s***.

    Saturday, June 17, 2017 5:48 PM
  • Thank you for your kind advice, im going to do this and let you know when i get some free time. Worse thing is I'm a noob when it comes down to windows technical side, but so far your advice has been easy to follow. However, cleanup seems to sound very Long, is there a way of cleaning it up by easily searching it or i dont know maybe a software that cleans it up??

    Cheers!

    Friday, June 23, 2017 1:44 AM
  • I know, unfortunately, there's no cleaner for Kinect as far as I know and I'm not sure whether CCleaner can do the job.

    Good luck anyway.

    Friday, June 23, 2017 7:15 AM
  • Hey, sorry for the Very late reply, I hope you are still around, Unfortunately after several attempts to fix this, i have deleted everything related to Kinect, deleted everything related kinect from the RegEdit.  I tried installing it again, but it just doesn't install anymore.  It says installation successful but nothing gets installed. Im just ticked of at Microsoft for not making this user friendly.  I've got a Kinect 2.0 Hardware but cannot use it. Lame.

    ARGH!

    Thanks.

    Thursday, September 7, 2017 12:46 AM
  • Is clean installation of Windows 10 an option for you?

    You are not the first person on this forum to report issues with usage / installation of SDK on "upgraded" Windows.

    Thursday, September 7, 2017 6:37 AM
  • Yeah that's my last option. 
    Tuesday, September 12, 2017 12:34 PM