can't get installed on Windows 64 bit system

Question

can't get installed on Windows 64 bit system

mrchanshares opened this issue 7 years ago · 23 comments

I get a message saying
" The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
So it can't get installed on Windows 64 bit system. Any solution? Can you compile it in Window 10 64 bit system?

Answer 1 · 2017-10-30T13:48:37.000Z

Are you installing from the repository or from the release zip file?

FakeGPS is only built for x64 systems.

Answer 2 · 2017-10-31T00:52:22.000Z

I install the device driver from clone or download at https://github.com/juliankay/FakeGPS

I get the screenshot.

Answer 3 · 2017-10-31T00:53:01.000Z

I try again with
FakeGPS v1.0.0-alpha2

It still fail:

Answer 4 · 2017-11-04T18:32:12.000Z

I have exact same issue as above. I get "The following hardware was not installed..." message as the screenshot shows.

Answer 5 · 2017-11-04T20:58:45.000Z

@Nikvand also x64?

Answer 6 · 2017-11-04T21:24:28.000Z

@juliankay Of course x64

Answer 7 · 2017-11-10T08:34:53.000Z

@juliankay I have the same error on a brand new Azure VM on Windows 10 Pro 1709 (x64 of course

Answer 8 · 2017-11-10T08:50:35.000Z

Thanks for the information everyone. I've not had a chance to test this on 1709 yet, but I'm going to provision a new VM to work out what's happening.

Answer 9 · 2017-11-10T09:12:32.000Z

Interestingly it worked first time when I installed on an existing VM which has 1709 installed, but I'll provision a fresh machine to test there.

Answer 10 · 2017-11-10T10:02:04.000Z

Worked first time on a brand new VM running Windows 10 x64 version 1709.

Answer 11 · 2017-11-10T10:03:19.000Z

@supra63200 can you provide repro steps? can you assure me you following the instructions correctly?

Answer 12 · 2017-11-10T10:51:59.000Z

type bcdedit /set testsigning on in a Powershell (tried both admin and user)
Open device manager
Select the computer
Click Add legacy Hardware in Action Menu
Click Next
Select install the hardware that I manually select from a list (Advanced)
Select Sensors in the list and click Next
Slect the FakeGPS.inf from the extracted release archive (in "x64 driver" folder)
On page "ready to install click Next
"...Installing..."
Click Finish

Fun fact : after the fifth installation it just decided to work (did the exact same steps)
Previously after "..installing..." I had the same window as @mrchanshares

Answer 13 · 2017-11-10T11:26:36.000Z

Hmm. Well you need to reboot after turning on test mode, and either reboot or disable/enable the device after installation. If you've rebooted, that might have fixed your issue.

I'm not sure why it says "Fusion Sensor V2" as it says "FakeGPS Sensor" for me... bit strange!

Glad you've got it working, hopefully these steps will help other folk too.

Answer 14 · 2017-11-10T12:32:45.000Z

No I didn't that's the weird part it just worked after a while, no reboot necessary but it was stuck on the first start error (issue #3 ) even after reboot. So I uninstalled and reinstalled it and now it works perfectly and the name changed to FakeGPS Sensor

Answer 15 · 2017-11-10T12:55:16.000Z

Here is the updated walkthrough :

type bcdedit /set testsigning on in a Powershell (Right click on bottm-left corner Windows icon and then click on Windows PowerShell)
Reboot the computer
Open device manager (Right click on the Windows icon again and then on Device Manager)
Click on the computer (First element of the list)
Click Add legacy Hardware in Action Menu
Click Next
Select install the hardware that I manually select from a list (Advanced) and click Next
Click Next again
Click on "Have Disk" and then "Browse" and select the FakeGPS.inf from the extracted release archive (in "x64 driver" folder)
On page "ready to install click Next
Wait for the installation to complete
Click on Finish
Activate the driver:
- By rebooting the computer
- By Disabling the driver and re-enabling it again in the Device Manager(Right click on "FakeGPS Sensor and click Disable/Enable Device)
Open a PowerShell and navigate to the FakeGPS.exe folder (In the root of the extracted archive)
Use it by typing .\FakeGPS.exe -g or .\FakeGPS -s lat,long (ex: 1.2,3.4)

Answer 16 · 2017-11-11T02:51:23.000Z

Why I cannot do this? I am in Windows 10 x 64 Home

PS C:\WINDOWS\system32> bcdedit /set testsigning
The set command specified is not valid.
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.

Answer 17 · 2017-11-11T14:11:05.000Z

@mrchanshares as per the instructions:

Answer 18 · 2017-11-11T16:01:32.000Z

Maybe it can only be done on tablet device? My Window 10 is installed on a laptop made 3 years ago without touchscreen.

Answer 19 · 2017-11-11T16:16:36.000Z

@mrchanshares I think you probably just need to type the command correctly 🙂

bcdedit /set testsigning on

I don't know of any reason why it shouldn't work for you (though I haven't tested it on Windows 10 Home). I think it's just a user error here I'm afraid, I hope you work it out!

Answer 20 · 2017-11-11T16:22:24.000Z

Closed as there is no problem installing on Windows 10 x64, but I have opened #17 to track improved documentation.

Answer 21 · 2019-02-23T05:48:47.000Z

why i've this error " Object reference not set to an instance of an object."

Answer 22 · 2021-02-20T15:07:44.000Z

why i've this error " Object reference not set to an instance of an object."

this stopped happening to me after i open the MAPS app for windows and accept the popup. Then i tried FakeGPS -g and voila!

Answer 23 · 2021-04-07T17:56:15.000Z

@rangelrmorais That was it! I have no idea why this would be, I've even used my windows "device gps" in another application without complaint.