Along with other 24h2 issues surrounding upgrading to 24h2, MS announced that it was blocking automatic 24h2 upgrade to some Asus devices affected by known issues.
Blocks have also been put on a number of devices prior to this announcement about Asus. I strongly advice anyone at this time to apply the upgrade only if it is offered through WU. IF you do decide to force this upgrade, I also advise that you have a full system image in case things go south during the upgrade and you are unable to rollback or if issues arise after the rollback period.
Issues these blocked affected devices can experience if 24h2 is forced are disappearing mouse cursers, SSD related crashes, driver crashes, undeletable crash files, broken Clipboard, and broken internet connections.
AFAIK there is no one list available for what devices this upgrade negatively affects.
Yes, I know that. I read it. It's not just Asus. There are a number of others of different brands that MS is blocking as well. We are seeing threads every day about issues that MS is saying is caused by the upgrade for some. My post was simply a warning to those not being offered the upgrade through WU that there may well be a reason for why they aren't..
I am curious @glasskuter, I have an Asus Q504UAK Flipbook with a UX560UAK motherboard with an Intel i5 processor, with a UEFI BIOS. I am wondering if this combination of hardware the W11 24H2 update does not like this combination of hardware? Regardless if the storage used for W11 use is or are SSDs or HDDs?
Just a thought...
Looks like I will not be installing 24H2 any time soon! I am glad I saw this post before I installed the ISO of 24H2 I have.... thanks!
I have no way of knowing if your machine would be impacted by upgrading to 24h2 or not. If you want to do an inplace upgrade using the iso you downloaded, go for it. You may encounter no problems. If the upgrade fails, your machine should roll back to where you are now. But be prepared in case it doesn't. Make sure you create a full system image using one of the 3rd party imaging applications and make sure you create recovery media for whatever application you choose to use. Also test that you can boot from that media. This is a CYA tactic in case something goes wrong either during the upgrade or any problems that pop up after the upgrade. You can always get back to working condition by restoring the image.
It's not that you won't ever get offered 24h2 through windows update. It's that MS has put a temporary hold on releasing 24h2 to certain systems until whatever problems they've identified are worked out. That's why some systems are being offered the upgrade and some aren't.
MS have really made a dogs dinner of this 24H2 upgrade.
i have never come across an upgrade that has caused so many problems before its even installed.
I am glad I saw this post before I installed the ISO of 24H2 I have.... thanks!
