Replies

The article that Martin sourced has been edited to state that it’s not related to 24H2.

Editor’s note 9.18.2024 – The dates conveyed below are for our regular monthly servicing updates for supported versions of Windows 11 and unrelated to when Windows 11, version 24H2 will be generally available.

1 user thanked author for this post.

Travasaurus

It seems to be related to the em dash that they used in the title. The forum software is altering the dashes in the URL. There should be four dashes between ‘macos’ and ‘even’.

1 user thanked author for this post.

Alex5723

I’ve been running 24H2 in Release Preview since June, thankfully it has been fine for me. That’s not to say that anyone should install it immediately, just that it hasn’t given me any trouble at all.

I haven’t heard any confirmation either way but I’m presuming that it will be a full feature upgrade rather than an enablement package. Usually when enablement packages are used, the build number is only incremented slightly, such as 19041-19045 being used for the Windows 10 builds from 2004 up to 22H2, or Windows 11 22H2 to 23H2 being 22621 to 22631. But 24H2 is build 26100.

1 user thanked author for this post.

PL1

Linux definitely doesn’t feel “more modern”, it’s based off concepts from the 1970s!

If I were dual-booting Linux, I’d probably just turn Secure Boot off, it doesn’t really have much benefit over there from what I can see.

3 users thanked author for this post.

rc primak, Cybertooth, jburk07

I didn’t get to use it until 1997 (in our equivalent of middle school) but I loved it at the time.

I got hit by this on a new build HP, I can’t remember the exact model but it was a brand new 15″ EliteBook. I was setting it up to deploy to a user and upon installing updates, I got a POST error, claiming that the Secure Boot keys had been tampered with and were reverted. Upon reboot, I was prompted for the BitLocker key.

Alex5723 wrote:

Nibbled To Death By Ducks wrote:

There is something tragicomically ironic about the fact that an A/V company was responsible for this train wreck

https://www.askwoody.com/forums/topic/crowdstrike-agent-got-updated-and-may-be-triggering-bsods/page/3/#post-2689315

There is something tragicomically ironic that an OS can’t handle a faulty file and crashes.
That is how it should have been done

Microsoft tried to change this in x64 but Symantec and McAfee lost the plot and accused them of trying to lock them in favour of Defender. So Microsoft had to open up APIs to allow them to continue their kernel-patching ways. If that hadn’t been forced on Microsoft, then this may not have happened.

3 users thanked author for this post.

Steve, rc primak, Alex5723

I have to agree with Alex5723 here. The messaging platforms you can use largely depends on what your contacts use. WhatsApp is huge in Ireland and it’s hard to avoid as a result. I don’t know anyone on Signal or Telegram and only heard of Threema on this thread!

This doesn’t really surprise me. Microsoft already restricted Wi-Fi 6E (6 GHz) support to Windows 11. Despite that, a single Intel driver slipped through the cracks that let it work on Windows 10.

64-bit versions of Windows (which would be the vast majority now) no longer support 16-bit DOS applications directly. You might need to run it in an emulator like DOSBox instead.

1 user thanked author for this post.

Artie

While Terminal defaults to PowerShell, it can be whatever you want it to be, as explained by @TryLinux above. I defaulted mine to cmd as I’m more old school, but you can even default it to a WSL terminal if you want!

It used to be the case that you could, provided that you didn’t install Outlook on more than one of them (it would complain if you tried to have both Outlook 2003 and 2007 for example). But now, there’s all sorts of issues with C2R and non-C2R versions co-existing, as well as mixing 32-bit and 64-bit. I personally wouldn’t do it.

1 user thanked author for this post.

AWRon

n0ads wrote:

Ah, that explains why the first two returned a blank value on my PC.

It wasn’t an OEM purchase but a DIY build where I had to actually purchase Windows to install it (originally Window 7 Pro, upgraded to Windows 10 Pro.)

Exactly, self-builds or devices which didn’t ship with Windows 8 or later will return blank values.

The article is wrong in that this doesn’t give you the “current” product key, just the key that the machine shipped with. So if you upgraded from 10 Home to 10 Pro for example, the key these commands return will be the original Home key.