FORUM › Forums › Software › CLS2SIM Software › WIN10 update V1903 and VJoy installation error
- This topic has 13 replies, 6 voices, and was last updated 5 years, 3 months ago by mikerichardsonuk.
-
AuthorPosts
-
14/06/2019 at 11:15 #1279jovabraParticipant
The combination of WIN10 v1903 is not a happy couple. The buttons in the CLS2sim and to assign to the USB function are out of order. I reverted back to WIN 10 V1809. See also my information on:
https://www.avsim.com/forums/topic/555422-vjoy-and-win10-version-1903-not-a-happy-couple/?tab=comments#comment-4014973
Regards
John v Braam14/06/2019 at 11:28 #1280webmaximusParticipantThis is really great info John, thanks for sharing!
I already stopped this Windows update thanks to you before I ended up in trouble.
Are there any news from Brunner how this will be handled going forward?
14/06/2019 at 22:36 #1281captainmdParticipantHi Richard, just curious as to how you were able to freeze the v1903 update only. The way I understand it, Windows will eventually shove this update into your PC whether one likes it or not.
14/06/2019 at 23:12 #1282webmaximusParticipantIt depends on what version of Windows you have. I have the Pro version which allows you do postpone so called ‘Feature updates’ for up to 365 days IIRC.
Even if you have the Home version of Windows, you might be able to use a MS tool that will allow you to hide (and by doing so block) certain updates you don’t want get installed. Not sure though if 1903 falls into the category of updates that can be hidden and blocked using the tool.
You can read more about it over here ->
https://www.digitalcitizen.life/how-block-unwanted-windows-driver-updates-installing-windows-10
05/07/2019 at 14:16 #1314othelloParticipantStopping updating Windows is not a solution.
As far as I know it is not a Win bug that will be fixed, but a new Win security(?) feature.
What we need is a working tool allowing to use X-Planes commands./Othello
05/07/2019 at 14:35 #1316webmaximusParticipantI fully agree!
I hope there will be some input from Brunner on this topic and what the plan is going forward.
05/07/2019 at 14:44 #1317Diego BĂĽrginKeymasterHi all
Raymond Beehler seems to be taking over the vJoy project. See here:
The topic from that post on is a particularly interesting read.
We are currently waiting for him to finish getting his code signing certificate.
Should his efforts fail, we will attempt to continue the project, but I don’t think that’s gonna happen.
He already has a test release linked on the forum, it’s just not signed yet.Regards
Diego05/07/2019 at 16:18 #1319webmaximusParticipantThis is really promising news, thanks Diego for commenting and sharing this information!
16/07/2019 at 18:17 #1335webmaximusParticipantDid you receive any more news or info on this Diego?
I noticed the last post in the linked thread is from early June.
Asked the same question in another thread in here, did something change in CLS2Sim 4.23.3 that would allow vJoy to work with Windows 1903? Guess not since nothing related to vJoy is mentioned in the change log since 4.15.0.
16/07/2019 at 18:24 #1336Diego BĂĽrginKeymasterHi all
Short answer: No news.
Raymond has ‘released’ a driver, but he doesn’t have his code signing certificate yet, so the driver is not signed.
You can install it but, you’ll need to put Windows into test signing mode, which is a pain.
That’s why we don’t include it.See here:
https://github.com/R-T-B/vJoy/releasesRegards
Diego16/07/2019 at 18:27 #1337webmaximusParticipantGot it, thanks again Diego!
16/07/2019 at 19:16 #1338jovabraParticipantHi all
The working vJoy for the 1903 is now avialable at:
http://vjoystick.sourceforge.net/site/index.php/download-a-install/download
I have just installed vJoy and until now no problems.
Succes and regards
John v Braam16/07/2019 at 19:44 #1339webmaximusParticipantWow, so this means we can now update Windows to 1903 and still use vJoy with CLS2Sim with no issues.
Thanks for sharing this great news John!
30/07/2019 at 19:18 #1350mikerichardsonukParticipantOk so VJoy installed fine but in cls2sim I’m getting A blocking operation was interrupted by a call to WSACancelBlockingCall
any ideas ? -
AuthorPosts
- You must be logged in to reply to this topic.