• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Windows 11 24H2 yes or no?

Joined
May 3, 2019
Messages
2,404 (1.06/day)
System Name BigRed
Processor ryzen 7 7800X3D
Motherboard Asus Rog Strix B650E-E Gaming WIFI
Cooling Thermalright Phantom Spirit 120 EVO
Memory Corsair Vengeance 2x16GB DDR5 6000c30
Video Card(s) MSI RTX 3080 Gaming Trio X 10GB
Storage M.2 drives WD SN850X 1TB 4x4 BOOT/WD SN850X 4TB 4x4 STEAM/USB3 4TB OTHER
Display(s) Dell s3422dwg 34" 3440x1440p 144hz ultrawide
Case Corsair 7000D
Audio Device(s) Logitech Z5450/KEF uniQ speakers/Bowers and Wilkins P7 Headphones
Power Supply Corsair RM850x 80% gold
Mouse Logitech G604 lightspeed wireless
Keyboard Steelseries Apex Pro
Software Windows 10 Pro X64
Benchmark Scores Who cares
If you are on windows 11, will/do you install 24H2? I have seen there a certain problems with it, so do you just stick to 23H2?
 
i clean installed 24h2 day it officially came out on my work laptop as dual boot with linux mint cinnamon, i have had 0 issues with either of them. Linux Mint Cinnamon does seem to be more smooth overall though, so Win11 bloat is a real thing imo.
 
I guess it's depends from person to person and hardware you are using....personally I updated tried it and reverse it back on 23H2 'tho I am using "oldish" X299 Platform and when I did some benchmarking tests results was usually worst from 5%-7% on 24H2 so I just returned back on 23H2
 
It's good if you use the LTSC version.

No chance I'd ever use standard Windows these days. Horrific.
 
I still haven’t gotten it as an available update on my personal PC and when I do I’ll probably hold off for a few months. It usually takes a bit for all the bugbears to be cleaned up with these big feature updates.
That said, I did try the LTSC on a couple of work PCs and the 24H2 does seem a tad snappier than the debloated 23H2 Pro. Not an apples to apples comparison exactly, but it’s what I’ve got.
Then again, I am one of those weird people who’s been running 11 since RTM and had no real issues after customizing it to my liking. *shrug*
 
It's good if you use the LTSC version.

No chance I'd ever use standard Windows these days. Horrific.
Seems 24H2 is the first Windows 11 LTSC, yet people have been claiming to use LTSC on Windows 11 before 24H2. Interesting.

But anyway the only major issue I have heard of is related to a few WD SSDs. There is already a released fix for it.
 
Seems 24H2 is the first Windows 11 LTSC, yet people have been claiming to use LTSC on Windows 11 before 24H2. Interesting.
I mean, some people also claim that they are Napoleon, their dad works at Nintendo and other silly things. The last LTSC was indeed 10 based one. Maybe people used one of those scuffed custom ISOs that are floating around and thought that they are LTSC since they are usually majorly gutted.
 
I have heard that 24H2 installs Recall as a part of explorer. Once I get a decent period of free time (kinda busy these days), I'll probably shrink my Windows partition on my XPS 15 and install Linux Mint in that space (I'll keep Windows around for some games w/anticheat). I've also started reading the book 1984, and I realize that having something on your PC taking screenshots at random intervals is far too similar to Big Brother (even if you can supposedly disable it).
 
@jak_2456
It’s completely inert by default, at least as far as we can see. And is seemingly disable-able.

As this is relevant to Windows 11, I'm bring this subject over to this thread;


I am currently installing to test this. Will chime in with everyone to verify. I have no reason to doubt Chris, but just hadn't seen it yet.

EDIT:
On fresh install with an ISO freshly downloaded from microsoft, I'm not finding ReCall at all. No settings like those shown in the video, no services and nothing in the Task Manager or Task Scheduler.

CoPilot was there, but easily removed. Chris did mention that it was on his "inside" build. Maybe insiders builds have it? But ATM, it's not been pushed out to end users.
Additionally, when running the DISM command listed in the video( Dism /online /Disable-Feature /FeatureName:"Recall" ), it did state that the feature was removed successfully.

This would imply that Recall is present on the system, but not enabled by default, which is in line with what microsoft promised to do.

I will keep a watchful eye on this one and follow up with new developments.

@lexluthermiester
Can confirm, if Recall is present (and it seems it is) it’s fully inert by default on non-supporting hardware and easily removed/disabled via PS. No services or processes were running and nothing in Task Scheduler or Events to imply it working. Question is how it will behave when/if MS decides to extend the support to more configs.
I am annoyed that it isn’t listed under System Components in Settings, though. Doesn’t matter if inert or not - it should be. Then again, seems like it’s less of a component/app and more of a layer on top of the explorer.
 
It’s completely inert by default, at least as far as we can see. And is seemingly disable-able.
Just the thought of them trying to implement it is enough to give me cold feet about keeping Win11 on my PC. I do not trust Microsoft.
 
I've got a pre-release build of 24H2 and I think I'll be keeping that, unless the release build of IoT Enterprise also lacks the Recall bullshit, which this one does.

Zero issues.
 
FYI it automatically enables bitlocker on almost all drives. make sure to disable that ransomware.
 
I don't understand the question.

If your Apple or Android phone or tablet offers a new OS update, do you refuse it? If your smart TV offers an update, do you refuse it? If your security app offers an update, do you refuse it?

I get putting off the update for a week or so to see if any issues arise. But of course I am going to install it! Keeping our systems current is one of, if not "the" best way to keep it, our data and our personal information secure. Keeping our computers current is "the" fundamental part of "practicing safe computing".

Yes, there has been the occasional update that caused problems. But it is important to note there are 1.6 Billion Windows systems out there, and each one became a unique machine within a couple minutes after its very first boot. This happened as the unique networking configuration was setup, as users configured their own unique "personalizations", setup their own security, installed and configured their own apps, printers, drives and partitions, USB devices, motherboards, RAM, graphics cards, etc. etc. etc. Then there are those users who dink with the default settings, then blame Microsoft when those changes hose their systems. :rolleyes: :kookoo: :(

So OF COURSE there will be some problems. But every time there is, the numbers are blown WAY WAY out of proportion, with a single report gong viral and being repeated 100s and 1000s of times making the problem "appear" much worse than it really is. :(

The problem is, if there are just 0.1% of the users who genuinely have a problem with an update (and that is a high estimate, BTW), that is still, 1.6 million upset users. And 1.6 million upset people can make a lot of noise - especially when all the wannabe IT journalists, bloggers, and Windows haters jump on board and repeat those angry complaints.

It would seem all those wannabe journalists, bloggers and Windows haters expect Microsoft to test every update on every possible (1.6 billion) configuration before releasing it - as poor, inadequate in-house testing is almost always blamed. :(

I have 5 systems here and several more I am responsible for. I have never, not once, ever, since migrating from W7 to W10/11 had any Windows Update "brick" one of those computers. Not once! Worse case is the occasional (yes, scary!) lock up that was cleared by a simple reboot :). There have been a couple failed updates that were automatically rolled back by Windows that were resolved in a week or two by MS sending out another update. But never, not once, ever did I have to manually roll-back an update, or worse, reinstall the OS due to a botched update.

Frankly, with 1.6 billion unique Windows computers out there, I am amazed, and must give credit and kudos to Microsoft, that there are not more actual problems. I guess some expect perfection 100% of the time, every time. I wonder if those critics can walk on water? :rolleyes:

So yes, of course, I will install the update. While I don't expect any problems, with major updates, I may keep my fingers and toes crossed - but I will update. Should something go drastically wrong, I have my current backups. Don't you?
 
YES

I have it already installed via the ISO image over my existing w11 pro installation. The iso image installer refused to start because tpm was not active. I had issues with my asus mainboard with tpm. I had to reset my Bios. Than do a bios update. Reset the bios and than install the iso image. My asus mainboard has a long term tpm fault, once disabled it can not be renabled anymore, except with a bios reset.

Certain issues with high contrast mode which I had to reset after the installation was finished. (See the other main topic on w11 24h2 update where I posted those screenshots.)
Up to 8 reboots what I remember. Very bad installer.

I use windows 11 pro 24h2 only for gaming. No issues detected. I do have the windows update paused for 5 weeks usually.
My main operating system is something else.

I do not have bitlocker - as before. I checked with the recall key combination which I saw in a topic. That recall feature does also not exists because bitlocker is not enabled.

I don't understand the question.

I expect that my windows 11 looks the same after an update. Which was not the case. See those screenshots I posted in that another topic on the main page. Those screenshots were just taken after the installer had finished. Nothing was changed before and after I started the setup from the official microsoft windows 11 iso.

I do not change much anymore in windows 11 pro. My main operating system is something else. It's just installed so i can play the windows only games.

I do not get the fan boy style argument. Windows is buggy since I remember. To be honest I can not remember any issues with Windows 3.11 or earlier. I do remember lots of bugs with Windows 95B and later. At work and at home with my small sample size.
 
Last edited:
Seems 24H2 is the first Windows 11 LTSC, yet people have been claiming to use LTSC on Windows 11 before 24H2. Interesting.

But anyway the only major issue I have heard of is related to a few WD SSDs. There is already a released fix for it.
They used a prerelease, its been out for months.
 
If your Apple or Android phone or tablet offers a new OS update, do you refuse it? If your smart TV offers an update, do you refuse it? If your security app offers an update, do you refuse it?
I always delay major macOS and iOS/iPadOS by nine months. Nowadays I upgrade the week before Apple WWDC in June. That is the best assurance that I will get a mature and relatively stable operating system.

Jumping to the latest and greatest operating system for security reasons ignores the fact that Apple offers security updates for the previous two operating system. Apple typically releases these at the same time as their updates for the current OSes.

Thus my Apple handheld devices and Mac are running fully patched iOS 17 and macOS 14.7 Sonoma, not iOS 18 and 15 Sequoia.

I get putting off the update for a week or so to see if any issues arise. But of course I am going to install it! Keeping our systems current is one of, if not "the" best way to keep it, our data and our personal information secure. Keeping our computers current is "the" fundamental part of "practicing safe computing".
For Windows, I tend to upgrade around the same timeframe, about nine months after the release date. So I'll probably move to Windows 11 24H2 in June 2025. Like Apple, Microsoft will offer security updates for the previous two versions, 23H2 and 22H2.

If you read Windows Latest or Bleeping Computer, new Patch Tuesday updates are rife with problems. The major updates are even worse and Microsoft frequently pulls back distribution. Here's one example for 24H2:


The problem is you don't know what flavor dogchow Microsoft is going to serve up at any time. Taking a measured and cautious approach to installing major updates from whatever software vendor you are using is a critically important option for people who favor stability over new features. This isn't just good practice for Joe Consumer. In all of the corporate places I've worked the IT staff carefully tested updates on disposable systems before pushing out the patches to production systems (servers and employees' machines). Thus Patch Tuesday was never a flurry of new software and frequently updating systems. That was usually saved for later in the week (off hours), over the weekend or sometimes the following week.

This is why some software offer ESR (Extended Support Release) branches like Mozilla Foundation for Firefox. Security patches are good. Security patches on stable software are great.

Unstable software is for fools. Like brand new major updates of Windows, macOS, Linux, whatever. It's just a sysadmin timesink that can be easily avoided by staying on the previous release and enjoying ongoing security patches until you have enough confidence to upgrade.

Trust is earned.

Unfortunately Microsoft squandered all of theirs a looooooooong time ago. Ahahahahahahahahahaha!!!!

:):D:p
 
Last edited:
I do not get the fan boy style argument.
And I don't understand the need to degrade the thread with personal insults.

Defending something does not make one a fanboy. I never, not once said I like these updates. I never even said I like Windows or Microsoft.

I merely pointed out that keeping our computers updated is one of the best ways to keep it secure. That implies that failing to keep it current puts users at risk as updates typically include security patches, and bug fixes too.

FTR, there are lots of things I do NOT like about W10 or W11 (and every version before). But I'm not constantly whining about them. And I have been very critical about Microsoft shoving unwanted changes down our throats too.

Some changes I refuse to live with. For that reason, I use Start10 on my W10 systems to bring back W7's familiar start menu and desktop. And I use Start11 on my W11 systems to do the same, plus I use Explorer Patcher to bring back the invaluable (IMO) Quick Launch toolbar. But I will still update Windows and keep it updated to ensure I have the latest security patches.

And I will still defend Microsoft (or anyone else, whether I like them or not) when unjustly accused. That still will not make me a fanboy of them.

For Windows, I tend to upgrade around the same timeframe, about nine months after the release date.
If that works for you, then fine. But personally, I think 9 months is way too long. If an update has serious flaws, there will start to be reports almost immediately as millions and millions of computers are updated. That is plenty of time for the word to get out (at least for me as I tend to pay attention to that sort of news). If problems are reported, and my research show it might affect me, I may then delay the update a little longer but most likely, MS will already be on it and will have pulled the update.

Now for these HUGE updates where Microsoft rolls out the update over several weeks, then yeah, it might be prudent to wait more than a week or two. But again, I have to go by the fact I have never, not once, on any system I am responsible for (and that is about 3 dozen, including my own), had an update brick a computer. But IMO, waiting longer than a month is unnecessary.

I will point out waiting to install updates plays right into the badguy's mitts. They seek out unpatched systems and sadly, frequently find them. :(
 
Installed it the least intended way on my "DLSS" system and despite TPM2 and all that nonsense being disabled and not very optimal activation method being chosen I'm running a 100% solid and stable system. Some intermittent latency spikes do occasionally happen but this is most likely my GPU VRAM is asking for it. Can't say for sure for now but it's likely a hardware issue.

Didn't bother to actually debloat it, just disabled Edge, OneDrive, Copilot and whatever useless BS spawns out of the box.
 
You mean removable? It's disabled be default.
Nah, I mean disable-able. We talked about it in the Win 11 thread - the “removal” via PS doesn’t really remove the function itself on the whole since it’s apparently baked into the Explorer. I assume it “removes” some triggers and an id or two, but doesn’t outright delete the feature. It’s semantics, really, I just usually say “remove” when something is actually fully wiped.
Basically splitting hairs though.
 
Nah, I mean disable-able.
@jak_2456 was commenting on ReCall. I've tested this.
We talked about it in the Win 11 thread - the “removal” via PS doesn’t really remove the function itself on the whole since it’s apparently baked into the Explorer. I assume it “removes” some triggers and an id or two, but doesn’t outright delete the feature.
The jury is still out on that. I tried re-enabling it and that failed when I denied access to the internet. This directly indicates that a full removal took place and likely a deletion.
It’s semantics, really, I just usually say “remove” when something is actually fully wiped.
To me, removed indicates that the function is no longer workable and can not be re-enabled without patching from an external source. The term "Deleted" when it's completely erased from the system.
Basically splitting hairs though.
I disagree. The use of differing vocabulary defines specific distinctions.
 
if you like OS level keyloggers go for it.
 
if you like OS level keyloggers go for it.
That has not been a thing for a while for VERY serious legal reasons. Rather than risk being sued into the poor house and being shut down by multiple governments, microsoft wisely choose to remove that crap. The only service that was doing it was "diagtrack", which is easily removed and deleted anyway.
 
That has not been a thing for a while for VERY serious legal reasons. Rather than risk being sued into the poor house and being shut down by multiple governments, microsoft wisely choose to remove that crap. The only service that was doing it was "diagtrack", which is easily removed and deleted anyway.
i was talking about recall, but im interested to know what they removed?
 
Back
Top