Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

vJoy failed to install on Windows11 #57

Open
TianyiFranklinWang opened this issue Oct 1, 2021 · 63 comments
Open

vJoy failed to install on Windows11 #57

TianyiFranklinWang opened this issue Oct 1, 2021 · 63 comments

Comments

@TianyiFranklinWang
Copy link

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
@Mayerch1
Copy link

Mayerch1 commented Oct 5, 2021 •
edited

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

@Mayerch1
Copy link

Mayerch1 commented Oct 5, 2021 •
edited

@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

@TianyiFranklinWang
Copy link
Author

@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.

@Mn29-02
Copy link

Mn29-02 commented Nov 11, 2021

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?

@TianyiFranklinWang
Copy link
Author

I had had enough of bad experience on Windows 11, so I just downgraded to Windows 10. 🎉 Problem solved!

@devMorpheus
Copy link

any fix?

@Colmanian
Copy link

I'm really keen for a fix to this too. njz3 or anyone else, is someone interested in taking a look at this? Thanks :)

@Colmanian
Copy link

@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?

@longjunyu2
Copy link

@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.

@Mayerch1
Copy link

Mayerch1 commented Dec 8, 2021

@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.

@SlyryD
Copy link

SlyryD commented Dec 19, 2021 •
edited

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.

@jdubus
Copy link

jdubus commented Dec 22, 2021 •
edited

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

@SlyryD
Copy link

SlyryD commented Dec 23, 2021

Awesome, 2.1.9.1 by jshafer817 worked for me too! Thanks!

@jshafer817
Copy link

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

@njz3
Copy link

njz3 commented Dec 29, 2021

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.

@CoDYsss
Copy link

CoDYsss commented Jan 3, 2022

vJoy 2.1.9.1 by jshafer817 installed correctly on Windows 11, and works well.

@MichalBerner
Copy link

Hi, are there any plans to release the signed version for Windows 11?
@jshafer817 @njz3

@jshafer817
Copy link

@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.

@MichalBerner
Copy link

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).

@jshafer817
Copy link

@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.

@britxpatusa
Copy link

@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....

@byjokese
Copy link

byjokese commented Jul 25, 2022 •
edited

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.

@jshafer817
Copy link

jshafer817 commented Jul 25, 2022 •
edited

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

@njz3
Copy link

njz3 commented Jul 25, 2022

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.

@byjokese
Copy link

I do get it, thanks for the info.

@jshafer817
Copy link

jshafer817 commented Jul 28, 2022 via email

@micsthepick micsthepick mentioned this issue Nov 1, 2022
Closed
@wolfbiteaus
Copy link

wolfbiteaus commented Jan 23, 2023 •
edited

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.

@Neonnite1753
Copy link

njz3#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.

@Neonnite1753
Copy link

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??

@njz3
Copy link

njz3 commented Aug 16, 2023

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:
image
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
image

@jshafer817
Copy link

Great work man!!!!

@njz3
Copy link

njz3 commented Aug 16, 2023

The fixed version also installs perfectly on win10
image

@Sycret01
Copy link

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

@njz3
Copy link

njz3 commented Aug 23, 2023

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.

@njz3 njz3 mentioned this issue Aug 23, 2023
Closed
@njz3
Copy link

njz3 commented Aug 24, 2023 •
edited

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.

@jshafer817
Copy link

Great work!

@Sycret01
Copy link

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.

@njz3
Copy link

njz3 commented Aug 25, 2023

The error is really self explaining....

@Sycret01
Copy link

yes, i figured it out even if i don't know anything about programming, but how to fix it?

@njz3
Copy link

njz3 commented Aug 25, 2023

EmuWheel software expect an old version of the driver. You have to recompile.

@njz3
Copy link

njz3 commented Aug 29, 2023

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 njz3#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).

@njz3 njz3 mentioned this issue Sep 13, 2023
Closed
@flexgrip
Copy link

flexgrip commented Nov 1, 2023 •
edited

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.

@njz3
Copy link

njz3 commented Nov 1, 2023

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 :
njz3#12

@MrNiceUK
Copy link

@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.

@njz3
Copy link

njz3 commented Nov 30, 2023

@MrNiceUK probably UCR use an older version of the vJoyInterface dll which is not compatible with vJoy 2.2.x, mainly due to forcefeedback fixes that needed internal changes to the driver API.
If you don't need the fixes for FFB, you can stay on vjoy 2.1.9.

@xenicle
Copy link

xenicle commented Dec 10, 2023 •
edited

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 njz3#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).

Hello ! I've tried 2.2.1.3 and it install correctly on latest Windows 11 in TESTSIGN mode, but I use irFFB and in this mode IRacing prevent to start race with an anti-cheat and when disabling TESTSIGN mode Windows disallow Vjoy driver to start due to not verified signature... Hope a fully signed version will drop ! :p

@BrunnerInnovation
Copy link

Hey folks
we decided to go through the signing process and just released a fully signed version in our fork here.
We just built the master branch which was already at version v2.2.2.0 and tested it on several win10 and win11 machines with great success.
Hope this helps others and puts the great work of @njz3 (and others) to use :)

@njz3
Copy link

njz3 commented Dec 19, 2023

@BrunnerInnovation many thanks!

@njz3
Copy link

njz3 commented Dec 19, 2023

@BrunnerInnovation I just see that you have based your certified build on my master rep. Would it be possible to do another build integrating my latest fixes ? (those are mainly in this branch : https://github.com/njz3/vJoy/tree/dev/w7_pr3)
I can perform the merge to master today.

@BrunnerInnovation
Copy link

@njz3 yes, I saw that you made fixes in another branch, but I had troubles building it. And since the master built just fine and no issues were found while testing I decided to just go with the current state of the master branch.
But sure, if you merge the changes we could do another run of the certification process and maybe release a v2.2.2.1?
The process of submitting the driver files in the Microsoft Partner backend isn't that complicated or time consuming now that we finally know how to do it :D

@jshafer817
Copy link

jshafer817 commented Dec 19, 2023 via email

@njz3
Copy link

njz3 commented Dec 19, 2023

@njz3 yes, I saw that you made fixes in another branch, but I had troubles building it. And since the master built just fine and no issues were found while testing I decided to just go with the current state of the master branch. But sure, if you merge the changes we could do another run of the certification process and maybe release a v2.2.2.1? The process of submitting the driver files in the Microsoft Partner backend isn't that complicated or time consuming now that we finally know how to do it :D

The explanation is that the "master" branch was updated to compile for w10/w11 only, while the /dev/w7_pr3 is meant to be compiled for w7 up to w11, requiring build tools older than the ones that are readily available from Microsoft when installing VS2022.

@BrunnerInnovation
Copy link

Ok I thought so... And I actually tried for several hours to get all required build tools, but with no luck.
And since those older platforms aren't relevant to us I stopped to spend time on it. It would of course be nice to have a repo still supporting all old platforms going forward, but I'm afraid the time and effort required isn't really justified. Retro gaming scene can still use the older releases available. Or what are your thoughts about that?

@njz3
Copy link

njz3 commented Dec 19, 2023 •
edited

I only know some industrial platforms like Beckhoff and Siemens that were using win7 (mostly embedded versions WES7) where it could be relevant, but that's really a niche.
I will try to backport my most important changes to the master branch w10/w11 and let you know when done.

@sonicviz
Copy link

sonicviz commented Apr 8, 2024

Hi,
I came across this while looking into https://sourceforge.net/projects/dxace/ which has a vjoy dependency.
I've previously avoided vjoy in win 11 for obvious reasons 😱
Any chance of an update on vjoy status with win11?
Is this V2.2.1.1 https://github.com/njz3/vJoy/releases/tag/v2.2.1.1 the definitive working win 11 version, or ?

Is it even worth the pain of trying to get vjoy working on win 11 atm?

Thanks! (also for the great work above, I read the thread and can feel your pain.)

@BrunnerInnovation
Copy link

Hi @sonicviz,

we've a signed version of vJoy https://github.com/BrunnerInnovation/vJoy/releases/tag/v2.2.2.0.
We've had great success with it on win 11 so I hope it works for you as well.
kind regards

@sonicviz
Copy link

sonicviz commented Apr 8, 2024

Awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests