Windows 11 24H2 rollout issues (1 Viewer)

[Dennis Nicholls]

I just got through updating my household's desktops and laptops to 24H2. I found that the Latitude 3500s and Optiplex 3060s would only be offered the 24H2 update on Windows Update if the "get the latest updates" switch was toggled ON.

The 24H2 supposedly has a large amount of code re-written in Rust language, which means replacing a lot of code. Once downloaded it takes a long time to install, and quite a bit of time after restarting. Expect at least an hour. Installing is very CPU intensive. An i3-8145U laptop showed 100% CPU use on Task Manager quite often, while staying under 50% on an i5-8500 desktop. The install on the laptop took a good deal longer to complete.

In general no major issues after the update. Biggest bug was deleting the printer driver for my Canon MF462dw AIO. I re-installed the driver and the printer came back, both printing and scanning. I keep the Settings icon on the Taskbar and it removed that too. I had to put Settings back there.

 

[Malcolm R]

Not sure what's going on with Windows updates, but my Win 10 system hasn't updated in over a month. Updates all seem to fail. I see something about WinRE partition size and have tried to follow their instructions to adjust this, but it doesn't seem to work.

 

[Dennis Nicholls]

Are you talking about Windows Recovery partition? If it's too small Windows may have issues. On one of my machines it stopped being able to make Win 7 Backups. I had to enlarge it using 3rd party app "MiniTool Partition Wizzard".

 

[Malcolm R]

Yes. It's worked fine for years, now all of a sudden the partition is apparently too small. I followed their manual instructions to resize the partition, but that didn't seem to work.

 

[Dennis Nicholls]

IIRC one of my machines on installation had a 400MB recovery partition. All the others had larger ones. I boosted it up to 700MB and all of a sudden Win 7 Backup started running again.

 

[Malcolm R]

Microsoft guidance says it needs to be at least 250MB, but apparently there are machines where it's set smaller than that.

EDIT: I did some more reading on a MS support forum and think I may know where I went wrong in the process. Will have to try the process again maybe this weekend.