Last week Saturday I did clean installs of 24H2 on all four of my Windows 11 devices. No issues at all, install went smoothly and everything is running smoothly. I was thrown for a loop initially when I saw the install screens were a little different, when prompted, I opted to use the previous method on my first three installs, on the fourth I used the new way.
The only minor problem I’m having is Detector Tools Pro, the update utility for Escort radar detectors is crashing when I attempt to update the Defender (Red light cam/speed cam) database. But it’s probably an Escort problem. I only have that installed on one laptop, works fine on my Windows 10 desktop, but Escort’s stuff can be iffy at times. One nice thing, unlike with 22H2 and 23H2, for my two 2 in 1s, as soon as I paired the pens for each device the Pen Settings app installed immediately. In the past would have had to manually run the SP installer from HP for Wacom pen support and sometimes that wouldn’t work right the first time or two.
I’m still not sold on the Widows 11 taskbar, although better since 23H2 that you can uncombine and show labels but many thanks to the ExplorerPatcher folks for coming up with a Windows 10 style taskbar after MS removed the code in 24H2. I will be throwing them a 50 EUR donation in the coming days.
Can’t comment on the BitLocker stuff. I’ve been using BitLocker for years on everything and I don’t dual boot. For what I do in older versions of Windows and Linux, running them in VMWare is more than suitable for me. Just to minimize the risk of problems, I always unencrypt the boot drive prior to reformatting and reinstalling and then re-encrypt after everything is complete.
I did notice the just under 9 GB of Windows update files that won’t delete almost right off that bat. I have a very very specific routine when installing Windows and doing a Disk Cleanup after everything is installed and configured is one of my final steps. I ran Disk Cleanup 3 or 4 times on the first computer that finished and when it wouldn’t delete I did it on the next computer and same thing so figured it was a bug. After a Disk Clean up using the GUI, I run this cmd for good measure, and what usually takes a few minutes to complete, completed almost instantly, so I doubt it did anything. Dism.exe /online /Cleanup-Image /StartComponentCleanup.
A few of the articles I've read on this issue, make it seem like this is a problem if you do an in place update or get 24H2 via Windows Update, but it is also a problem if you do a clean install.
I have had no BSODs, disappearing mouse cursors or networks issues.