For most people, it's probably okay but the 24H2 update has been a mess to a point where it even had to be recalled once. It's the slowest rollout of an update they've done I think. It was released officially all the way back in October and they are still having a lot of issues, it's still being very slowly rolled out, it's still hitting snags that means they are pulling it from being offered to some people and certain configurations. It's having lots of issues with a handful of Ubisoft games that straight up can't start on 24H2. Personally, I'd just leave it for another 3-6 months even though I am on a 24H2 clean install but nothing in 24H2 is worth upgrading over. Has no interesting features, no performance gains, you won't gain anything by upgrading. 

So unless you desperately just want the version number to say 24H2, just wait. 

 

14 minutes ago, Sethos said:

For most people, it's probably okay but the 24H2 update has been a mess to a point where it even had to be recalled once. It's the slowest rollout of an update they've done I think. It was released officially all the way back in October and they are still having a lot of issues, it's still being very slowly rolled out, it's still hitting snags that means they are pulling it from being offered to some people and certain configurations. It's having lots of issues with a handful of Ubisoft games that straight up can't start on 24H2. Personally, I'd just leave it for another 3-6 months even though I am on a 24H2 clean install but nothing in 24H2 is worth upgrading over. Has no interesting features, no performance gains, you won't gain anything by upgrading. 

So unless you desperately just want the version number to say 24H2, just wait. 

 

Sethos right I would be very careful upgrading.... I have 24H2 on my p.c and it has been acting super strange and slow with strange glitches I'm not sure if its messing with memory too but it does feel like it sometimes it could be just me but i don think this update is good.

1 hour ago, Reset XPDR said:

As long as you don't want to use an HP Reverb G2 VR headset, which is no longer supported in 24H2 due to WMR being deprecated in this build, you should be fine.

Thanks, not using this Headset !

cheers 😉

39 minutes ago, Sethos said:

For most people, it's probably okay but the 24H2 update has been a mess to a point where it even had to be recalled once. It's the slowest rollout of an update they've done I think. It was released officially all the way back in October and they are still having a lot of issues, it's still being very slowly rolled out, it's still hitting snags that means they are pulling it from being offered to some people and certain configurations. It's having lots of issues with a handful of Ubisoft games that straight up can't start on 24H2. Personally, I'd just leave it for another 3-6 months even though I am on a 24H2 clean install but nothing in 24H2 is worth upgrading over. Has no interesting features, no performance gains, you won't gain anything by upgrading. 

So unless you desperately just want the version number to say 24H2, just wait. 

 

Yes, i think i will wait until the point i have to install it to go on with Windows 11, see no problems at all with my current build so why should i hurry up with the new build - thanks to all replys, much appreciated !

cheers 😉

I had an issue with my Logitech rudder pedals/drivers.  To get them to work again, I had to disable Memory Integrity' in Windows Security. 

2 hours ago, Tom Wright said:

I've got it and no issues. There was one weird one where I had to manually install a driver for my Saitek/Logitech rudder pedals again as Windows couldn't download the right one and it kept giving an error.

Same thing happened to me with a Saitek throttle quadrant. All my other controller drivers loaded fine.

No VR here so, no problem and I've been on 24H2 since a while.

Edited January 3, 20251 yr by jcomm

Hello,

If you use a camera (or computer) that uses the samba protocol, you will no more be able to copy your pictures from it.
Because Samba policy has changed with 24H2.
Workaround :
Enable guest access in local Group Policy to allow unauthenticated SMB connections:
Press Win+R, type gpedit.msc, then press Enter.
Access:Computer Configuration > Administrative Templates > Network > LANMAN Workstation
Double-click Enable insecure guest connections.
Select Enabled, then click OK.

No problem using 24H2 with MSFS 2024 on my computer.

The big thing is keeping an eye on when your current version falls off support.  There's nothing wrong with staying on an older version as long as it is still supported.  

It looks like Win 11 23H2 falls off support in November this year.  

https://learn.microsoft.com/en-us/windows/release-health/windows11-release-information

There’s a similar topic on the Windows forum. It might be helpful to merge them.

I had problems with GoFlight GF166 displays plus Lossless Scaling requires a new version.

5 hours ago, kerosene31 said:

There's nothing wrong with staying on an older version as long as it is still supported.  

It looks like Win 11 23H2 falls off support in November this year.  

absolutely. that's why I am still on Windows11 - 23H2 (with none of the 24H2 related problems) with HP Reverb G2 VR headset and plan on keeping it at least until November 2025, by which time I plan on getting the then latest non-WMR VR headset (MeganeX or some such) and possibly only then update Windows 11.  

I need some help from the W11 boffins here and this nothing to do with simming.

I installed 24H2 a few days ago. First impressions, cool, no big upsets. Then I hit a snag.

It seems that 24H2 has managed to destroy the computer's connectivity over wifi. What do I mean?
I have various movie/music etc files on the computer. I could access them through a variety of apps such as VLC, Foobar2000 and the like and enjoy the view on the home theatre tv set.

Since 24H2 I simply cannot access anything neither from my mobile nor from the tv. I keep getting asked to input a domain name and password.
After numerous days of trying different solution suggested on various websites I finally decided to restore the computer to 23H2.
It is now all back to normal.

This is, obviously, not a solution as support for 23H2 ends in November and I would prefer be up to date with security issues rather than risk anything especially now that we are constantly connected.

Does anyone have any ideas?

Cheers.