Very strange behavior with Build 24H2

[DevNull]

I "upgraded" to 24H2 and 2 things happened:
1 - My DL4100 My Cloud NAS became inaccessible, fixed with a PowerShell script ("Set-SmbClientConfiguration -EnableInsecureGuestLogons $true"

2 - A few days after moving to 24H2, I was watching a video using VLC, after 10 or so minutes it froze and an error appeared "Cannot play the file E:\Files\Movies\filename, it does not exist". I looked using Explorer and there was no file with that name but I knew that there was, since it played for 10+ minutes. A search of drive E came up empty, so I searched all drives and it was found in D:\Files\Movies. There has never been a folder with that name on that drive so of course it would not play from there, Restart and Shutdown did nothing, Drive D and E tested fine. I went back to Build 23H2 and everything went back to normal. My conclusion is that 24H2 is a hot mess,

[Taliseian]

I had issues with 24H2 myself.  First off, I was blocked due to having a 2TB WD NVME drive.  Then, when that was lifted I had issues with other drivers and software.

I ended up going back to 23H2 and I use GRCs InControl so I stay on 23H2.  I can still get any 23H2 updates (like the one that was listed for the recent Patch Tuesday).

[mkol]

24H2 is full of bugs. One major bug I found is reporting incorrect space of C drive.