vJoy failed to install on Windows11

[TianyiFranklinWang]

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

[njz3]

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

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]

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]

@BrunnerInnovation many thanks!

[njz3]

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

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

:) nice work

On Tue, Dec 19, 2023, 6:19 AM Brunner Elektronik AG < @.***> wrote:

@njz3 https://github.com/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

— Reply to this email directly, view it on GitHub https://github.com/shauleiz/vJoy/issues/57#issuecomment-1862657748, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6CD2PHJGHFEF6EKF5U6ULYKGA55AVCNFSM5FEDTUB2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBWGI3DKNZXGQ4A . You are receiving this because you were mentioned.Message ID: @.***>

[njz3]

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

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]

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]

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]

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]

Awesome, thanks!

[eliasgm17]

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

i Just logged in to say thank you.