Windows 24H2 upgrade?

1

This morning, Windows decided that I needed to upgrade my shop computers to the 24H2 version. By the time I saw what it was doing, it was too late. All four shop computers. Ugh.
Let the fun begin. I will update you guys on the results or problems. It is my fault. I come into the shop, turn them all on in the morning, and go about my business. Bam they got me…

2 Likes
2

It took out my network settings between shop computers. I’m working on it, but other than that, it seems to be okay. CutControl and FireControl are both working.

3 Likes
3

I’m dealing with a black screen - explorer.exe is running but not working. I have to run programs from task manager or cmd prompt. Windows settings and other features (device manager, regedit…) inop.

Can’t find my bitlocker code, and never uploaded to MS account. I need that or I have to suck it up and nuke my HD and loose everyting. I have never been very good at navigating and file transfer from cmd prompt.

4

Sorry my friend. Windows updates suck. They roll out crap that has bugs. Then they play dumb.

5

I have no idea what some of this means, but somehow an Adjustable Rate Mortgage (ARM) is required to run it. I guess I’m out since my home has no mortgage. :wink:

From Wikipedia.

System requirements

[edit]

Version 24H2 introduces modified system requirements, for some systems, for the first time since the release of Windows 11, as follows:

  • A x86-64-v2 CPU supporting SSE4.2 and POPCNT CPU instructions is now required, otherwise the Windows kernel is unbootable.[9] (Only affecting systems bypassing or exempt from the TPM 2.0 requirement.)
  • IoT Enterprise editions (LTSC and non-LTSC) have officially eliminated a TPM and UEFI requirement, and dropped the minimum DirectX version down to 10 (version 12 was previously required on 23H2).[7][10]
  • The new IoT Enterprise LTSC edition drops the minimum required RAM down to 2 GB, and storage space down to 16 GB.[7][10]
  • ARMv8.1 is now required for ARM variants, dropping unofficial support for ARMv8.0.[11] On ARMv8.0 CPU, the Windows kernel is unbootable.
  • ARM variants drop support for 32-bit ARM applications.[12] Only 64-bit ARM applications will run.
6

Pretty much any current computer will accept this version. I recommend waiting a while to download it—too many bugs exist. The network issue is a total pain in the ass. Lots of people have reported the blue screen of death after the update. Please use caution. I’m sure any older unit that can’t load Windows 11 is exempt from this.
They are forcing this out for some god knows reason.

2 Likes
7

To make people buy new computers. Consume, Consume, Consume.

Same as Apple puts a bug in their phone OS to rapid drain the battery when the phone gets to a certain age. Make them buy a new one since you can’t replace the batteries anymore.

Consume consume consume.

4 Likes
8

Any company that does thing like that or adds any designed / planned obsolescence to their products should be dissolved, liquidated and the shareholders and board members should also be personally fined.

I am a large believer in the right to repair and any companies agaisnt this should not exist.

We in Canada are making law about it

And Louis Rossman had been lobbying in the USA for years.

And these software “end of life” scenarios should included under designed / planned obsolescence.

5 Likes
9

That’s awesome. Hopefully that will help the rest of us like when the EU mandated USB C so Apple finally caved.

I thought we scored a minor victory recently. I think there was a ruling that they must make their proprietary tools and parts available at least.

1 Like