Bms on Windows 11

[Selot]

Does anyone have bms installed on Windows 11? It is going well? Could you make a simple review? Something we should take into account before upgrading from windows 10 to windows 11?

Thank.

[Pegasus82]

@Selot:

Does anyone have bms installed on Windows 11? It is going well? Could you make a simple review? Something we should take into account before upgrading from windows 10 to windows 11?

Thank.

Unless there is a very compelling reason to upgrade to Windows 11 (and for me, there isn’t yet) I will be sticking with Windows 10.

[Lippy]

Support for Windows 10 will end in 2025 no more security updates.

[hoover]

I thought win10 was the last windows version ever?

I predicted win10 would change to a monthly subscription model once they had enough people on the hook, I’m going to extend /modify that prediction to win11 (or even better, win1X. :))

All the best,

Uwe

[Snake122]

My biggest concern with Win11 is if the driver/SST workaround for the X65F will still work.

[Ilmars]

@Snake122:

My biggest concern with Win11 is if the driver/SST workaround for the X65F will still work.

I’m using the 7.0.53.6 Saitek driver and SST software with W10 and it works fine with my X65F. Is there another workaround that you are referring to?

[oakdesign]

@Ilmars:

I’m using the 7.0.53.6 Saitek driver and SST software with W10 and it works fine with my X65F. Is there another workaround that you are referring to?

Same here works on win10 without any needed workaround

[Snake122]

SST isn’t really a work around but Win10 throws the not verified software when installing. Slightly worried that Win11 security features will cause an issue with SST, but think that’s a not too much of a concern really. But since I was mentioning drivers I thought I would put “/SST” on there.

Away from the computer to confirm if I’m using 7.0.53.6, but the drivers have been problematic for me because they are not verified drivers. I had to do the dig into device manager and select the more generic named driver instead of the one Windows assigns. Again, not hard to work around but seems like it all happens because they are older drivers. I’m afraid security features in Win11 will lock this down even more to where it is an issue where it breaks something since Logitech isn’t going to fix them.

This is the main thing I can see me from stop using the X65F stick for the Viper and the throttle for everything since I’ve also squirreled away two spares. I love the HOTAS!

Also I have been using your lift detents Oakdesign, so far they have been great, thanks for the design!

[white_fang]

@Lippy:

Support for Windows 10 will end in 2025 no more security updates.

Ok. Panic mode ON. :uham:

[drtbkj]

@white_fang:

Ok. Panic mode ON. :uham:

ROFL . My prediction: In a few years, when people start using it here and the price comes down (Yeesh), we’ll be saying “why did we fuss?”

[Ilmars]

@Snake122:

SST isn’t really a work around but Win10 throws the not verified software when installing. Slightly worried that Win11 security features will cause an issue with SST, but think that’s a not too much of a concern really. But since I was mentioning drivers I thought I would put “/SST” on there.

Away from the computer to confirm if I’m using 7.0.53.6, but the drivers have been problematic for me because they are not verified drivers. I had to do the dig into device manager and select the more generic named driver instead of the one Windows assigns. Again, not hard to work around but seems like it all happens because they are older drivers. I’m afraid security features in Win11 will lock this down even more to where it is an issue where it breaks something since Logitech isn’t going to fix them.

I’ve installed the 7.0.53.6 drivers and SST software several times and have never seen W10 throwing the not verified warning. I’ve only had 2 problems using the drivers and sofware. The first is that on two occasions the SST profiler seemed to lose the scan code for a single key stroke and didn’t transmit the key stroke from an assigned button. A reinstall of the drivers seemed to fix it, though. The second was trying to install the Vjoy virtual joystick drivers. For some reason the Vjoy installer doesn’t completely finish and the result was that the Saitek drivers were trashed. When I tried to reinstall the Saitek drivers, after completely uninstalling them, the reinstall process would not recognize that the X65F was plugged in. My only remedy was to go back to an earlier W10 system restore point. Be careful when trying the Vjoy drivers, create a W10 restore point first, just in case.