I update my Win 10 computers with a cumulative update file and did not
notice one of the computers had not successfully updated since April 2024.
I should of been checking the updates listing and I would have seen this.
The computer is stuck at 19045.5011. It appears this started with the installation of KB5001716. I have been working on this on and off for the
10 days. I used MediaCreationTool_22H2 to create a USB Flash drive and ran that and got a message the computer was up to date. I did make a Macrium image backup so I can restore the computer to its broken state. I am going to use MediaCreation on one of the good computers to create a Flash drive
and try that with the hope I do not have to use my Macrium backup. Any suggestions?
I update my Win 10 computers with a cumulative update file and did not
notice one of the computers had not successfully updated since April 2024.
I should of been checking the updates listing and I would have seen this.
The computer is stuck at 19045.5011. It appears this started with the installation of KB5001716. I have been working on this on and off for the
10 days. I used MediaCreationTool_22H2 to create a USB Flash drive and ran that and got a message the computer was up to date. I did make a Macrium image backup so I can restore the computer to its broken state. I am going to use MediaCreation on one of the good computers to create a Flash drive
and try that with the hope I do not have to use my Macrium backup. Any suggestions?
<Bill>
I update my Win 10 computers with a cumulative update file and did not
notice one of the computers had not successfully updated since April
2024. I should of been checking the updates listing and I would have
seen this. The computer is stuck at 19045.5011. It appears this
started with the installation of KB5001716. I have been working on
this on and off for the 10 days. I used MediaCreationTool_22H2 to
create a USB Flash drive and ran that and got a message the computer
was up to date. I did make a Macrium image backup so I can restore
the computer to its broken state. I am going to use MediaCreation on
one of the good computers to create a Flash drive and try that with
the hope I do not have to use my Macrium backup. Any suggestions?
<Bill>
Ignore this. I bit the bullet and reinstalled so now it is current
other than I have to rebuild it and try to remember all the things I
have done over the years.
I update my Win 10 computers with a cumulative update file and did not
notice one of the computers had not successfully updated since April
2024. I should of been checking the updates listing and I would have
seen this.
The computer is stuck at 19045.5011. It appears this started with the installation of KB5001716. I have been working on this on and off
for the 10 days. I used MediaCreationTool_22H2 to create a USB Flash
drive and ran that and got a message the computer was up to date.
I did make a Macrium image backup so I can restore the computer to its
broken state. I am going to use MediaCreation on one of the good
computers to create a Flash drive and try that with the hope I do not
have to use my Macrium backup.
On 12/18/2024 3:58 PM, Bill Bradshaw wrote:
I update my Win 10 computers with a cumulative update file and did not
notice one of the computers had not successfully updated since April 2024. >> I should of been checking the updates listing and I would have seen this.
The computer is stuck at 19045.5011. It appears this started with the
installation of KB5001716. I have been working on this on and off for the >> 10 days. I used MediaCreationTool_22H2 to create a USB Flash drive and ran >> that and got a message the computer was up to date. I did make a Macrium >> image backup so I can restore the computer to its broken state. I am going >> to use MediaCreation on one of the good computers to create a Flash drive
and try that with the hope I do not have to use my Macrium backup. Any >> suggestions?
You didn't say if KB5001716 failed or not. Are there other KB updates that too have failed.
Here's the usual stuff you might have tried and that winston generally recommends.
<https://www.partitionwizard.com/news/kb5001716-fails-to-install.html>
Bill Bradshaw wrote:
I update my Win 10 computers with a cumulative update file and did not
notice one of the computers had not successfully updated since April
2024. I should of been checking the updates listing and I would have
seen this. The computer is stuck at 19045.5011. It appears this
started with the installation of KB5001716. I have been working on
this on and off for the 10 days. I used MediaCreationTool_22H2 to
create a USB Flash drive and ran that and got a message the computer
was up to date. I did make a Macrium image backup so I can restore
the computer to its broken state. I am going to use MediaCreation on
one of the good computers to create a Flash drive and try that with
the hope I do not have to use my Macrium backup. Any suggestions?
<Bill>
Ignore this. I bit the bullet and reinstalled so now it is current other than I have to rebuild it and try to remember all the things I have done
over the years.
<Bill>
Paul wrote on 12/19/24 12:11 AM:
On Wed, 12/18/2024 6:54 PM, Bill Bradshaw wrote:Way too much work..
Bill Bradshaw wrote:
I update my Win 10 computers with a cumulative update file and did not >>>> notice one of the computers had not successfully updated since April
2024. I should of been checking the updates listing and I would have
seen this. The computer is stuck at 19045.5011. It appears this
started with the installation of KB5001716. I have been working on
this on and off for the 10 days. I used MediaCreationTool_22H2 to
create a USB Flash drive and ran that and got a message the computer
was up to date. I did make a Macrium image backup so I can restore
the computer to its broken state. I am going to use MediaCreation on >>>> one of the good computers to create a Flash drive and try that with
the hope I do not have to use my Macrium backup. Any suggestions?
<Bill>
Ignore this. I bit the bullet and reinstalled so now it is current other >>> than I have to rebuild it and try to remember all the things I have done >>> over the years.
<Bill>
<cough>
There is no escape from the Borg.
Or so I'm reliably informed.
The problem is, the install disc doesn't know how to set up
the Recovery Partition properly. This means any SafeOS update
is going to get stuck the same way, at some point. If they had
fixed the install materials, this would not have happened.
But of course they didn't fix the install materials.
The SafeOS that was installed by the installer DVD, also
did not self-document properly. the "WinReVersion" Reg_SZ
string did not get created, so you cannot tell what the
revision of WinRE.wim is in the Recovery Partition. The logic
uses that entry, to decide whether the SafeOS receives
an update or not. There is now a folder in the WinRE.wim that
marks the release of the file, but not all softwares
that do this work, are going to inject that. That might
be in a very recent SafeOS fix.
Since Windows 10 is end of life, KB5001716 is a multi-faceted
patch. Not only will it add a "band" to the screen, advertising
Windows 11 and indicating Windows 10 is going out of date, but
it also does a SafeOS update.
This means, there is a very good chance, even on your shiny
new OS, the KB5001716 is going to show up... and it is going to
get stuck (not finish) because of the difficulty with the
procedure to make a new WinRE.wim file and create the registry
key that documents the current version of it.
There *IS* a way to fix this. But you rushed ahead and
did the Win10 clean install, without instructions, so there
was no chance to warn you how to fix it up.
You can create partitions on the disk drive, such that
the Windows 10 installer cannot make a Recovery Partition.
If you succeed at this mission, the reagentc will create
the file in the C: partition. The C: partition *always*
has space, since the C: partition is huge, compared to the
inadequate size of the Recovery Partition. While creating
a SafeOS solution inside the C: partition is the very
embodiment of stoopid, it DOES solve the problem of the
updates getting stuck.
Otherwise, you still have to address the care and feeding
of your Recovery Partition, if you want a good mixture
of functionality (emergency boot capability) plus the
windows Update not getting jammed.
*******
Notice that none of this behavior, is anywhere near SaaS.
It's a joke, that individual users have to Work THIS HARD
to keep their updates working. On the one hand, I can see
the argument that "automation is hard for us". They've
made such a mess, I would not want to be the person
having to work with a ton of different disk configs
(Dell, HP, thankyou), and resize stuff. But the Microsoft
architecture team made this mess, and somebody has to pay
to clean it up. It would appear to be a "Casual indifference"
is behind all of this. The indifference that comes of
throwing away 400,000,000 users.
We're still here, and we await your next move.
Paul
Just use the available instructions to increase the size of WinRE partition to 1GB or 2 GB at the expense of the C: Windows partition
or if clean installing from scratch
Use 22H2 booted media(or mounted ISO) and Windows installed advanced settings to create the 4 required GPT partition(with WinRE 1 GB or 2 GB) then install Windows 22H2.
- even easier to use a script to create the partitions especially when pre-written scripts for use in Diskpart are readily available.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 507 |
Nodes: | 16 (2 / 14) |
Uptime: | 196:03:02 |
Calls: | 9,965 |
Calls today: | 7 |
Files: | 13,828 |
Messages: | 6,356,760 |