Open TianyiFranklinWang opened 2 years ago
Same issue here, it fails when trying to install the Device Drivers. Plugging out all controllers doesn't help (unlike Windows 10)
Install Log: https://pastebin.com/UvLB0kZ6 Setup Log: https://pastebin.com/9ye9qty5
Most suspicious lines are
2021-10-05 23:32:36.164 InitFromRegistry(): FileF:\Christian\Downloads\vJoyInit.reg not found
2021-10-05 23:32:36.164 Exec_vJoyInstall() - Start
2021-10-05 23:32:38.673 vJoyInstall.exe Was executed. Result code: -5
@NPU-Franklin I've just seen that the author is not maintaining the project anymore.
I used this fork https://github.com/njz3/vJoy and installed it successfully under Windows 11
@NPU-Franklin I've just seen that the author is not maintaining the project anymore.
I used this fork https://github.com/njz3/vJoy and installed it successfully under Windows 11
Thanks a lot! I'll try it later.
hi for me same vjoy not working since windows 11 update and i dont know how to fix the problem.Anyone know how to fix it Thx?
I had had enough of bad experience on Windows 11, so I just downgraded to Windows 10. :tada: Problem solved!
any fix?
I'm really keen for a fix to this too. njz3 or anyone else, is someone interested in taking a look at this? Thanks :)
@NPU-Franklin I've just seen that the author is not maintaining the project anymore.
I used this fork https://github.com/njz3/vJoy and installed it successfully under Windows 11
Did you have to do anything special to get this working?
@NPU-Franklin I've just seen that the author is not maintaining the project anymore. I used this fork https://github.com/njz3/vJoy and installed it successfully under Windows 11
Did you have to do anything special to get this working?
I built it for arm64 platform and it didn't work on Windows11 arm64 too.
@Colmanian @longjunyu2 I just used the latest github release vJoySetup-2.2.1-signed.exe
.
The config menu is a unstable, but the virtual device itself is functioning for me. However I'm not using vJoy at the moment, so I don't know about long-term stability.
Did anyone else get the vJoySetup-2.2.1-signed.exe to work for them on Windows 11? It doesn't seem to be working for me. I have basically the same error as above.
No it isn't working, the install fail, it is unable to create the devices.
But vJoy 2.1.9.1 from jshafer817 seems to work
Awesome, 2.1.9.1 by jshafer817 worked for me too! Thanks!
Sweet, don't want to buy a new signing certificate and go through all that again, but I will if needed. 2.2.1 has some newer force feedback features.. Hmmm
Spent some hours yesterday to dig into the Windows 11 issue for v2.2.1, and can confirm it is related to the driver itself not being loaded by windows 11 (while it works on windows 10), and not the installer process. During the install phase, vjoy installer asks to load the driver vjoy.sys file after copying all the file. The -5 errors come from Windows 11 indicating the file is either not loadable (driver compatibilty issue), or there is not enough memory to load it (?!?). Sadly, I cannot test on a computer equiped with Win 11 and test-signing enabled to confirm where the driver issue is located.
vJoy 2.1.9.1 by jshafer817 installed correctly on Windows 11, and works well.
Hi, are there any plans to release the signed version for Windows 11? @jshafer817 @njz3
@MichalBerner https://github.com/jshafer817/vJoy/releases/tag/v2.1.9.1 That is signed for Windows 10, but people say it works with Windows 11. Not sure about @njz3 status is on his version as his supports more force feedback stuff.
You are right. Version 2.1.9.1 works with Windows 11. I can confirm. I should be more precise with my question. What I meant was if there is a plan to release the signed version of vJoy driver with extended FFB support (2.2.1.1).
@MichalBerner I was going to renew my signing cert, I even paid the money. But then they wanted me to "revalidate" which requires letters from an attorney or etc. It was a bit of a pain the first time around and so I decided not to renew. As long as 2.1.9.1 is working in Windows 11 I am happy. But when vjoy broke in Windows 10 1903, I put down like $400 and a friend pitched in $300. I think this is why the original developer stopped messing with vjoy as he stated he didn't want to mess with the certificate requirements and I totally get that.
@MichalBerner I was going to renew my signing cert, I even paid the money. But then they wanted me to "revalidate" which requires letters from an attorney or etc. It was a bit of a pain the first time around and so I decided not to renew. As long as 2.1.9.1 is working in Windows 11 I am happy. But when vjoy broke in Windows 10 1903, I put down like $400 and a friend pitched in $300. I think this is why the original developer stopped messing with vjoy as he stated he didn't want to mess with the certificate requirements and I totally get that.
totally get this..suck a shame great little app..thanks for all the efforts!...used this for Oculus and pinball VR...doesnt work for me now on windows 11.... anyone got it working or another way to Oculus controllers please share....
As of July 25 of 2022, the v2.1.9.1 version is working, on Windows 11 (I'm using the Windows 11 Version 21H2 Build 22000.795)
I Would love to see the @njz3 version working that has great improvements (https://github.com/njz3/vJoy/releases/tag/v2.2.1.1) But that gives an error on installing the driver. Even if is a paid software, I would pay for it...
Or even @ianb888 with his latest fork.
A lot of the issue is signing the program again. I don't have to resign my fork, but the njz3 version needs to be signed, although disabling driver enforcement should work without having to sign the program. Signing costs $700.... Want to spend $700?? In addition they have to verify you... so you gotta get with your attorney or if you are a company and have a dunn and bradstreet it is a bit easier. sarcasm
Before even trying to sign it, I need to found the explanation why the driver does not load. Unfortunately I don't have a second computer with win11 to debug this kernel loading issue.
I do get it, thanks for the info.
I tried compiling my fork with Visual Studio 2022 and the latest WDK and SDK and.... no dice... same error as you.
On Mon, Jul 25, 2022 at 3:39 PM njz3 @.***> wrote:
Before even trying to sign it, I need to found the explanation why the driver does not load. Unfortunately I don't have a second computer with win11 to debug this kernel loading issue.
— Reply to this email directly, view it on GitHub https://github.com/shauleiz/vJoy/issues/57#issuecomment-1194599983, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6CD2LKPKMXTD7PZUSJWU3VV33OJANCNFSM5FEDTUBQ . You are receiving this because you were mentioned.Message ID: @.***>
-- Justin Shafer Onsite Dental Systems 7704 Sagebrush Ct. S. North Richland Hills, TX. 76182 (817) 909-4222
Just confirming & updating date, loaded & running in Windows 11 OS Name Microsoft Windows 11 Pro Version 10.0.22621 Build 22621
side note MOST pass issue have been with Windows HOME version I surgest NEVER get the HOME version as I ALWAY had my hands tied when dabbling with things. Will try the other version too. NUP! :(
As of July 25 of 2022, the v2.1.9.1 version is working, on Windows 11 (I'm using the Windows 11 Version 21H2 Build 22000.795)
I Would love to see the @njz3 version working that has great improvements (https://github.com/njz3/vJoy/releases/tag/v2.2.1.1) But that gives an error on installing the driver. Even if is a paid software, I would pay for it...
Or even @ianb888 with his latest fork.
https://github.com/njz3/vJoy/issues/9 the workaround for installing v2.2.1 can be found here. I just went through it and it installed so now to check it out.
ok so it installed but I can't get it to do anything. I run Vjoy configure and it runs but when I click add device I get nothing, I can check the box that say enable vjoy but the apply button is greyed out. Thoughts??
Just tried the workaround and even if the installer succeed, the driver is actually not loaded as nothing appears in the device manager of Windows. Faking the reg HID seems to make the installer beleived it was loaded (the registry keys appears when the driver loads), while actually it did not.
Awesome, 2.1.9.1 by jshafer817 worked for me too! Thanks!
We still don't really know why......
On Thu, May 11, 2023 at 1:22 AM HDXUT @.***> wrote:
Awesome, 2.1.9.1 by jshafer817 worked for me too! Thanks!
— Reply to this email directly, view it on GitHub https://github.com/shauleiz/vJoy/issues/57#issuecomment-1543404160, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6CD2I45PFVA62QH6F7DDLXFSARTANCNFSM5FEDTUBQ . You are receiving this because you were mentioned.Message ID: @.***>
-- Justin Shafer Onsite Dental Systems 7704 Sagebrush Ct. S. North Richland Hills, TX. 76182 (817) 909-4222
No it isn't working, the install fail, it is unable to create the devices.
But vJoy 2.1.9.1 from jshafer817 seems to work
here we are in 2023, this works as of 08/08/2023. thanks.
And none of us really know why... because I signed both projects.... One was compiled in a newer SDK and Visual Studio. The other was signed with the same exact stuff as the original, with one additional commit. Weird.
And none of us really know why... because I signed both projects.... One was compiled in a newer SDK and Visual Studio. The other was signed with the same exact stuff as the original, with one additional commit. Weird.
Hello there.
What I had to do in order to get vjoy to download ( I am on W11 ) I had to download the Version- 2.1.9.1 in order for it to work as none of the other versions seemed to want to download.
and with any of the other versions, each time i tried to download em, ( which the installer itself downloads ) but when downloading Vjoy after going through the installer phase, keep getting greeted with a Vjoy failed to install error. BUT Version 2.1.9.1 worked fine for me.
Ok, good news. After many months (years?), I finally setup a windows 11 computer for kernel debugging to see what happens . This required me to compile and install vjoy with testsigning enabled (using a test certificate), using VS2022 and latest WDK available to date (10.0.22621.0). The dowside of this upgrade is that win32 is not accepted anymore, only x64 is available. So OS Windows target version must be >10 (ie windows 10, windows 11, and possibly future major OS).
So, after debugging step by step, I discovered that the main loading issue is related to this function DriverEntry function, where a piece of code is called at the wrong time: Basically, we ask for a memory allocation, while driver memory pool is not yet created...
So I am happy to say that we probably have a fix for vjoy 2.2.x
Great work man!!!!
The fixed version also installs perfectly on win10
Good morning, thanks for your work. I have win 11, I can install Vjoy 2.2.1 using registry patch but when I start Vjoy everything is disabled. Will there be patches in the future? Thanks again
Current v2.2.1 cannot be installed on Win11 as there is a bug inside the code that does the initialization of the driver. The fix is in the new source code, but not published as an installer as I do not have the necessary certificate to sign the driver.
Here is a download link to the TESTSIGN binary version v2.2.1.2 for feedbacks.
https://drive.google.com/file/d/1Vu2JICPl9xMlvjQvZLP05dBodJmepk6o/view?usp=sharing
To use it, first enable TESTSIGN mode on your windows computer by entering Bcdedit.exe -set TESTSIGNING ON
in an elevated command prompt.
https://learn.microsoft.com/en-us/windows-hardware/drivers/install/the-testsigning-boot-configuration-option
Then download my test certificate that you can download from here:
https://drive.google.com/file/d/1QAWUyx7mptCcIt99xyQ3mjhte9KgxxDY/view?usp=sharing
Install the certificate by double-clicking on it and select the "Trusted Root Certification" store.
https://learn.microsoft.com/en-us/windows-hardware/drivers/install/installing-test-certificates
Finally, proceed to vJoy installation as usual.
Great work!
great job, it installs. However.. when I launch Force EmuWheel the program gives me this error : [ERROR] vJoy driver version does not match the version of 'vJoyInterface.dll'[ERROR] Could not initialize vJoy.
The error is really self explaining....
yes, i figured it out even if i don't know anything about programming, but how to fix it?
EmuWheel software expect an old version of the driver. You have to recompile.
Here is another download link to the TESTSIGN binary version v2.2.1.3 for feedbacks. https://drive.google.com/file/d/1SEYtmJMelM_2xMC0SeO8neArsTy6_fh2/view?usp=drive_link And the corresponding SDK: https://drive.google.com/file/d/1r1MUxAatZxZW-fnKETdP7weKKwXJMGkL/view?usp=drive_link It includes a fix for gamepad javacript API on browser (see https://github.com/njz3/vJoy/issues/12), by reducing the HID reported values of axes and continous hat switches to 16 bits instead of 32 bits. This may break compatibility with existing feeder software (to be confirmed).
I've tried 2.1.9.1, as well as the two testsign builds by njz3. I can get them all to install, kinda. They hang at the end. The kdmf installer is stuck. Once I close it it says its successful and will often work.
But as soon as I restart it is dead and never works again. I have to uninstall and reinstall.
What is it about a restart that causes it to completely stop working from that point on? I had it working for the last year or so, but it was flaky. Tried installing the njz3 versions above and now none of them seem to work.
I've tried 2.1.9.1, as well as the two testsign builds by njz3. I can get them all to install, kinda. They hang at the end. The kdmf installer is stuck. Once I close it it says its successful and will often work.
But as soon as I restart it is dead and never works again. I have to uninstall and reinstall.
What is it about a restart that causes it to completely stop working from that point on? I had it working for the last year or so, but it was flaky. Tried installing the njz3 versions above and now none of them seem to work.
Have you try my test builds with TESTSIGN mode enabled? Please look here for step by step instructions : https://github.com/njz3/vJoy/issues/12
@njz3 Although I got both the test signed builds you linked above to install on Windows 11, the configure utility works as expected, and the vjoy devices appear in control panel USB Controllers etc, they don't seem to work with UCR as the feeder. The vJoy device(s) appear as output devices and can be mapped to as expected, but no response in the vJoy monitor app. For reference, vJoy 2.1.9.1 from jshafer817 does work as expected.
vJoy kept failed to install on my device even the latest release. Please help me! Here is some detailed information about my device.