vJoy
vJoy copied to clipboard
shauleiz
vJoy failed to install on Windows11
vJoy kept failed to install on my device even the latest release. Please help me! Here is some detailed information about my device.
版本 Windows 11 专业工作站版
版本 21H2
安装日期 2021/8/17
操作系统版本 22000.194
体验 Windows 功能体验包 1000.22000.194.0
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!
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
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 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.