Open TheSurfCrusader opened 1 month ago
Here is the winver screenshot showing current 1909, in the process of upgrading to 22H2
Progress update,
I've upgraded to Windows 22H2, however the issue still exists, XboxKeyboardMouse is still throwing the windows error pop-up whenever i try to start the program :(
I did notice that i had two installations of the SlimDX program, a 32bit and a 64bit version, i've removed both and re-installed the SlimDX X64 program, however this does not appear to have solved anything.
I'm totally stuck now, am thinking about getting a new laptop but not even sure if the XboxKeyboardMouse program will work on a new laptop with Windows 10 or 11?
Is anyone using the program successfully anymore?
Anyone who can help get me back up and running will be greatly rewarded :)
Many thanks
Regards
Andrew
Maybe I need a bluetooth dongle plugged into my laptop for the Xbox controller driver?
I have a mouse plugged into my laptop and i have my Xbox controller plugged into my laptop via a sub cable but nothing seems to be overcoming the windows pop-up error :(
As a further update and in-light of the issues I've been experiencing with XboxKeyboardMouse on my upgraded laptop which has moved from windows 8 to 10.
I have been out and purchased a new PC running Windows 11 pro 64bit,
I've followed all the recommendations as per GitHub and installed the required SlimDX 64bit version and run the XboxKeyboardMouse setup.exe directly from GitHub, as well as running the ScpDriverInstaller.exe
The results of which are as follows:
The XboxKeyboardMouse program no longer shows the Windows error pop-up box, however this time as soon as the XboxKeyboardMouse program starts it quits :(
Now i remember reading somewhere about the program looking for a particular window title for the Xbox app, which from what i gathered from the comments, had changed as part of the latest Microsoft update to the Xbox app, does this ring any bells with anyone?
Again any further help with this would be greatly appreciated, either from developers or users :)
A bit of extra information:
When i run the XboxKeyboardMouse program with the task manager window open i do notice the following:
Both Wermgr.exe and Werfault.exe appear in the details section and then disappear when the XboxKeyboardMouse.exe quits ...
Just wondered if this was significant as I have no idea what either Wermgr.exe or Werfault.exe relate to?
Dear Developers,
I seem to have run into a problem with the XboxKeyboardMouse program I'm running on my laptop.
XboxKeyboardMouse had been running fine on my laptop for about a year, this was until my windows laptop told me that I needed to update the Xbox app.
I updated the Xbox app which appeared to move me to a new windows version, currently windows 10 version 1909 OB build 18363.1556
Since then every time i now run the XboxKeyboardMouse program, i get a windows generated relating to "XboxKeyboardMouse has stopped working" (screenshots attached)
"A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." (screenshots attached)
I've also noticed that a new XBOX controller driver has been installed and appears in device manager, not sure if this is relevant, but there's a ping from my laptop every time I run the XboxKeyboardMouse program just before i get the windows generated error message pop-up.
I've uninstalled and re-installed the XboxKeyboardMouse program with no joy, I've also installed the SlimDX SDK (January 2012) software as recommended, however I am still experiencing the same issue.
I read somewhere about someone who plugged a mouse into their laptop and the XboxKeyboardMouse program started working, however that does not seem to be the case for myself unfortunately :(
The Xbox 360 controller in device manager is showing as working properly, however there is an event which mentions, "Device USB\VID_045E&PID_028E\0000001 requires further installation.", again not sure if this is relevant and screenshots attached.
I'm currently in the process of upgrading the windows version to 22H2 to see if that makes a difference, I'll keep you posted.
In the meantime is there anything that the developers would like me to check and share?
Many thanks
Much appreciate any help anyone has on this issue :)
Regards
Andrew