Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[gt94sss2]

Microsoft has clarified that Windows 11 24H2, unlike Windows 11 23H2, is a full OS swap and can not merely be enabled via an Enablement Package (EKB).

Aside from that, the company has also explained how managed devices can be upgraded directly from Windows 10 to Windows 11 24H2, using the target version capability in the Windows Update for Business deployment service and feature update deployments via Windows Autopatch.

As always, Microsoft has urged users to upgrade immediately to the latest OS version as Windows 10 will reach the end of support on October 14, 2025. As for those on previous Windows 11 versions, Microsoft says that systems must be on the May 2024 non-security preview to be able to upgrade to Windows 11 24H2.

https://www.neowin.net/news/microsoft-details-windows-11-24h2-upgrade-compatibility-info-full-features-for-office-pcs/

https://techcommunity.microsoft.com/t5/windows-it-pro-blog/windows-11-version-24h2-what-s-new-for-it-pros/ba-p/4259108

[Alex Atkin UK]

Had a few Crashes, but overall nice and stable

This is obviously the definition of "nice and stable" in the modern world of "alternative facts".

[HPsauce]

I've updated two of my secondary systems from 23H2 and both had Windows Update problems after the upgrade.
HOWEVER I did use a "new" trick I discovered to bypass the hardware checks (product server option) so reverted and used my older methods (registry etc.).
All seem fine now and not very different.

[HPsauce]

Just to add that since then I've successfully used the "product server" option several times to upgrade to 24H2 without any issues so I suspect there was a problem with the very early downloads that was quickly fixed by Microsoft.

[tiffy]

Although I have never tried the revision I've decided to stick with 23H2 on my Win 11 PC in the mean time until all bugs are resolved.
My main, daily use desktop PC is still running Win 10 Pro which I still prefer and intend to retain this until the bitter end!

Have found this very informative YouTube video listing a number of ways to avoid/delay for longer periods any specific Windows upgrade, have implemented on my Win 11 PC, same methods can also be applied to Win 10:
https://www.youtube.com/watch?v=nEjkPacrJ00
 

[jelv]

I've updated both my desktop and my laptop to 24H2 and haven't had any issues on either.

[HPsauce]

I hit an interesting "problem" with 24H2 the other day, helping a friend of mine update his PC from 22H2. 
He'd asked me what his "end of life" warning messages were about; this was despite me asking him back last Autumn if he had any systems still on 22H2 - "I don't think so" was his answer - WRONG!
First we updated his laptop, which wasn't that old, but equally wasn't full W11 spec. No problem.
Then we went for the Dell desktop, which started updating fine, then I noticed something odd....

Even though he'd long ago updated it with an SSD and 8GB ram, so it ran fine, I spotted a windows XP label on the box! 
A quick Google of the model confirmed it had an older processor that doesn't have SSE4.2 instruction extensions or POPCNT! Needed for 24H2 
Fortunately I was able to cancel the update before completion and it rewound it back to 22H2, then I updated it to 23H2 which I fortunately had a copy of, even though for some inexplicable reason his system needed the US English download not the UK/International English one. 

He was then happy that it would run for a few more months and he'd look to buying a new system when Windows 12 appears. I agreed.
Then a few days later we had a massive lightning strike about 100 yards up the road from me - multiple trees shredded!
My house was unaffected, nothing even tripped, but my friend was 50 yards away the other side and most houses there has significant electronic damage. His router was fried, as was his PC that was next to it on a cabled LAN connection. So my W11 upgrades were a waste of time. BT have had an engineer in the area for several days now sorting out the many problems created.

I did do some diagnosis of his stricken PC and it would actually boot, the CPU and ram survived as did the hard disks. The video card was toast as was the LAN port and all but one USB port so it was effectively unusable. The SSD and HDD inside, with lots of family photos, were fine surprisingly. 

[HPsauce]

I've hit an "interesting" 24H2 issue that killed three of my PCs yesterday!
All the same old model, the ones that had the weird power-related issues that were cured by turning off the EU-mandated power-saving modes.

So, if you got an HP Z600 or something using similar disk controllers, read on, you may be hit similarly:

My "test" system, that I was doing various jobs on yesterday (NOT reconfiguring, just using it) suddenly refused to boot with a disk read error very early in the boot - no logo yet, just a blank screen then the message.
After various investigations I determined that it WASN'T the disk so it had to be the I/O controller (or as I discovered later probably a driver issue). That system has other pending hardware issues so I decided it was time to replace it and started researching what to buy. Until......
An hour or two later my wife's PC did exactly the same when turned on, followed shortly by my main PC! 

I decided to sleep on it as I was faced with potentially rebuilding all 3 systems. The finger was definitely pointing at a recent big Windows 11 update though.   
Today I started trying various recovery/update processes on the test system, all to no avail, until I thought "what about BIOS settings?"
Checking the setup the BIOS by default goes into RAID mode with AHCI though I don't use the RAID features. The alternative is good old IDE.

Set to IDE my test system did indeed start to boot, logo, swirling circle etc. but quickly crashed.
After a few iterations of recovery I eventually (possibly with the help of a recovery USB drive) got it to boot into Safe Mode (with networking) and it looked much better. Back into standard mode and it was then working, with a few odd niggles that needed sorting.
So somehow Safe Mode had got it to load the IDE drivers and make them available.
I did try it back in RAID/AHCI mode but it had the same error, so I decided IDE was the way forward. Performance tests (NovaBench) showed minimal differences. 

I moved on then to my wife's PC and put it straight into IDE mode. Incredibly it sorted itself out after a few reboots, I didn't need to force it into safe mode. I did see a message about it removing a recent update. It currently seems to have a "glitch" on Windows Update but I'll sort that eventually.

Finally my main PC which is rather more complex. Again, straight into IDE mode but I did need to force it into safe mode myself, it couldn't cure itself.
It's all running fine now as far as I can tell so far. 

So it looks like the latest (May, KB5058499) update of 24H2 has something in it that doesn't work well with the RAID controller on the HP Z600 motherboard. 

[Chrysalis]

Yes safe mode does that, but its not well documented.  I think safe mode will early load all i/o drivers as a precaution, and if it detects it used a driver not configured in early load then it automatically adds it to early load, so then next you boot normally it will work.
If you have standard AHCI in the bios without RAID, then thats the ideal option, Windows does have tis own standard AHCI driver, it was the RAID option giving you the problem.

I learnt this when I first switched from AHCI to NVME.  The system wouldnt boot as NVME wasnt in early load, I then tried safe mode it booted, then it booted fine normally after.

[HPsauce]

If you have standard AHCI in the bios without RAID, then that's the ideal option, Windows does have its own standard AHCI driver, it was the RAID option giving you the problem.

Unfortunately the BIOS only gives IDE or AHCI with RAID, but it's working OK now.

And yes, I recall from long ago that bit about safe mode loading missing drivers when your hardware has changed, useful feature.