Windows 10: Windows update 22H2 at update 0% for hours.

I started the Windows 11 22h2 update, using a thumb drive to get enough space and now it is frozen. It is saying Working on updates 0% Please keep your computer on. It has been like this for hours and the thumb drive is super hot. I am not sure how to stop it and just keep windows 10. Please Help.

:)

 

Intel Updates Core 2 Quad Q9550 to E-0 Stepping

We continue our Monday news list with another Intel story that brings to our attention information concerning the company and more specificly its 2.83GHz Core 2 Quad Q9550 chips that will move from the current C-1 to the newer E-0 stepping. The updated chips will start selling on August 22nd, featuring the following changes:

• New SSpec and MM numbers for the converting products
• CPUID will change from 0x10677 to 0x1067A
• Package change to Halide free package

Apart from that, the new stepping CPUs will not include any other changes. Of course, like most new stepping parts a BIOS update will be needed.


Product Change Notification 108663 - 00

Source: TechConnect Magazine

 

How to get the Windows 10 2022 Update version 22H2 Win Update

If you can't install it from windows update you can try to install it manually, it's the same KB5015684 obtained with windows update.

Windows 10 Version 22H2 is coming in October 2022 ---> KB5015684 Provides Quick Windows 10 22H2 Upgrade - Ed Tittel On the Ed Tittel page click on the links DeskModder.de or .MSU x64 version of the upgrade.

KB5015684 Funktionsupdate auf die Windows 10 22H2 (19045) [Manueller Download] - Deskmodder.de

Do dism and sfc /scannow commands before and/or after installing it.

 

How to get the Windows 10 2022 Update version 22H2 Win Update

I wish things are that simple. My error code was 0x80246017, and I don't have KB5020435 installed so it's a dead end. BTW, MS lists like 6 or 7 error codes of the format 0x8024xxxx on the "troubleshooting WU problems", and when you chose next step, it suggests generic steps: run WU troubleshooter, check if your disk has no errors, is your remote disk is accessible, etc. Same as MS community; each similar error has completely different cause and (re)solution.
MS in notorious for this- if it works then OK, if it doesn't then good luck.