This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
1 / 37
Nov 2017

A hotfix for this issue has been released, please update to version 3.2.1 of the Orion software available here: http://www.leapmotion.com/setup5.0k

Hey everyone,

With the Windows 10 Fall Creators Update, Microsoft made some changes to how they handle Imaging Devices, changing them to "Cameras." This has resulted in a bug with our software. While we work on a better solution to the problem, here's a quick fix!

Note: Only make this change if you have installed the Fall Creators Update. This will break the software in earlier versions of Windows.

  1. Open up services.msc and pause or stop LeapService
  2. Navigate to your Leap Motion software installation folder and go to the Core Services folder (default C:\Program Files (x86)\Leap Motion\Core Services)
  3. Backup LeapSvc.exe and LeapSvc64.exe in a separate folder
  4. For V2 users, download and unzip this file6.7k into the Core Services folder, replacing LeapSvc.exe and LeapSvc64.exe
  5. Return to services.msc and restart LeapService
  6. Launch a Leap Motion enabled application and test!

If you have any questions, let us know. As an alternative to step 4, you can open up LeapSvc.exe or LeapSvc64.exe and change them manually with a hex editor:

  • Search for C6 1F DD 6B 0F 81 D0 11 BE C7 08 00 2B E2 09 2F
  • Replace that with B9 7A 3E CA C3 B4 E6 4A 82 51 57 9E F9 33 89 0F
  • created

    Nov '17
  • last reply

    Dec '20
  • 36

    replies

  • 55.0k

    views

  • 26

    users

  • 53

    likes

  • 10

    links

Is there a particular hex editor you recommend?

Notepad++96 has a hex editor plugin. I'd generally recommend it because I use Notepad++ all the time, though I can't vouch for its stability or usability compared to other hex editors.

Wow, I don't recall the last time I've seen a company advise their users to use a hex editor to fix a problem. No EXE files to download, no offset to the bytes for each EXE file, and no reminder to backup the file first. As a fellow programmer, I like it. Nicely done.

Thanks guys, Notepad ++ is already in the quiver so I will go with that.

Updated for those who are less comfortable with hex editors, but kept the original instructions for those who like to roll their own fixes.

To me for some reason Leap Motion Control Panel said that Leap Motion is Off and i could not enable it in any way after either using the downloaded exe's or modifying the files myself. But works fine with original ones.

Strange indeed, if with others it works so good sob

But if there is an official patch coming soon i think i can manage wink

@DARKKi did it show the red 'Disconnected' indicator in diagnostics?

If so, running this worked for me after reinstalling Leap Motion Control Panel: C:\Program Files (x86)\Leap Motion\Core Services\Drivers\dpinst64.exe

This fixed worked until I rebooted the computer. Now even when I repeat the process, it continues to say the device is not connected.

I tried the steps above and running dpinst64.exe, but it still has a red 'Disconnected' indicator in the diagnostics.

For me this was solved by reinstalling the drivers (instead of editing the hexes), i.e:

C:\Program Files (x86)\Leap Motion\Core Services\Drivers\cyfx3.inf

and

C:\Program Files (x86)\Leap Motion\Core Services\Drivers\ov580.inf

rightclick each file and choose install.

Don't know how persistent that is but got rid of the red "disconnected" anyways and my leap motion works like before now

1 month later

It worked for me, pretty straightforward. Thank you, Alex!

16 days later

Could this be the issue I'm facing with leap motion V2 as well?

It used to work just by installing the setup, but it isn't recognizing the device now (Windows 10).

I have noticed the version is still the same (2.3.1+31549), so I'm guessing no hotfix has been released yet.

I'll try Orion and see if that solves the issue.

Edit: Yeah, it works with Orion, so V2 has probably the same issue with Fall Creators Update.

Yes, this affects V2. The patched service files are posted in the original post in bold. You can replace those files if you wish to continue using the V2 software.

Thanks for the info :slight_smile: I'll try that soon. But a hotfix version should be released soon, right?

I'm not aware of any ETA for a hotfixed version of the V2 installer but Orion was hotfixed with V3.2.1

1 month later