Been attempting to get this to work for the last couple of days. I cannot seem to get it to work for the life of me on my x64 Vista machine.

My system specs and error:
http://img44.imageshack.us/gal.php?g=specsm.jpg

I have followed nearly every guide i could find, repeating and restarting many many times. I have the OS set to automatically disable the driver signing problem, also i'm running windows in driver test mode. I have noticed that the guides are all fragmented. Please, if you would be so kind, compile a guide including pictures, such that I wouldn't have to refer to anything outside the one page. The more pages i switch between, the more confusing it gets. Sometimes the files aren't the same and i get confused. I'm getting really frusturated, I just wanna have basic usage of the controller.

I'd REALLY REALLY appreciate it so I am not wasting another 12 hours trying to figure it out.

hey InoSix,
i dont know how much help i can be, but error 39 is because your computer is still looking a signed motioninjoy driver.
If you are running test mode means that you must be using deso.
i had this problem to but wat i did was to digitally sign the driver using deso.
that seemed to do the trick for me.

driver location in C:\WINDOWS\System32\drivers\Mijufilt.sys
it should ask you to restart.

dats all i could think of now. if dats not it then it may have to do with sp2 cause im runing sp1 and i have no trouble

but no, it's because the service pack 2, the drivers are not compatible with, puts you on windows 7 x64 in 7201, its work very well.

download and put her in place of another in
http://rapidshare.com/files/242983353/driver.rar.html

C:\Windows\System32

after his work very well

What Dante said was that service pack 2 brokes the compatibility of monitionninjoy with vista x64, however, using the files from windows 7 rc it's possible to recover such compatibility.

The files that he posted above are from windows 7 rc, you should put them on C:\Windows\System32 directory....

I haven't tested myself but there is succesful reports of it, I can only say thanks to dante

http://www.megaupload.com/?d=5OBB374P <- another mirror for the same files.

I'm running Vista x64 Home Premium on an HP Pavilion dv71130-us. SP2 did indeed break the MiJ driver - I was using the older version that didn't have the configuration tool. I updated to the latest driver (MotioninJoy_0100_amd64) but still couldn't get it to work - both the USB and BT drivers fail with Code 39, and log 4 events to the event log (all EventID 26, two each of "Application popup: : \SystemRoot\system32\DRIVERS\MijBThid.sys cannot find WDFLDR.SYS WdfVersionUnbindClass" and "Application popup: : \SystemRoot\system32\DRIVERS\MijUfilt.sys cannot find WDFLDR.SYS WdfVersionUnbindClass").

I found this post and downloaded the updated WDFLDR.SYS and WDF01000.SYS files, then copied them to %SYSTEMROOT%\System32 as instructed and rebooted. This did not solve the problem however, as those two files need to be located in %SYSTEMROOT%\System32\Drivers.

In order to overwrite the files, you must take ownership of them first. Here's how:
1. Create a System Restore point (just in case)
2. Open Windows Explorer as Administrator (go to Start, type Windows Explorer, right-click and select Run as administrator)
3. Browse to C:\Windows\System32\Drivers, highlight WDFLDR.SYS and WDF01000.SYS, press Ctrl-C then press Ctrl-V to make backup copies of the original files (yet another precautionary measure)
4. Right-click on WDFLDR.SYS and select Properties, then go to the Security tab
5. Click the Advanced button and go to the Owner tab, then click the Edit button
6. Set the owner to Administrators, then keep clicking OK until the file properties dialog is closed
7. Right-click on WDFLDR.SYS again and select Properties, then go to the Security tab again
8. Click the Edit button, highlight Administrators, and click the check box for Full Control, then click OK twice
9. Repeat steps 4 - 8 for WDF01000.SYS - you will now be able to overwrite the files
10. Browse to where you downloaded and extracted the Windows 7 RC files, highlight them both and press Ctrl-C
11. Browse back to C:\Windows\System32\Drivers and press Ctrl-V
12. Reboot the system and enjoy using your Sixaxis or DS3

I have fixxed the issue, but i dont like how i did it. I ended up installing the libusb-win32 under compatibilty for XP service pack 2. I dont like this because if I dont boot Windows up without disabling driver signing environment, ALL my usb and all extras (aka network card, modem) shit conflicts and will not work AT ALL. Le sigh. However, this does allow me to use the default HID drivers that loads up when I otherwise plug the damn thing in. Only extra step I hafta take aside from the F8 trick is to run the sixaxis64.exe to dectect the controller after its plugged in. I had tried the motion joy thing (many many many times). I was running in test mode with dseo and had used F8 to disable the driver signing and the driver was still giving me a code (39) error. I'd perfer to do it this motion joy way, but i dont wanna undo any of the changes to what i've already done if its not going to work on x64 Vista SP2. Thanks for all of your help.

Works fine with Hambone method....

Yeah, I gave it a try and it works. But configuring it is stupid hard. The only way i can map the R2 and L2 switches as they should be, I hafta pick the option to keep on the motion sesning. I simply can't get the Dpad to work because it seems to pick up the motion tracking when i go to configure the device. Kinda lame

yes you was right it was system32/drivers, files are duplicate, I forget, I solved this problem by looking at the log of the event said HAMBONE

I couldn't get this to work on Vista home premium 64 SP2, it was stuck on Code 10 and never registered my DS3.

So I did the same thing with hidusb.sys, hidparse.sys and hidclass.sys from my Windows 7 RC install (7100) to my Vista 64 install, and now everything works. I must have had an old version of something that needed an update, like maybe DirectX.

Well it works great in Assassin's Creed, but for some reason the sync lights never turn on like the instructions say they should. It's not a big deal, just odd.