vJoy
vJoy copied to clipboard
shauleiz
Windows 10 (1903) version released 22/5/2019 breaks vJoy (now fixed in new release!)
edit This issue now seems to be fixed thanks to some determined effort from jshafer817. See thread below or just jump straight to https://github.com/jshafer817/vJoy/releases for the fixed version. Thanks jshafer817 for helping the community out, saving everyone's sanity.
original message Have been using vJoy for quite some time now (a couple of years?) and unfortunately this latest build of Windows 10 stops it from running. It also will not install if you try to remove and re-install, giving the error "vJoy failed to install". I hope you can find a way to fix this as I have become rather reliant on it for running my GameCube controller on my PC games.
Thank you in advance.
To all of you having the issue, please do the following:
- Open the file
%windir%\inf\setupapi.dev.logwith a text editor and empty/clear it - Try the installation again until you hit said error
- Then open
%windir%\inf\setupapi.dev.logagain and search for one or more lines starting with!!! dvi:and share the whole line here
In my case the issue is
Device not started: Device has problem: 0x03 (CM_PROB_OUT_OF_MEMORY), problem status: 0xc000009a.
Let's collect some common faults. Thanks.
I think it has already been fixed simply by compiling the code with Visual Studio 2019, but the final code needs to be signed to allow it to be safely distributed and installed. The original author does not want to pay for a new driver signing certificate.
https://vjoy.freeforums.net/thread/101/windows-1903-install-vjoy?page=1
@shauleiz According to this document a PARTIAL solution might be available, that does NOT require being in a constant "testing mode", but only a one time installation through "Disable driver signature enforcement" mode:
- the latest vjoy ( with win10 1903 support ) needs to be signed with the OLD CERTIFICATE - even if the cert is expired !
- a max of 3 new registry items needs to be added ( see above link ) to the system.
- a single reboot into "Disable driver signature enforcement " mode -> install that vjoy ( signed with old cert )
- reboot normally to windows.
IMHO, it should work... I currently use win10 1903, and managed to install a driver ( for another device ) using "Disable driver signature enforcement" mode, that has been sign with an expired cert ( that ended at 2010 ) with SHA-1 .... AND IT WORKS after a normal reboot !
Can you please sign latest vjoy with the OLD CERT ? I'm willing to test it and report back.
Luckily, I still have my old cert on my machine. If you or someone else is willing to provide me a file to sign I will be glad to sign it.
@R-T-B has made a working fork, see https://github.com/R-T-B/vJoy/releases
This is the installer. I need to get the compiled driver, then send it back for re-packaging.
On Mon, 24 Jun 2019 at 11:27, Bram Hagens [email protected] wrote:
@R-T-B https://github.com/R-T-B has made a working fork, see https://github.com/R-T-B/vJoy/releases
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/shauleiz/vJoy/issues/30?email_source=notifications&email_token=ADGHYJHGRPMHU5XMRNWDKF3P4CAOZA5CNFSM4HPSL7W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYMFOTA#issuecomment-504911692, or mute the thread https://github.com/notifications/unsubscribe-auth/ADGHYJB2XB4YCOKR4WTJORDP4CAOZANCNFSM4HPSL7WQ .
@R-T-B has made a working fork, see https://github.com/R-T-B/vJoy/releases
This is the installer. I need to get the compiled driver, then send it back for re-packaging.
I managed to extract the installer using 'innounp' free tool., and the compiled drivers (x86 & x64) are there.
extract innounp.exe in the same dir as vjoy installer, open cmd in that path and run:
innounp.exe -x vJoySetupUnsigned1903.exe -d<extracted_folder_name> -m
just replace <extracted_folder_name> with the name of the folder you want the extract file to enter to.
the '-m' option might be redundant, it extracts any embedded files related to the installer operation, like icons images and the installer config.
Please do tell if that helps you. TODA RABA :-)
Then I will have to repack and test. No thanks. I will be happy to sign it for you if you want. Just send me the file to sign.
On Mon, 24 Jun 2019 at 19:25, gps3dx [email protected] wrote:
@R-T-B https://github.com/R-T-B has made a working fork, see https://github.com/R-T-B/vJoy/releases
This is the installer. I need to get the compiled driver, then send it back for re-packaging. … <#m_1566818929351454317_> On Mon, 24 Jun 2019 at 11:27, Bram Hagens @.***> wrote: @R-T-B https://github.com/R-T-B https://github.com/R-T-B has made a working fork, see https://github.com/R-T-B/vJoy/releases — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#30 https://github.com/shauleiz/vJoy/issues/30?email_source=notifications&email_token=ADGHYJHGRPMHU5XMRNWDKF3P4CAOZA5CNFSM4HPSL7W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYMFOTA#issuecomment-504911692>, or mute the thread https://github.com/notifications/unsubscribe-auth/ADGHYJB2XB4YCOKR4WTJORDP4CAOZANCNFSM4HPSL7WQ .
I managed to extract the installer using 'innounp' free tool. https://sourceforge.net/projects/innounp/files/latest/download extract innounp.exe in the same dir as vjoy installer, open cmd in that path and run: innounp.exe -x vJoySetupUnsigned1903.exe -d<extracted_folder_name> -m just replace <extracted_folder_name> with the name of the folder you want the extract file to enter to. the '-m' option might be redundant, it extracts any embedded files related to the installer operation, like icons images and the installer config.
Please do tell if that helps you. TODA RABA !
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/shauleiz/vJoy/issues/30?email_source=notifications&email_token=ADGHYJEJULBAMSJCRLIXA43P4DYOBA5CNFSM4HPSL7W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYNPBII#issuecomment-505082017, or mute the thread https://github.com/notifications/unsubscribe-auth/ADGHYJEBUABYQK7UVCGCBLTP4DYOBANCNFSM4HPSL7WQ .
@shauleiz Since I don't know which files are needed for the driver to work I zipped files from 2 locations:
- the files AFTER installation ( of R-T-B compiled unsigned release of vjoy with 1903 support ) from "c:\Program Files\vJoy"
- the files extracted from the INNO installer ( e.i before installing ) - found in the zip under "extracted files" folder.
DOWNLOAD THROUGH WETRANSFER HERE
AFAIK ( please correct me if i'm wrong ), I only need the driver's files to be signed, not the installer or the rest of the vjoy's files. I can always install the complete unsigned installer, then replaced the unsigned drivers in "c:\Program Files\vJoy" with the signed one from you... then manually install them with 'vJoyInstall.exe' or devcon.
I hope this time I uploaded the right files - otherwise please clarify which files you need. Thanks.
Hello all. I am glad you are all following up with this. I sadly lost interest after I got stonewalled by nearly everyone I asked in person to help me with a signature and finally just realized I'd have to depend on nefarious on discord; Something unacceptable for our organizations needs (we need an under 6 hour turn around for any future issues, so I advised just dumping the hardware in question for something else. No offense to nefarious but he's just some guy online and I can't ask that kind of demand)
Don't let me deter you though, feel free to fork my code. I really hope you can all get it going for other needs like gaming and such with a valid (even if outdated) signature! Just wanted you to know I'm out, for these purposes. Good luck.
@R-T-B pardon me, but what have I missed here? Have we ever had contact in any way, shape or form before? This "some guy on Discord" has a registered business and an e-mail address btw. for "serious" conversations.
6 hour turn around? So what? Without an SLA? With FOSS developers? On Discord? What? 😅 Makes no sense whatsoever...
I have no idea how I was dragged into this "retirement" post but I don't like being confronted with "facts" I know literally nothing about, thank you very much.
Cheers
Oy, Nefarious, nice to see you here. No we never spoke and that was intentional on my part. I as I stated, never involved you because yes we need an SLA level of turn around and can't employ anyone further (ie I would never ask you to supply our needs without pay) than me for financial, confidentiality and trust reasons (understand, my client works in a court with high level security requirements. We used vjoy to work with very old footpedals via a custom feeder app I am the author of).
Yes, my requirements and situation are unique, but over. A cost analysis was done and new hardware is cheaper. A new hardware purchase covered our needs.
I don't mean any ill towards you with my statements. You just never were an option to begin with, due to several factors beyond my personal control. I am sure you are in actuality, probably a better coder than me. I also only referenced you because other people kept asking why I never contacted you and I felt I owed them and perhaps you an explanation for my strange rejection of your generous offer. Peace.
"Makes no sense whatsoever..."
Aye, I'd say more but... no. I like my job.
Alright, that makes things more clear now, the initial post was IMHO missing some context, thanks for your investment so far and have a good one 🙂
Yep, this issue is spread all over and it's easy to lose context and get lost. Sorry about that.
Anyhow, I still would support the project by providing compiled, unsigned drivers. Presumably that's what you would need for signing this? Or shaul above? I know the ones linked so far are "test signed" with my selfsigned certs and that will probably muck things up.
Otherwise you can work with the mess I have on github to produce your own properly signed builds. My build environment was Windows 10 1903 and VS Community 2019... Beware, so much cleanup needed in terms of whitespace, etc, but it does work.
I am going to sign this.. I use it so I have to get it signed. I had a friend donate, another will soon. https://www.gofundme.com/f/code-signing-app-for-vjoy
We are now at $390.. soon as I get a check in.. I will sign it. Since the code cert will be in my business name (they verify with dun and bradstreet, etc) I am going to add the patch to drivers.c and sign it. But it will be signed.
Whow, $ 486/450 reached. Is there any need to fund? I wanna support the project, too! I need vJoy for my X52 Pro (jittering slider) and DCS under W10 1903 again!
I use vJoy too for GameCube, I totally support the project ! Big thanks from France ! :)
@jshafer817 thanks for taking this on, I'm wondering if you could share a ballpark guess on the timeline until a signed release?
I just finished signing the agreement, after showing digi-cert my sales tax stuff.. then my mortgage and bank statement.. then had an attorney attest to who I am.. 3 more days????
Crazy the hoops required to jump thru to allow a free program to work on windows. MS really have the market locked down, don't they?
Doesn't really have anything to do with free or commercial, Microsoft really wants to clamp down on who can ship kernel binaries as they literally run with highest privileges and can crash the machine at best or could run malicious parts. I understand both sides.
Doesn't really have anything to do with free or commercial,
As can be seen from up there, it is impossible for a non-commercial entity to get this done. Even if that entity is able to pay for it, which is often unlikely. We're just fortunate that a commercial entity was willing to help us. (thank you jshafer817 you're a legend)
Meanwhile, a commercial entity which has less noble intentions could have their software signed easily.
I recognise that there are security issues to consider, and they are very real... but this is not the answer.
