Two More Reasons Why You May Not Want to Install Windows 11 24H2 Just Yet!

It seems that there are issues with sfc /scannow and Storage Sense after upgrading to this years annual feature update.

Keep an eye out for fresh content uploaded regularly.

#windows11 #windows10 #windowsupdate #windows11updates #googlechrome #bravebrowser #microsoftedge #mozillafirefox #vivaldibrowser #powertoys #howtowindows #speedupwindows #googleapps #windows12 #chromerefresh2023 #edgeprojectphoenix #wallpapers #windowsconcepts #linux #brentech #wheretechismadesimple

[Funtasters]

Just released but already has 6 known issues, windows without issues is not windows. 😅

[IvoMimica]

Running 24H2 over here, updated thru Installation Assistant everything went smooth, after first boot had another update (KB5043178) that left me in build 26100.1882. Glad to know the Windows Update Cleanup bug is happening to everyone, hopefully they fix it soon.

[andrewquinn]

Still more than happy on Windows 10 22H2 it runs flawless and there is no reason what so ever to change it

[BufuMeister]

I dont want to jinx myself, but luckily I havent had any blue screen of death problems or anything like that yet. I am now worried if I should have waited until it got available through check for updates instead of downloading it right away. Only time will tell I guess but so far so good.

[TtnumShld]

1:56 I've had this issue on my Windows 10 laptop since 2022, though I've never gotten a BSOD or any other form of bugs as result of this. I've also had storage sense issues over the past 4 years of using Windows 10, but they eventually resolved themselves.

[BartierCardia]

Im experiencing the same issue with sfc even after restarting and using dism

[PWingert]

I have seen at least two videos indicating that BSODs occur for some people. As a result, I am currently pausing updates for the full 4 weeks on my home machines. Then I will decide if I want to install 24H2 and expect it to continue to be an optional update that should be ignored for the next 60 - 90 days until MS can get its first major update to 24H2 released. It has been decided at work that we will implement a full testing process and delay installation for one year.

[hubertherbut]

I have encountered both problems. After updating with Assistant I did clean install from ISO last night as well - sfc behaviour is still the same.

[soheilbeygi]

I installed a clean version of 24h2 on my laptop, while SFC did find a problem the first time, the second time it didn't find any. Updating windows instead of doing a clean install has always caused weird problems in my experience.

[Aranimda]

I got the SFC issue as well after upgrading from 23H2 to 24H2.

[abc_cba]

I installed it and lost the ability to run the WSL Ubuntu on my Win 11 ever since.
😿

[arckie]

Exact same issues here. Repeated corrupt files found from sfc /scannow, and 8.63gb of undeletable windows update cleanup files. multiple installs, via assistant, via clean iso from MS, via latest build from uupdump, all the same.

[MikeHL]

The comment section is full of bunch bad words on 24h2. Remember, this is a new version and had just released 2 days ago so bug and issuses are something that cannot be avoided. Like ios 18 or macos 15 update. Wait until the update more stable usually takes a few weeks.

[GummyDeer]

i was also wondering why i am getting that error.I also ran dism again and again with restarts but it said operation successful for different dism commands

[botbr]

OMG the sfc scannow was also always giving me corruption files as well, i was going crazy xd

[DeanosRides]

I got issues current with the "Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5044284)"

Doesn't like that install and keeps undoing the update on reboot.

Guess we wait till next Tuesday to see if there is a fix...

[davidwalker]

sfc /scannow is a 26100.1882 error hopefully it be fixed on patch Tuesday

[The_Debug_Life]

Found this to be true in the release preview channel on the insider build. Cmd command line sfc scannow had that issue

[JorgeReyGMartinez]

Does this only happen to the in-place upgrades from previous versions and not the freshle installed one?

[spede]

My SFC /Scannow came back fine after the 24H2 update, started having the same issue as you after installing the Cumulative KB5043178 update