Failure to update Windows 10 (Home) from 21H2 to 22H2

Topic

New Reply

[Alex B]

Hello,

I’ve a Toshiba Satellite C855 that will not update to 22H2.

A month or 2 ago I updated the registry Target Release Version from 21H2 to 22H2 using Susan’s file.

Going through the Windows 10 ISO page and clicking on Update (for the past 2 or 3 months) continues to end with, “<i>Sorry were having trouble determining if your PC can run Windows 10.  Please close setup and run again.   Error Code: 0xc0000024.”  </i>

Before this it notes, “<i>CPU, Memory and disk all OK.”</i>

This machine has been running Windows 10 for several years now, so I don’t get it.

In desperation I even tried using the command prompt as admin and the following commands, which also failed (I’m not this smart; I just followed this video: https://youtu.be/1m2WdYbpG_U?t=4 which was actually about forcing an update to Windows 10).

net stop wuauserv

ENTER

net stop bits

ENTER

Then I renamed the Software distribution folder at C:\Windows\SoftwareDistribution\Download and created a new empty Download folder there.

Then back to the command prompt:

net start wuauserv

ENTER

net start bits

ENTER

wuauclt.exe/updatenow

ENTER

Finally, I used the Windows Creation Tool to make a bootable 22H2 USB drive for repairs; but I don’t see an option of installing this version – 22H2; while also preserving my current configuration and data etc.  Even though I’ve a backup I’d really rather not have to go thru that if I could at all avoid it.  But if it’s the only way, then I’ll take that advice too if someone lays out the path.

Any help is appreciated.

Thank you!

• This topic was modified 2 years, 1 month ago by Alex B.

Reply | Quote

Replies

Don’t boot from the usb. While in windows navigate to setup on the usb you created and run it.

1 user thanked author for this post.

Alex B

Reply | Quote

Start the computer win 22H1.
Insert the USB stick – it will appear as another drive letter in File Explorer.
Open File Explorer and navigate to the Drive,
Run setup.exe

It will give you the choice to keep your programs and data, keep only your data, or keep nothing.
Choose keep your programs and data

1 user thanked author for this post.

Alex B

Reply | Quote

@PKCano,
I ran setup.exe as indicated.  I did not see the options referenced and so proceeded as it made sense; and I ended back with the same notice of, “Sorry were having trouble determining if your PC can run Windows 10. Please close setup and run again.” but without an error code this time.  Thanks for the suggestion tho; much appreciated.

I’ll also add that Update Troubleshooter found nothing also.

Frustrating.

Reply | Quote

Run winver – what version and build does it indicate?
Check the Registry (actually look at the settings), Group Policy (if you have Pro) and be sure you are not blocking 22H2. If you need to find the settings, see the screenshots at the bottom of AKB2000016.
Are you running WUMgr or any other update controlling program? If so, check the settings.
Run chkdsk /f (you will need to reboot to do this)
then in an elevated Command Prompt run:
DISM /online /cleanup-image /restorehealth
then
sfc /scannow

Download Gibson Research’s InControl.
Place it on your desktop.
Set it for Windows 10 and 22H2.
Reboot.
Give it a day and see it you are offered 22H2 or you can run setup.exe on the USB drive from within Win10 22H1.

2 users thanked author for this post.

TechTango, Alex B

Reply | Quote

I’d been wondering why my Win10 21H2 machine wasn’t being offered 22H2. I had all the correct Registry settings (AFAIK), and Steve Gibson’s InControl was set to 22H2.

The trick was to Release Control in InControl and then search for updates in Windows Update Manager. Now 22H2 showed up. But setting InControl back to Take Control without actually installing 22H2, made 22H2 disappear from WuMgr’s listings.

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

2 users thanked author for this post.

Alex B, PKCano

Reply | Quote

Update:  (TLDR, I implemented everything in PKCano’s latest suggestions and it’s still failing to update).

After PKCano’s latest recommendation (Thank you PKCano!) same failure to update, and here are the requested details:
4/2/23

1) Ver 21H2 (OS Build 19044.2728), Windows 10 Home

2) Windows Update Registry entries checked out as indicated.

3) To my knowledge not running WUMgr or any other update controlling program; except I have controlled versions using Susan Bradley’s regedit files but that was last ran to update to 22H2.  I also verified WUMgr not listed in installed programs.  wushowhide reported No Hidden Updates.   Not sure what else to check or do…

4) Ran chkdsk /f, rebooted and failed to see any results.  Ran in an elevated Command Prompt:  DISM /online /cleanup-image /restorehealth  follwed by sfc /scannow.  sfc /scannow reported corrupt files and successfully repairing them.

5) Downloaded, installed and ran: Gibson Research’s InControl. (Seems way easier, more comprehensive, and less fuss that Susan’s regedits :D).  Set for Windows 10 and 22H2.  Rebooted and then tried looking for updates and also running the Windows 10 ISO page updater.  Still no love.

6) Based on @Cybertooth’s  comment; released control, rebooted and tried looking for updates and also running the Windows 10 ISO page updater.  Still no love.

7) The morning of 4/3/23 I even installed optional update KB5023773
resulting in the now Winver: Ver 21H2 (OS Build 19044.2788) and (as Einstein would say, insanely) repeated the update attempts resulting in the same effect as follows:

8) In all cases so far the attempted update process ends with the same non-de-script “Something went wrong” “Select Try again, and if that doesn’t work, contact Microsoft support for help. Error code 0xc0000024” and/or “Windows 10 Setup Sorry, we’re having trouble determining if you PC can run Windows 10. Please close Setup and try again.”

I get the above after, AFAICT anywhere from about 76-97% complete (after the failure it goes back briefly to the progress windows before exiting.

Short of any more ideas, I guess the question is should I retake control or not using InControl?  But as neither way seems to make a difference it would seem the better question and answer is some other solution.  Sigh.

Thank you to everyone who’s commented and provided suggestions.

 

 

 

Reply | Quote

Does the computer have lots of unused hard drive space, at least 20GB?  If you have not already done so I would start a question at the official Microsoft support https://support.microsoft.com/contactus/ as well.  If you are still having problems at the end of the year when Windows 10 2023 update comes, with a lot of luck that might help.

1 user thanked author for this post.

Alex B

Reply | Quote

@Energy SaVer:  Yes, plenty of free space:  344GB free of 465GB (500GB) on Crucial SSD.

Thank you for the Microsoft support recommendation.  Will do!

Reply | Quote

I used Windows Update Assistant to finally move from 21H2 to WIN 10 22H2. Build 19045.2728. I checked my settings/system and it showed 22H2. Checked WU but it wasn’t in the Feature updates history. Ran updates again which installed a security and cumulative updates for 22H2 plus updated the Feature updates history.

Reply | Quote

Since 22H2 is installed via an enablement package it does not show as a feature update.

--Joe

1 user thanked author for this post.

PDX5802

Reply | Quote

You are correct. Looked again on history, it wasn’t listed. But system definitely shows update to 22H2

Reply | Quote

PDX5802 wrote:

You are correct. Looked again on history, it wasn’t listed. But system definitely shows update to 22H2

Look under History – uninstall updates.

Reply | Quote

I am happy to report I’m now on Win10 Ver 22H2 – after it was offered when I checked for updates again this morning.  FWIW, In Control was off (I’d tried it both ways and this is probably just coincidence).

Thank you to all who made suggestions – especially PKCano!

1 user thanked author for this post.

PKCano

Reply | Quote