On my desktop which has win10 Pro, for the last week I've tried over 10
times to install a feature update and it won't finish. Does that really
matter? I have a lot of features already. :-)

I've tried doing the update as soon as windows is started, before
running other programs.

Specifically it say Feature update to windows 10, version 22H2, Pending
download.

And after I click on Go, or whatever, it downloads nicely but Install
stops at 20%. Googling found that as a complaint years ago, but the
suggestions didn't work for me.

micky wrote:
> On my desktop which has win10 Pro, for the last week I've tried over 10
> times to install a feature update and it won't finish. Does that really
> matter? I have a lot of features already. :-)
>
> I've tried doing the update as soon as windows is started, before
> running other programs.
>
> Specifically it say Feature update to windows 10, version 22H2, Pending
> download.
>
> And after I click on Go, or whatever, it downloads nicely but Install
> stops at 20%. Googling found that as a complaint years ago, but the
> suggestions didn't work for me.

How long did you wait?
Those updates take ages .I've never had one hang, but I've often cursed
the time taken.

Ed

In alt.comp.os.windows-10, on Wed, 27 Sep 2023 16:00:51 -0400, micky
<NONONOmisc07@fmguy.com> wrote:

>On my desktop which has win10 Pro, for the last week I've tried over 10
>times to install a feature update and it won't finish. Does that really
>matter? I have a lot of features already. :-)
>
>I've tried doing the update as soon as windows is started, before
>running other programs.
>
>Specifically it say Feature update to windows 10, version 22H2, Pending
>download.
>
>And after I click on Go, or whatever, it downloads nicely but Install
>stops at 20%. Googling found that as a complaint years ago, but the
>suggestions didn't work for me.

I think this is a fairly standard? message that eventually it gives,

There were some problems installing updates, but we'll try agian later.
If you keep seing this and want to search the web or contact support for
information, this may help: (0x8007025d)

In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:16:41 +0100, Ed Cryer
<ed@somewhere.in.the.uk> wrote:

>micky wrote:
>> On my desktop which has win10 Pro, for the last week I've tried over 10
>> times to install a feature update and it won't finish. Does that really
>> matter? I have a lot of features already. :-)
>>
>> I've tried doing the update as soon as windows is started, before
>> running other programs.
>>
>> Specifically it say Feature update to windows 10, version 22H2, Pending
>> download.
>>
>> And after I click on Go, or whatever, it downloads nicely but Install
>> stops at 20%. Googling found that as a complaint years ago, but the
>> suggestions didn't work for me.
>
>How long did you wait?

I should have said that. Until I got the bad message that I just quoted
in my follow-up post.

>Those updates take ages .I've never had one hang, but I've often cursed
>the time taken.
>
>Ed

Today would be the 11th failure.

On 9/27/2023 3:34 PM, micky wrote:
> In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:16:41 +0100, Ed Cryer
> <ed@somewhere.in.the.uk> wrote:
>
>> micky wrote:
>>> On my desktop which has win10 Pro, for the last week I've tried over 10
>>> times to install a feature update and it won't finish. Does that really
>>> matter? I have a lot of features already. :-)
>>>
>>> I've tried doing the update as soon as windows is started, before
>>> running other programs.
>>>
>>> Specifically it say Feature update to windows 10, version 22H2, Pending
>>> download.
>>>
>>> And after I click on Go, or whatever, it downloads nicely but Install
>>> stops at 20%. Googling found that as a complaint years ago, but the
>>> suggestions didn't work for me.
>>
>> How long did you wait?
>
> I should have said that. Until I got the bad message that I just quoted
> in my follow-up post.
>
>> Those updates take ages .I've never had one hang, but I've often cursed
>> the time taken.
>>
>> Ed
>
> Today would be the 11th failure.
A few times with problem updates doing a sfc /scannow fixed things.

Other times I went with brute force and and created a fresh W10 install
flash drive and did a windows "repair" install and let that get rid of
the problem.

In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:35:11 -0500,
GlowingBlueMist <zapbot@truely.invalid> wrote:

>On 9/27/2023 3:34 PM, micky wrote:
>> In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:16:41 +0100, Ed Cryer
>> <ed@somewhere.in.the.uk> wrote:
>>
>>> micky wrote:
>>>> On my desktop which has win10 Pro, for the last week I've tried over 10
>>>> times to install a feature update and it won't finish. Does that really
>>>> matter? I have a lot of features already. :-)
>>>>
>>>> I've tried doing the update as soon as windows is started, before
>>>> running other programs.
>>>>
>>>> Specifically it say Feature update to windows 10, version 22H2, Pending
>>>> download.
>>>>
>>>> And after I click on Go, or whatever, it downloads nicely but Install
>>>> stops at 20%. Googling found that as a complaint years ago, but the
>>>> suggestions didn't work for me.
>>>
>>> How long did you wait?
>>
>> I should have said that. Until I got the bad message that I just quoted
>> in my follow-up post.
>>
>>> Those updates take ages .I've never had one hang, but I've often cursed
>>> the time taken.
>>>
>>> Ed
>>
>> Today would be the 11th failure.
>A few times with problem updates doing a sfc /scannow fixed things.

Sounds good. I did this and in short time I got to 61% complete of the
Verification phase of the scan. And then I got the message:

Windows Resource Protection could not perform the requested operations.

Sounds serious.

>Other times I went with brute force and and created a fresh W10 install
>flash drive and did a windows "repair" install and let that get rid of
>the problem.

I'll need some time to do that.

If I never finish this feature update, will my life gradually get worse?
Or will/might other updates still install?

On 9/27/2023 4:32 PM, micky wrote:
> In alt.comp.os.windows-10, on Wed, 27 Sep 2023 16:00:51 -0400, micky
> <NONONOmisc07@fmguy.com> wrote:
>
>> On my desktop which has win10 Pro, for the last week I've tried over 10
>> times to install a feature update and it won't finish. Does that really
>> matter? I have a lot of features already. :-)
>>
>> I've tried doing the update as soon as windows is started, before
>> running other programs.
>>
>> Specifically it say Feature update to windows 10, version 22H2, Pending
>> download.
>>
>> And after I click on Go, or whatever, it downloads nicely but Install
>> stops at 20%. Googling found that as a complaint years ago, but the
>> suggestions didn't work for me.
>
> I think this is a fairly standard? message that eventually it gives,
>
> There were some problems installing updates, but we'll try agian later.
> If you keep seing this and want to search the web or contact support for
> information, this may help: (0x8007025d)
>

0x8007025d

"Going by an article by Windows support, the error code 0x8007025D
stands for ERROR_BAD_COMPRESSION_BUFFER."

Now you're going to have to re-bore the block and
put in bigger pistons and rings.

"This error signifies that an error occurred somewhere during the
decoding of the installation data, forcing the process to stop."

Yeah, sure, I believe you... Hmmm.

I wonder if this install material was downloaded via DoSvc from another PC in the house ?
One machine can share Windows Update files with another, if you tick the right boxes.
I've never managed to make that work.

It's hard to imagine an error in transmission, from the source, but I suppose
that is possible. (There might be CRC per packet, as well as a hash over the
entire file, the file would be checked as it's put on the disk drive, and checked
when it comes off the disk drive.)

It smells of "something else is doing that", but... what ?

The odds of RAM being bad in just the right spot, are pretty low.

*******

If the machine has a history of problems, or, you know of other
symptoms, it would help to know that part.

Paul

On 9/27/2023 4:00 PM, micky wrote:
> On my desktop which has win10 Pro, for the last week I've tried over 10
> times to install a feature update and it won't finish. Does that really
> matter? I have a lot of features already. :-)
>
> I've tried doing the update as soon as windows is started, before
> running other programs.
>
> Specifically it say Feature update to windows 10, version 22H2, Pending
> download.
>
> And after I click on Go, or whatever, it downloads nicely but Install
> stops at 20%. Googling found that as a complaint years ago, but the
> suggestions didn't work for me.
>

You can download the Windows 10 DVD image, which will be 22H2, and
install that. If you download the ISO9660 file, you can right-click
the file and select "Mount" from the top of the context menu, and
a virtual DVD drive will appear in File Explorer. (You don't have to
waste any optical media for this, saving a buck.)

If you double-click Setup.exe on the virtual DVD drive letter,
that will start an in-place Upgrade. That will take the place
of your "thingy that breaks at 20%".

Some of the ISO files Microsoft is releasing, won't fit on single layer
media. For example, today I tried to use this.

Name: Windows10-x64-22H2.iso
Size: 4,783,996,928 bytes (4562 MiB)
SHA256: F39A34B8884E03D1CA6770D0186ED86F3010A5DAF859307EE24C97A228BC178C

That's on the order of 83 megabytes too much, for a single layer DVD.
I ended up putting that on a USB stick (as I was doing a Clean Install) with

https://web.archive.org/web/20181004075559if_/https://download.microsoft.com/download/C/4/8/C48F6E20-FE20-41C6-8C1C-408FE7B49A3A/Windows7-USB-DVD-Download-Tool-Installer-en-US.exe

which is a wee bit of a pain in the ass to use. If you find bugs in it,
the source is available :-) It's like it was not written by Microsoft.
The USB stick must be prepped just right, or the stick will be rejected.
It's like getting a kid who won't eat his broccoli, to eat his broccoli.

https://web.archive.org/web/20200602085130if_/https://download.microsoft.com/download/C/4/8/C48F6E20-FE20-41C6-8C1C-408FE7B49A3A/wudtsource.zip

Rufus.ie is smoother. But the reason I look at alternatives, is to find
something which doesn't beat up the USB stick so much.

*******

While you can do this (in-place install), you'll never really know what was broken
at the 20% mark. And you'll also never know whether that kind
of symptom will come back (if it was due to hardware issues).

I only pass along the info about the Clean Install media, in case you're
ever baffled by a Windows DVD not fitting on a DVD :-) You don't need a Clean Install
in this case, and just running the Setup.exe from the virtual DVD is good enough.

Paul

In article <uf2oov$3ghbd$1@dont-email.me>, GlowingBlueMist wrote...
>
> On 9/27/2023 3:34 PM, micky wrote:
> > In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:16:41 +0100, Ed Cryer
> > <ed@somewhere.in.the.uk> wrote:
> >
> >> micky wrote:
> >>> On my desktop which has win10 Pro, for the last week I've tried over 10
> >>> times to install a feature update and it won't finish. Does that really
> >>> matter? I have a lot of features already. :-)
> >>>
....

> A few times with problem updates doing a sfc /scannow fixed things.
>

If SFC fails, try using DISM first.

https://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-
with-the-sfc-and-dism-commands/

--

Phil, London

micky wrote:
> On my desktop which has win10 Pro, for the last week I've tried over 10
> times to install a feature update and it won't finish. Does that really
> matter? I have a lot of features already. :-)
>
> I've tried doing the update as soon as windows is started, before
> running other programs.
>
> Specifically it say Feature update to windows 10, version 22H2, Pending
> download.
>
> And after I click on Go, or whatever, it downloads nicely but Install
> stops at 20%. Googling found that as a complaint years ago, but the
> suggestions didn't work for me.

There's a Windows Update Troubleshooter that's rather buried out of
sight. It worked for me once, after I'd found it.
Settings/ Update & Security/ Troubleshoot/ Additional Troubleshooters/
Windows Update.

Give it a try.

Ed

In alt.comp.os.windows-10, on Thu, 28 Sep 2023 12:08:03 +0100, Philip
Herlihy <PhillipHerlihy@SlashDevNull.invalid> wrote:

>In article <uf2oov$3ghbd$1@dont-email.me>, GlowingBlueMist wrote...
>>
>> On 9/27/2023 3:34 PM, micky wrote:
>> > In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:16:41 +0100, Ed Cryer
>> > <ed@somewhere.in.the.uk> wrote:
>> >
>> >> micky wrote:
>> >>> On my desktop which has win10 Pro, for the last week I've tried over 10
>> >>> times to install a feature update and it won't finish. Does that really
>> >>> matter? I have a lot of features already. :-)
>> >>>
>...
>
>> A few times with problem updates doing a sfc /scannow fixed things.
>>
>
>If SFC fails, try using DISM first.
>
>https://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/

Thanks. It also suggests restarting your PC in Safe Mode and running sfc
again. I always forget safe mode.

And it summarizes things at the start:

Key Takeaways
Open Command Prompt or PowerShell as administrator, then run "sfc
/scannow" to fix corrupted Windows System Files. If SFC fails to run
properly or cannot repair the files, run "DISM /Online /Cleanup-Image
/RestoreHealth" to fix any remaining issues.

Well, for now, I skipped running sfc in safe mode and went straight to
DISM/ I restarted the computer and ran it, and I got:

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19042.844

==== It got to 55.4%.

Error: 4448

The WOF driver encountered a corruption in the compressed file's
Resource Table.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

So this is the middle of that file, and I think the error is noted in
the middle of this excerpt, especially in those lines that you can find
by Finding the word error . There are 7 such lines, but I don't
think they show exactly where the error is or what do next. The error
message above mentions the compressed file's Resource Table. But it
doesn't say which compressed file. ???

2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
to add the commands from provider: OfflineSetupManager
2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
registered commands for the provider: OfflineSetupManager.
2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
to add the commands from provider: SysprepManager
2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
registered commands for the provider: SysprepManager.
2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
to add the commands from provider: Edition Manager
2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
registered commands for the provider: Edition Manager.
2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
to add the commands from provider: SetupPlatformManager
2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
registered commands for the provider: SetupPlatformManager.
2023-09-28 15:52:38, Info DISM DISM Package Manager:
PID=4624 TID=12652 Processing the top level command
token(cleanup-image). -
CPackageManagerCLIHandler::Private_ValidateCmdLine
2023-09-28 15:52:38, Info DISM DISM Package Manager:
PID=4624 TID=12652 Attempting to route to appropriate command handler. -
CPackageManagerCLIHandler::ExecuteCmdLine
2023-09-28 15:52:38, Info DISM DISM Package Manager:
PID=4624 TID=12652 Routing the command... -
CPackageManagerCLIHandler::ExecuteCmdLine
2023-09-28 15:52:38, Info DISM DISM Package Manager:
PID=4624 TID=12652 CBS session options=0x40100! -
CDISMPackageManager::Internal_Finalize
2023-09-28 15:55:15, Info DISM DISM Package Manager:
PID=4624 TID=12636 Error in operation: (null) (CBS HRESULT=0x80071160)
- CCbsConUIHandler::Error
2023-09-28 15:55:15, Error DISM DISM Package Manager:
PID=4624 TID=12652 Failed finalizing changes. -
CDISMPackageManager::Internal_Finalize(hr:0x80071160)
2023-09-28 15:55:15, Error DISM DISM Package Manager:
PID=4624 TID=12652 Failed processing package changes with session option
CbsSessionOptionRepairStoreCorruption -
CDISMPackageManager::RestoreHealth(hr:0x80071160)
2023-09-28 15:55:15, Error DISM DISM Package Manager:
PID=4624 TID=12652 Failed to restore the image health. -
CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80071160)
2023-09-28 15:55:15, Error DISM DISM Package Manager:
PID=4624 TID=12652 Failed while processing command cleanup-image. -
CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80071160)
2023-09-28 15:55:15, Info DISM DISM Package Manager:
PID=4624 TID=12652 Further logs for online package and feature related
operations can be found at %WINDIR%\logs\CBS\cbs.log -
CPackageManagerCLIHandler::ExecuteCmdLine
2023-09-28 15:55:15, Error DISM DISM.EXE: DISM Package
Manager processed the command line but failed. HRESULT=80071160
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Found the OSServices. Waiting to finalize it until
all other providers are unloaded. -
CDISMProviderStore::Final_OnDisconnect
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Found the OSServices. Waiting to finalize it until
all other providers are unloaded. -
CDISMProviderStore::Final_OnDisconnect
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Found the PE Provider. Waiting to finalize it until
all other providers are unloaded. -
CDISMProviderStore::Final_OnDisconnect
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Finalizing the servicing provider(DISM Package
Manager) - CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Package Manager:
PID=4624 TID=12652 Finalizing CBS core. - CDISMPackageManager::Finalize
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Disconnecting Provider: DISM Package Manager -
CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Finalizing the servicing provider(MsiManager) -
CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Disconnecting Provider: MsiManager -
CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Finalizing the servicing provider(IntlManager) -
CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Disconnecting Provider: IntlManager -
CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Finalizing the servicing provider(IBSManager) -
CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Disconnecting Provider: IBSManager -
CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Finalizing the servicing provider(DriverManager) -
CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Disconnecting Provider: DriverManager -
CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Finalizing the servicing provider(DISM Unattend
Manager) - CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Disconnecting Provider: DISM Unattend Manager -
CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Finalizing the servicing provider(SmiManager) -
CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Disconnecting Provider: SmiManager -
CDISMProviderStore::Internal_DisconnectProvider
2023-09-28 15:55:15, Info DISM DISM Provider Store:
PID=4624 TID=12652 Finalizing the servicing provider(AppxManager) -
CDISMProviderStore::Internal_DisconnectProvider

In alt.comp.os.windows-10, on Thu, 28 Sep 2023 19:11:13 +0100, Ed Cryer
<ed@somewhere.in.the.uk> wrote:

>micky wrote:
>> On my desktop which has win10 Pro, for the last week I've tried over 10
>> times to install a feature update and it won't finish. Does that really
>> matter? I have a lot of features already. :-)
>>
>> I've tried doing the update as soon as windows is started, before
>> running other programs.
>>
>> Specifically it say Feature update to windows 10, version 22H2, Pending
>> download.
>>
>> And after I click on Go, or whatever, it downloads nicely but Install
>> stops at 20%. Googling found that as a complaint years ago, but the
>> suggestions didn't work for me.
>
>There's a Windows Update Troubleshooter that's rather buried out of
>sight. It worked for me once, after I'd found it.
>Settings/ Update & Security/ Troubleshoot/ Additional Troubleshooters/
>Windows Update.
>
>Give it a try.

Roger, willco.

"Troubleshooting couldn't identify the problem."

plus a list of 4 potentional issues that were checked.
and a list of 4 other potential issues that were checked.
All were followed by "Issue not present".

Detection details.
IsPostback_RC_PendingUpdates IsPostback: False

Service Status
Problem with BITS service : The requested service has already been
started. System.Management.Automation.RemoteException More help is
available by typing NET HELPMSG 2182.
System.Management.Automation.RemoteException

And when in the CMD window I type NET HELPMSG 2182, I get
The requested service has already been started.

>Ed

In alt.comp.os.windows-10, on Thu, 28 Sep 2023 00:24:39 -0400, Paul
<nospam@needed.invalid> wrote:

>On 9/27/2023 4:32 PM, micky wrote:
>> In alt.comp.os.windows-10, on Wed, 27 Sep 2023 16:00:51 -0400, micky
>> <NONONOmisc07@fmguy.com> wrote:
>>
>>> On my desktop which has win10 Pro, for the last week I've tried over 10
>>> times to install a feature update and it won't finish. Does that really
>>> matter? I have a lot of features already. :-)
>>>
>>> I've tried doing the update as soon as windows is started, before
>>> running other programs.
>>>
>>> Specifically it say Feature update to windows 10, version 22H2, Pending
>>> download.
>>>
>>> And after I click on Go, or whatever, it downloads nicely but Install
>>> stops at 20%. Googling found that as a complaint years ago, but the
>>> suggestions didn't work for me.
>>
>> I think this is a fairly standard? message that eventually it gives,
>>
>> There were some problems installing updates, but we'll try agian later.
>> If you keep seing this and want to search the web or contact support for
>> information, this may help: (0x8007025d)
>>
>
>0x8007025d
>
> "Going by an article by Windows support, the error code 0x8007025D
> stands for ERROR_BAD_COMPRESSION_BUFFER."
>
>Now you're going to have to re-bore the block and
>put in bigger pistons and rings.
>
> "This error signifies that an error occurred somewhere during the
> decoding of the installation data, forcing the process to stop."
>
>Yeah, sure, I believe you... Hmmm.
>
>I wonder if this install material was downloaded via DoSvc from another PC in the house ?

No, I woudln't know how to do that if I wanted to, and I wouldnt' want.
to.

>One machine can share Windows Update files with another, if you tick the right boxes.
>I've never managed to make that work.
>
>It's hard to imagine an error in transmission, from the source, but I suppose
>that is possible. (There might be CRC per packet, as well as a hash over the
>entire file, the file would be checked as it's put on the disk drive, and checked
>when it comes off the disk drive.)
>
>It smells of "something else is doing that", but... what ?
>
>The odds of RAM being bad in just the right spot, are pretty low.
>
>*******
>
>If the machine has a history of problems, or, you know of other
>symptoms, it would help to know that part.

No, it's been fine. It's a refurbished HP Elite Desk from Amazon. They
had at least 3 refurbishers doing them, maybe 4 or more, depending on
what day you looked at the Amazon ad page.

Do you remember almost 2 years ago when it wouldn't start, for months. I
got all kinds of repair programs -- I forget their names -- and they
didnt' work and I was going to write the refurbisher, since he was the
last one to work on it, but I couldn't figure out which one it was and I
might have failed to write it somewhere and I didn't know where the
shipping box was.

Eventually I read one passing comment on a webpage and fixed it just by
pressing one of the high F keys when starting the computer. It
uninstalled a bad file which had just been installed. I thought it had
been a bad installed file, because I just installed something a little
out of the ordinary, but later I became sure it was a bad file from MS.
By now 2 or 3 months had gone by and I installed it again without a
problem. I guess they had fixed it.

The refurbisher would have no special way to know what the problem or
solution was. so nothing lost that I could not reach him.

After all this, I noticed the sticker on the side of the machine, with
the refurbisher's name, email, and phone number. Now a 2 years later,
half of the sticker has curled up. FWIW
RefurbishedPC.com support@refurbishedpc.com

> Paul
>

On 9/28/2023 4:17 PM, micky wrote:
> In alt.comp.os.windows-10, on Thu, 28 Sep 2023 12:08:03 +0100, Philip
> Herlihy <PhillipHerlihy@SlashDevNull.invalid> wrote:
>
>> In article <uf2oov$3ghbd$1@dont-email.me>, GlowingBlueMist wrote...
>>>
>>> On 9/27/2023 3:34 PM, micky wrote:
>>>> In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:16:41 +0100, Ed Cryer
>>>> <ed@somewhere.in.the.uk> wrote:
>>>>
>>>>> micky wrote:
>>>>>> On my desktop which has win10 Pro, for the last week I've tried over 10
>>>>>> times to install a feature update and it won't finish. Does that really
>>>>>> matter? I have a lot of features already. :-)
>>>>>>
>> ...
>>
>>> A few times with problem updates doing a sfc /scannow fixed things.
>>>
>>
>> If SFC fails, try using DISM first.
>>
>> https://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/
>
> Thanks. It also suggests restarting your PC in Safe Mode and running sfc
> again. I always forget safe mode.
>
> And it summarizes things at the start:
>
> Key Takeaways
> Open Command Prompt or PowerShell as administrator, then run "sfc
> /scannow" to fix corrupted Windows System Files. If SFC fails to run
> properly or cannot repair the files, run "DISM /Online /Cleanup-Image
> /RestoreHealth" to fix any remaining issues.
>
> Well, for now, I skipped running sfc in safe mode and went straight to
> DISM/ I restarted the computer and ran it, and I got:
>
> Deployment Image Servicing and Management tool
> Version: 10.0.19041.844
>
> Image Version: 10.0.19042.844
>
> ==== It got to 55.4%.
>
> Error: 4448
>
> The WOF driver encountered a corruption in the compressed file's
> Resource Table.
>
> The DISM log file can be found at C:\windows\Logs\DISM\dism.log
>
> So this is the middle of that file, and I think the error is noted in
> the middle of this excerpt, especially in those lines that you can find
> by Finding the word error . There are 7 such lines, but I don't
> think they show exactly where the error is or what do next. The error
> message above mentions the compressed file's Resource Table. But it
> doesn't say which compressed file. ???
>
> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
> to add the commands from provider: OfflineSetupManager
> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
> registered commands for the provider: OfflineSetupManager.
> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
> to add the commands from provider: SysprepManager
> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
> registered commands for the provider: SysprepManager.
> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
> to add the commands from provider: Edition Manager
> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
> registered commands for the provider: Edition Manager.
> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
> to add the commands from provider: SetupPlatformManager
> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
> registered commands for the provider: SetupPlatformManager.
> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
> PID=4624 TID=12652 Processing the top level command
> token(cleanup-image). -
> CPackageManagerCLIHandler::Private_ValidateCmdLine
> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
> PID=4624 TID=12652 Attempting to route to appropriate command handler. -
> CPackageManagerCLIHandler::ExecuteCmdLine
> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
> PID=4624 TID=12652 Routing the command... -
> CPackageManagerCLIHandler::ExecuteCmdLine
> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
> PID=4624 TID=12652 CBS session options=0x40100! -
> CDISMPackageManager::Internal_Finalize
> 2023-09-28 15:55:15, Info DISM DISM Package Manager:
> PID=4624 TID=12636 Error in operation: (null) (CBS HRESULT=0x80071160)
> - CCbsConUIHandler::Error
> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
> PID=4624 TID=12652 Failed finalizing changes. -
> CDISMPackageManager::Internal_Finalize(hr:0x80071160)
> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
> PID=4624 TID=12652 Failed processing package changes with session option
> CbsSessionOptionRepairStoreCorruption -
> CDISMPackageManager::RestoreHealth(hr:0x80071160)
> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
> PID=4624 TID=12652 Failed to restore the image health. -
> CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80071160)
> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
> PID=4624 TID=12652 Failed while processing command cleanup-image. -
> CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80071160)
> 2023-09-28 15:55:15, Info DISM DISM Package Manager:
> PID=4624 TID=12652 Further logs for online package and feature related
> operations can be found at %WINDIR%\logs\CBS\cbs.log -
> CPackageManagerCLIHandler::ExecuteCmdLine
> 2023-09-28 15:55:15, Error DISM DISM.EXE: DISM Package
> Manager processed the command line but failed. HRESULT=80071160
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Found the OSServices. Waiting to finalize it until
> all other providers are unloaded. -
> CDISMProviderStore::Final_OnDisconnect
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Found the OSServices. Waiting to finalize it until
> all other providers are unloaded. -
> CDISMProviderStore::Final_OnDisconnect
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Found the PE Provider. Waiting to finalize it until
> all other providers are unloaded. -
> CDISMProviderStore::Final_OnDisconnect
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Finalizing the servicing provider(DISM Package
> Manager) - CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Package Manager:
> PID=4624 TID=12652 Finalizing CBS core. - CDISMPackageManager::Finalize
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Disconnecting Provider: DISM Package Manager -
> CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Finalizing the servicing provider(MsiManager) -
> CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Disconnecting Provider: MsiManager -
> CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Finalizing the servicing provider(IntlManager) -
> CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Disconnecting Provider: IntlManager -
> CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Finalizing the servicing provider(IBSManager) -
> CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Disconnecting Provider: IBSManager -
> CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Finalizing the servicing provider(DriverManager) -
> CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Disconnecting Provider: DriverManager -
> CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Finalizing the servicing provider(DISM Unattend
> Manager) - CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Disconnecting Provider: DISM Unattend Manager -
> CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Finalizing the servicing provider(SmiManager) -
> CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Disconnecting Provider: SmiManager -
> CDISMProviderStore::Internal_DisconnectProvider
> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
> PID=4624 TID=12652 Finalizing the servicing provider(AppxManager) -
> CDISMProviderStore::Internal_DisconnectProvider

On 9/28/2023 4:33 PM, micky wrote:
> In alt.comp.os.windows-10, on Thu, 28 Sep 2023 19:11:13 +0100, Ed Cryer
> <ed@somewhere.in.the.uk> wrote:
>
>> micky wrote:
>>> On my desktop which has win10 Pro, for the last week I've tried over 10
>>> times to install a feature update and it won't finish. Does that really
>>> matter? I have a lot of features already. :-)
>>>
>>> I've tried doing the update as soon as windows is started, before
>>> running other programs.
>>>
>>> Specifically it say Feature update to windows 10, version 22H2, Pending
>>> download.
>>>
>>> And after I click on Go, or whatever, it downloads nicely but Install
>>> stops at 20%. Googling found that as a complaint years ago, but the
>>> suggestions didn't work for me.
>>
>> There's a Windows Update Troubleshooter that's rather buried out of
>> sight. It worked for me once, after I'd found it.
>> Settings/ Update & Security/ Troubleshoot/ Additional Troubleshooters/
>> Windows Update.
>>
>> Give it a try.
>
> Roger, willco.
>
> "Troubleshooting couldn't identify the problem."
>
> plus a list of 4 potentional issues that were checked.
> and a list of 4 other potential issues that were checked.
> All were followed by "Issue not present".
>
> Detection details.
> IsPostback_RC_PendingUpdates IsPostback: False
>
> Service Status
> Problem with BITS service : The requested service has already been
> started. System.Management.Automation.RemoteException More help is
> available by typing NET HELPMSG 2182.
> System.Management.Automation.RemoteException
>
> And when in the CMD window I type NET HELPMSG 2182, I get
> The requested service has already been started.

BITS and DoSVC are downloaders that support system functions.

BITS was the original, DoSVC came later. BITS seems to be
used for fallback purposes. If normal package-level (tiny files)
is not working with DoSVC, BITS is capable of downloading a 2.5GB
file instead.

They might still be turning it OFF and ON, even though it's not
a primary service provider.

I experimented with this. I used a GPEDIT policy,
to "starve" DoSVC and reduce its bandwidth setting. And the
thing I was doing, switched to using BITS. This would amount
to a "Plan B".

And you know how much those troubleshooters are worth. I have
some swamp land... it's the same with "SetupDiag", which is supposed
to diagnose Windows installation failures. I have YET to get any
response from it. I can write a Hello World program in C, that
produces two words more output than these Microsoft programs :-/

Imagine if ChatGPT could diagnose a computer. But you'll notice
they are not doing that. It would be too useful. We
can't have that. Instead, we get Clippy.

Paul

In alt.comp.os.windows-10, on Thu, 28 Sep 2023 17:15:51 -0400, Paul
<nospam@needed.invalid> wrote:

>On 9/28/2023 4:17 PM, micky wrote:
>> In alt.comp.os.windows-10, on Thu, 28 Sep 2023 12:08:03 +0100, Philip
>> Herlihy <PhillipHerlihy@SlashDevNull.invalid> wrote:
>>
>>> In article <uf2oov$3ghbd$1@dont-email.me>, GlowingBlueMist wrote...
>>>>
>>>> On 9/27/2023 3:34 PM, micky wrote:
>>>>> In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:16:41 +0100, Ed Cryer
>>>>> <ed@somewhere.in.the.uk> wrote:
>>>>>
>>>>>> micky wrote:
>>>>>>> On my desktop which has win10 Pro, for the last week I've tried over 10
>>>>>>> times to install a feature update and it won't finish. Does that really
>>>>>>> matter? I have a lot of features already. :-)
>>>>>>>
>>> ...
>>>
>>>> A few times with problem updates doing a sfc /scannow fixed things.
>>>>
>>>
>>> If SFC fails, try using DISM first.
>>>
>>> https://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/
>>
>> Thanks. It also suggests restarting your PC in Safe Mode and running sfc
>> again. I always forget safe mode.
>>
>> And it summarizes things at the start:
>>
>> Key Takeaways
>> Open Command Prompt or PowerShell as administrator, then run "sfc
>> /scannow" to fix corrupted Windows System Files. If SFC fails to run
>> properly or cannot repair the files, run "DISM /Online /Cleanup-Image
>> /RestoreHealth" to fix any remaining issues.
>>
>> Well, for now, I skipped running sfc in safe mode and went straight to
>> DISM/ I restarted the computer and ran it, and I got:
>>
>> Deployment Image Servicing and Management tool
>> Version: 10.0.19041.844
>>
>> Image Version: 10.0.19042.844
>>
>> ==== It got to 55.4%.
>>
>> Error: 4448
>>
>> The WOF driver encountered a corruption in the compressed file's
>> Resource Table.
>>
>> The DISM log file can be found at C:\windows\Logs\DISM\dism.log
>>
>> So this is the middle of that file, and I think the error is noted in
>> the middle of this excerpt, especially in those lines that you can find
>> by Finding the word error . There are 7 such lines, but I don't
>> think they show exactly where the error is or what do next. The error
>> message above mentions the compressed file's Resource Table. But it
>> doesn't say which compressed file. ???
>>
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>> to add the commands from provider: OfflineSetupManager
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
>> registered commands for the provider: OfflineSetupManager.
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>> to add the commands from provider: SysprepManager
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
>> registered commands for the provider: SysprepManager.
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>> to add the commands from provider: Edition Manager
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
>> registered commands for the provider: Edition Manager.
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>> to add the commands from provider: SetupPlatformManager
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
>> registered commands for the provider: SetupPlatformManager.
>> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
>> PID=4624 TID=12652 Processing the top level command
>> token(cleanup-image). -
>> CPackageManagerCLIHandler::Private_ValidateCmdLine
>> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
>> PID=4624 TID=12652 Attempting to route to appropriate command handler. -
>> CPackageManagerCLIHandler::ExecuteCmdLine
>> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
>> PID=4624 TID=12652 Routing the command... -
>> CPackageManagerCLIHandler::ExecuteCmdLine
>> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
>> PID=4624 TID=12652 CBS session options=0x40100! -
>> CDISMPackageManager::Internal_Finalize
>> 2023-09-28 15:55:15, Info DISM DISM Package Manager:
>> PID=4624 TID=12636 Error in operation: (null) (CBS HRESULT=0x80071160)
>> - CCbsConUIHandler::Error
>> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
>> PID=4624 TID=12652 Failed finalizing changes. -
>> CDISMPackageManager::Internal_Finalize(hr:0x80071160)
>> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
>> PID=4624 TID=12652 Failed processing package changes with session option
>> CbsSessionOptionRepairStoreCorruption -
>> CDISMPackageManager::RestoreHealth(hr:0x80071160)
>> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
>> PID=4624 TID=12652 Failed to restore the image health. -
>> CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80071160)
>> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
>> PID=4624 TID=12652 Failed while processing command cleanup-image. -
>> CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80071160)
>> 2023-09-28 15:55:15, Info DISM DISM Package Manager:
>> PID=4624 TID=12652 Further logs for online package and feature related
>> operations can be found at %WINDIR%\logs\CBS\cbs.log -
>> CPackageManagerCLIHandler::ExecuteCmdLine
//..... truncated

I should have read farther and noticed this. Mild shame on me.

Here is cbs.log

Before I noticed that the date was yesterday, I copied these two
sections because they used the word error. They're not long so I'm
leaving them here:

2023-09-27 17:34:22, Info CBS Appl: DetectUpdate,
Package:
Microsoft-Windows-IIS-WebServer-Package~31bf3856ad364e35~amd64~~10.0.19041.844,
Local Parent: IIS-WebServerManagementTools, Intended State: Staged
2023-09-27 17:34:22, Info CBS Appl: Package:
Microsoft-Windows-IIS-WebServer-Package~31bf3856ad364e35~amd64~~10.0.19041.844,
Update: IIS-IIS6ManagementCompatibility, Applicable: NeedsParent,
Disposition: Staged
2023-09-27 17:34:22, Info CBS Store corruption,
manifest missing for package:
Microsoft-Windows-MSMQ-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.746
2023-09-27 17:34:22, Info CBS Mark store corruption
flag because of package:
Microsoft-Windows-MSMQ-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.746.
[HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2023-09-27 17:34:22, Info CBS Appl: DetectUpdate,
Package:
Microsoft-Windows-NetFx4-WCF-US-OC-Package~31bf3856ad364e35~amd64~~10.0.19041.1,
Remote Parent: NetFx4-AdvSrvs, Intended State: Installed
2023-09-27 17:34:22, Info CBS Appl: Package:
Microsoft-Windows-NetFx4-WCF-US-OC-Package~31bf3856ad364e35~amd64~~10.0.19041.1,
Update: WCF-Services45, Applicable: Applicable, Disposition: Installed

And one second later:
2023-09-27 17:34:23, Info CBS Appl: DetectUpdate,
Package:
Microsoft-Windows-IIS-WebServer-Package~31bf3856ad364e35~amd64~~10.0.19041.844,
Local Parent: IIS-WebServerManagementTools, Intended State: Staged
2023-09-27 17:34:23, Info CBS Appl: Package:
Microsoft-Windows-IIS-WebServer-Package~31bf3856ad364e35~amd64~~10.0.19041.844,
Update: IIS-IIS6ManagementCompatibility, Applicable: NeedsParent,
Disposition: Staged
2023-09-27 17:34:23, Info CBS Store corruption,
manifest missing for package:
Microsoft-Windows-MSMQ-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.746
2023-09-27 17:34:23, Info CBS Mark store corruption
flag because of package:
Microsoft-Windows-MSMQ-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.746.
[HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2023-09-27 17:34:23, Info CBS Appl: DetectUpdate,
Package:
Microsoft-Windows-NetFx4-WCF-US-OC-Package~31bf3856ad364e35~amd64~~10.0.19041.1,
Remote Parent: NetFx4-AdvSrvs, Intended State: Installed
2023-09-27 17:34:23, Info CBS Appl: Package:
Microsoft-Windows-NetFx4-WCF-US-OC-Package~31bf3856ad364e35~amd64~~10.0.19041.1,
Update: WCF-Services45, Applicable: Applicable, Disposition: Installed
2023-09-27 17:34:23, Info CBS Appl: DetectUpdate,
Package:
Microsoft-Windows-IIS-WebServer-AddOn-Package~31bf3856ad364e35~amd64~~10.0.19041.844,
Remote Parent: IIS-WebServerRole, Intended State: Staged

On Thu, 28 Sep 2023 18:43:45 -0400, micky <NONONOmisc07@fmguy.com>
wrote:

>In alt.comp.os.windows-10, on Thu, 28 Sep 2023 17:15:51 -0400, Paul
><nospam@needed.invalid> wrote:
>
>>On 9/28/2023 4:17 PM, micky wrote:
>>> In alt.comp.os.windows-10, on Thu, 28 Sep 2023 12:08:03 +0100, Philip
>>> Herlihy <PhillipHerlihy@SlashDevNull.invalid> wrote:
>>>
>>>> In article <uf2oov$3ghbd$1@dont-email.me>, GlowingBlueMist wrote...
>>>>>
>>>>> On 9/27/2023 3:34 PM, micky wrote:
>>>>>> In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:16:41 +0100, Ed Cryer
>>>>>> <ed@somewhere.in.the.uk> wrote:
>>>>>>
>>>>>>> micky wrote:
>>>>>>>> On my desktop which has win10 Pro, for the last week I've tried over 10
>>>>>>>> times to install a feature update and it won't finish. Does that really
>>>>>>>> matter? I have a lot of features already. :-)
>>>>>>>>
>>>> ...
>>>>
>>>>> A few times with problem updates doing a sfc /scannow fixed things.
>>>>>
>>>>
>>>> If SFC fails, try using DISM first.
>>>>
>>>> https://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/
>>>
>>> Thanks. It also suggests restarting your PC in Safe Mode and running sfc
>>> again. I always forget safe mode.
>>>
>>> And it summarizes things at the start:
>>>
>>> Key Takeaways
>>> Open Command Prompt or PowerShell as administrator, then run "sfc
>>> /scannow" to fix corrupted Windows System Files. If SFC fails to run
>>> properly or cannot repair the files, run "DISM /Online /Cleanup-Image
>>> /RestoreHealth" to fix any remaining issues.
>>>
>>> Well, for now, I skipped running sfc in safe mode and went straight to
>>> DISM/ I restarted the computer and ran it, and I got:
>>>
>>> Deployment Image Servicing and Management tool
>>> Version: 10.0.19041.844
>>>
>>> Image Version: 10.0.19042.844
>>>
>>> ==== It got to 55.4%.
>>>
>>> Error: 4448
>>>
>>> The WOF driver encountered a corruption in the compressed file's
>>> Resource Table.
>>>
>>> The DISM log file can be found at C:\windows\Logs\DISM\dism.log
>>>
>>> So this is the middle of that file, and I think the error is noted in
>>> the middle of this excerpt, especially in those lines that you can find
>>> by Finding the word error . There are 7 such lines, but I don't
>>> think they show exactly where the error is or what do next. The error
>>> message above mentions the compressed file's Resource Table. But it
>>> doesn't say which compressed file. ???
>>>
>>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>>> to add the commands from provider: OfflineSetupManager
>>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
>>> registered commands for the provider: OfflineSetupManager.
>>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>>> to add the commands from provider: SysprepManager
>>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
>>> registered commands for the provider: SysprepManager.
>>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>>> to add the commands from provider: Edition Manager
>>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
>>> registered commands for the provider: Edition Manager.
>>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>>> to add the commands from provider: SetupPlatformManager
>>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
>>> registered commands for the provider: SetupPlatformManager.
>>> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
>>> PID=4624 TID=12652 Processing the top level command
>>> token(cleanup-image). -
>>> CPackageManagerCLIHandler::Private_ValidateCmdLine
>>> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
>>> PID=4624 TID=12652 Attempting to route to appropriate command handler. -
>>> CPackageManagerCLIHandler::ExecuteCmdLine
>>> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
>>> PID=4624 TID=12652 Routing the command... -
>>> CPackageManagerCLIHandler::ExecuteCmdLine
>>> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
>>> PID=4624 TID=12652 CBS session options=0x40100! -
>>> CDISMPackageManager::Internal_Finalize
>>> 2023-09-28 15:55:15, Info DISM DISM Package Manager:
>>> PID=4624 TID=12636 Error in operation: (null) (CBS HRESULT=0x80071160)
>>> - CCbsConUIHandler::Error
>>> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
>>> PID=4624 TID=12652 Failed finalizing changes. -
>>> CDISMPackageManager::Internal_Finalize(hr:0x80071160)
>>> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
>>> PID=4624 TID=12652 Failed processing package changes with session option
>>> CbsSessionOptionRepairStoreCorruption -
>>> CDISMPackageManager::RestoreHealth(hr:0x80071160)
>>> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
>>> PID=4624 TID=12652 Failed to restore the image health. -
>>> CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80071160)
>>> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
>>> PID=4624 TID=12652 Failed while processing command cleanup-image. -
>>> CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80071160)
>>> 2023-09-28 15:55:15, Info DISM DISM Package Manager:
>>> PID=4624 TID=12652 Further logs for online package and feature related
>>> operations can be found at %WINDIR%\logs\CBS\cbs.log -
>>> CPackageManagerCLIHandler::ExecuteCmdLine
> //..... truncated
>
>I should have read farther and noticed this. Mild shame on me.

Yikes! I don't often read <os.win.10> but does anythng ever work
routinely for you?

In alt.comp.os.windows-10, on Thu, 28 Sep 2023 17:50:03 -0700, Nobody
<jock@soccer.com> wrote:

>
>Yikes! I don't often read <os.win.10> but does anythng ever work
>routinely for you?

Do you want me to post whenever something works routinely?

On 9/28/2023 9:08 PM, micky wrote:
> In alt.comp.os.windows-10, on Thu, 28 Sep 2023 17:50:03 -0700, Nobody
> <jock@soccer.com> wrote:
>
>>
>> Yikes! I don't often read <os.win.10> but does anythng ever work
>> routinely for you?
>
> Do you want me to post whenever something works routinely?
>

I can relate a funny to you.

I fired up my Optiplex 780 Refurb, and as it turns out, it
was on 21H2. I was missing W10 22H2. (Its not W11 material, but
I think the stupid thing does have a TPM, just an old one.)

I tried installing 22H2, without using a Windows Update copy.
I used an ISO. I ran the Setup.exe once the ISO was mounted,
using the right-click "Mount" option on the 4.5GB ISO file.

Well, it got part way along, and I could tell from the chugging,
it was rolling back.

I don't think the logs indicated exactly what was wrong.
I tried the utility you can download ("SetupDiag.exe") from Microsoft,
that is supposed to analyze the logs from an Upgrade attempt, and it
delivered nothing.

On a hunch, I checked the hardware with CPUZ and it said
I had a GMA x4500 for graphics. Which is pretty crusty.

Somewhere along the way, I'd read that 22H2 could be gated by
using older (XDDM) graphics. So I got out my retired HD6450 AMD
video card (13 watts or so) which is WDDM 1.3 and put that in the machine.
And just like magic, the upgrade to 22H2 finished for me. WDDM is up
to around 3.0 on supported vid cards.

I would hardly say the experience left me with a positive impression.
I had to use a hunch, and some info I'd glanced at briefly in some
news article, to kinda guess at what was broken. It's not like
the machine told me "look, pal, this graphics is TOO OLD". If I'd
looked at logs, the logs would look like your logs, with recipes
for chicken soup and such.

I hope your hardware is a bit better than that. It's not a bad
machine, it has an E7500 dual core and it has lots of RAM.

I would say my Component Store was in fine shape, as the rollback
was not related to anything like that. Storage in that case, is
a brand new WD Black 1TB 7200RPM desktop hard drive. As the
WD Blue the refurb came with, had some "issues" so I replaced it.
The reason I seem to have a lot of those, is that is one of the
few drives my "computer store" stocks. If you wanted a random
8TB drive, they don't have anything like that. My only option now
for big drives, is to order them online, and I HATE the packaging
they use for drives. You never know what is going to happen with
a slap-happy mailer box and an expensive drive.

*******

I could find accounts of some store corruption causes by
Windows Defender compressed files. But I don't think that's what is
going on in your case. You seem to have a lot of missing manifest files,
and it can't check the integrity of a package, without a manifest to
work with. I still can't tell from the log, exactly what kind of
flap the storage got into, that caused it to bail. Almost like
it had opened something, had done all the work preparing the
repairs, and then the repair couldn't be put back.

One of the purposes of examining logs, is to see if it is a hardware
issue. I don't see a strong hardware component there. You are closer
to the machine, if it was a HDD you might hear a "click" indicating
trouble (the "click" on a recent hard drive here, was actually
a power supply with only 11.6V on the 12V rail). Some aspects of
hardware, you gotta use your other senses to sense trouble.

What you do next, may depend on what media you have on hand,
whether you want to bother making fresh media with MediaCreationTool,
and give it a bash with that. I would do an Upgrade Install,
run the Setup.exe on the downloaded ISO, and do the job that way.

(Picture shows how to mount an ISO9660 as a virtual DVD drive
so you can get at the Setup.exe on it)

https://www.bleepstatic.com/tutorials/windows-8/mount-an-iso/mount-right-click.jpg

If you could not manage to get Windows to mount it, you can use

Name: osfmount__osforensics_com_passmark_V3.1.1000.exe
Size: 12,319,160 bytes (11 MiB)
SHA256: 033C69C76B0234544DC883B0E8D00CE9BE175A54732419756A9D93E6709D963B

[Picture]

https://i.postimg.cc/zBNXwdtT/osfmount.gif

Check that there is sufficient space on C: for the Windows.old .
For some reason, the last W10 install I did here, it made a
"full sized hiberfil.sys" and that took 64GB of hard drive space
on the C: . I wasn't expecting it to make one quite that big
(50% of that file size is workable as a number).

Paul

In article <3albhidgv7smlr8468orq4o9kcapofsdol@4ax.com>, micky wrote...
>
> In alt.comp.os.windows-10, on Thu, 28 Sep 2023 12:08:03 +0100, Philip
> Herlihy <PhillipHerlihy@SlashDevNull.invalid> wrote:
>
> >In article <uf2oov$3ghbd$1@dont-email.me>, GlowingBlueMist wrote...
> >>
> >> On 9/27/2023 3:34 PM, micky wrote:
> >> > In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:16:41 +0100, Ed Cryer
> >> > <ed@somewhere.in.the.uk> wrote:
> >> >
> >> >> micky wrote:
> >> >>> On my desktop which has win10 Pro, for the last week I've tried over 10
> >> >>> times to install a feature update and it won't finish. Does that really
> >> >>> matter? I have a lot of features already. :-)
> >> >>>
> >...
> >
> >> A few times with problem updates doing a sfc /scannow fixed things.
> >>
> >
> >If SFC fails, try using DISM first.
> >
> >https://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/
>
> Thanks. It also suggests restarting your PC in Safe Mode and running sfc
> again. I always forget safe mode.
>
> And it summarizes things at the start:
>
> Key Takeaways
> Open Command Prompt or PowerShell as administrator, then run "sfc
> /scannow" to fix corrupted Windows System Files. If SFC fails to run
> properly or cannot repair the files, run "DISM /Online /Cleanup-Image
> /RestoreHealth" to fix any remaining issues.
>
> Well, for now, I skipped running sfc in safe mode and went straight to
> DISM/ I restarted the computer and ran it, and I got:
>
> Deployment Image Servicing and Management tool
> Version: 10.0.19041.844
>
> Image Version: 10.0.19042.844
>
> ==== It got to 55.4%.
>
> Error: 4448
>
> The WOF driver encountered a corruption in the compressed file's
> Resource Table.
>

....

DISM has a /Source option as well. I've never done it, but you can download a
new copy of Windows, and rebuild your "image" from that. These two articles
both explain how:

https://adamtheautomator.com/dism-cleanup-image/

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-
windows-10-image

I've only the foggiest understanding of what's going on with the DISM and SFC
commands (there just isn't time to understand everything...)

As I "understand" it, Windows maintains an image of some kind, and SFC will
scan the live system for corruption, making replacements from that image. You
can check, repair and (possibly?) replace the image using the DISM command. I
never once had SFC fix anything until I found out about DISM! I've never had
DISM need to rebuild using the /Source option, so I'll be interested to hear
your experience.

--

Phil, London

In alt.comp.os.windows-10, on Thu, 28 Sep 2023 17:15:51 -0400, Paul
<nospam@needed.invalid> wrote:

>On 9/28/2023 4:17 PM, micky wrote:
>> In alt.comp.os.windows-10, on Thu, 28 Sep 2023 12:08:03 +0100, Philip
>> Herlihy <PhillipHerlihy@SlashDevNull.invalid> wrote:
>>
>>> In article <uf2oov$3ghbd$1@dont-email.me>, GlowingBlueMist wrote...
>>>>
>>>> On 9/27/2023 3:34 PM, micky wrote:
>>>>> In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:16:41 +0100, Ed Cryer
>>>>> <ed@somewhere.in.the.uk> wrote:
>>>>>
>>>>>> micky wrote:
>>>>>>> On my desktop which has win10 Pro, for the last week I've tried over 10
>>>>>>> times to install a feature update and it won't finish. Does that really
>>>>>>> matter? I have a lot of features already. :-)
>>>>>>>
>>> ...
>>>
>>>> A few times with problem updates doing a sfc /scannow fixed things.
>>>>
>>>
>>> If SFC fails, try using DISM first.
>>>
>>> https://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/
>>
>> Thanks. It also suggests restarting your PC in Safe Mode and running sfc
>> again. I always forget safe mode.
>>
>> And it summarizes things at the start:
>>
>> Key Takeaways
>> Open Command Prompt or PowerShell as administrator, then run "sfc
>> /scannow" to fix corrupted Windows System Files. If SFC fails to run
>> properly or cannot repair the files, run "DISM /Online /Cleanup-Image
>> /RestoreHealth" to fix any remaining issues.
>>
>> Well, for now, I skipped running sfc in safe mode and went straight to
>> DISM/ I restarted the computer and ran it, and I got:
>>
>> Deployment Image Servicing and Management tool
>> Version: 10.0.19041.844
>>
>> Image Version: 10.0.19042.844
>>
>> ==== It got to 55.4%.
>>
>> Error: 4448
>>
>> The WOF driver encountered a corruption in the compressed file's
>> Resource Table.
>>
>> The DISM log file can be found at C:\windows\Logs\DISM\dism.log
>>
>> So this is the middle of that file, and I think the error is noted in
>> the middle of this excerpt, especially in those lines that you can find
>> by Finding the word error . There are 7 such lines, but I don't
>> think they show exactly where the error is or what do next. The error
>> message above mentions the compressed file's Resource Table. But it
>> doesn't say which compressed file. ???
>>
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>> to add the commands from provider: OfflineSetupManager
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
>> registered commands for the provider: OfflineSetupManager.
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>> to add the commands from provider: SysprepManager
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
>> registered commands for the provider: SysprepManager.
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>> to add the commands from provider: Edition Manager
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
>> registered commands for the provider: Edition Manager.
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>> to add the commands from provider: SetupPlatformManager
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Succesfully
>> registered commands for the provider: SetupPlatformManager.
>> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
>> PID=4624 TID=12652 Processing the top level command
>> token(cleanup-image). -
>> CPackageManagerCLIHandler::Private_ValidateCmdLine
>> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
>> PID=4624 TID=12652 Attempting to route to appropriate command handler. -
>> CPackageManagerCLIHandler::ExecuteCmdLine
>> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
>> PID=4624 TID=12652 Routing the command... -
>> CPackageManagerCLIHandler::ExecuteCmdLine
>> 2023-09-28 15:52:38, Info DISM DISM Package Manager:
>> PID=4624 TID=12652 CBS session options=0x40100! -
>> CDISMPackageManager::Internal_Finalize
>> 2023-09-28 15:55:15, Info DISM DISM Package Manager:
>> PID=4624 TID=12636 Error in operation: (null) (CBS HRESULT=0x80071160)
>> - CCbsConUIHandler::Error
>> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
>> PID=4624 TID=12652 Failed finalizing changes. -
>> CDISMPackageManager::Internal_Finalize(hr:0x80071160)
>> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
>> PID=4624 TID=12652 Failed processing package changes with session option
>> CbsSessionOptionRepairStoreCorruption -
>> CDISMPackageManager::RestoreHealth(hr:0x80071160)
>> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
>> PID=4624 TID=12652 Failed to restore the image health. -
>> CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80071160)
>> 2023-09-28 15:55:15, Error DISM DISM Package Manager:
>> PID=4624 TID=12652 Failed while processing command cleanup-image. -
>> CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80071160)
>> 2023-09-28 15:55:15, Info DISM DISM Package Manager:
>> PID=4624 TID=12652 Further logs for online package and feature related
>> operations can be found at %WINDIR%\logs\CBS\cbs.log -
>> CPackageManagerCLIHandler::ExecuteCmdLine
>> 2023-09-28 15:55:15, Error DISM DISM.EXE: DISM Package
>> Manager processed the command line but failed. HRESULT=80071160
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Found the OSServices. Waiting to finalize it until
>> all other providers are unloaded. -
>> CDISMProviderStore::Final_OnDisconnect
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Found the OSServices. Waiting to finalize it until
>> all other providers are unloaded. -
>> CDISMProviderStore::Final_OnDisconnect
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Found the PE Provider. Waiting to finalize it until
>> all other providers are unloaded. -
>> CDISMProviderStore::Final_OnDisconnect
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Finalizing the servicing provider(DISM Package
>> Manager) - CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Package Manager:
>> PID=4624 TID=12652 Finalizing CBS core. - CDISMPackageManager::Finalize
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Disconnecting Provider: DISM Package Manager -
>> CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Finalizing the servicing provider(MsiManager) -
>> CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Disconnecting Provider: MsiManager -
>> CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Finalizing the servicing provider(IntlManager) -
>> CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Disconnecting Provider: IntlManager -
>> CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Finalizing the servicing provider(IBSManager) -
>> CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Disconnecting Provider: IBSManager -
>> CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Finalizing the servicing provider(DriverManager) -
>> CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Disconnecting Provider: DriverManager -
>> CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Finalizing the servicing provider(DISM Unattend
>> Manager) - CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Disconnecting Provider: DISM Unattend Manager -
>> CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Finalizing the servicing provider(SmiManager) -
>> CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Disconnecting Provider: SmiManager -
>> CDISMProviderStore::Internal_DisconnectProvider
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Finalizing the servicing provider(AppxManager) -
>> CDISMProviderStore::Internal_DisconnectProvider
>
>So there's a reference to CBS.log in there.
>
> %WINDIR%\logs\CBS\cbs.log

In alt.comp.os.windows-10, on Thu, 28 Sep 2023 17:15:51 -0400, Paul
<nospam@needed.invalid> wrote:

>On 9/28/2023 4:17 PM, micky wrote:
>> In alt.comp.os.windows-10, on Thu, 28 Sep 2023 12:08:03 +0100, Philip
>> Herlihy <PhillipHerlihy@SlashDevNull.invalid> wrote:
>>
>>> In article <uf2oov$3ghbd$1@dont-email.me>, GlowingBlueMist wrote...
>>>>
>>>> On 9/27/2023 3:34 PM, micky wrote:
>>>>> In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:16:41 +0100, Ed Cryer
>>>>> <ed@somewhere.in.the.uk> wrote:
>>>>>
>>>>>> micky wrote:
>>>>>>> On my desktop which has win10 Pro, for the last week I've tried over 10
>>>>>>> times to install a feature update and it won't finish. Does that really
>>>>>>> matter? I have a lot of features already. :-)
>>>>>>>
>>> ...
>>>
>>>> A few times with problem updates doing a sfc /scannow fixed things.
>>>>
>>>
>>> If SFC fails, try using DISM first.
>>>
>>> https://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/
>>
>> Thanks. It also suggests restarting your PC in Safe Mode and running sfc
>> again. I always forget safe mode.
>>
>> And it summarizes things at the start:
>>
>> Key Takeaways
>> Open Command Prompt or PowerShell as administrator, then run "sfc
>> /scannow" to fix corrupted Windows System Files. If SFC fails to run
>> properly or cannot repair the files, run "DISM /Online /Cleanup-Image
>> /RestoreHealth" to fix any remaining issues.
>>
>> Well, for now, I skipped running sfc in safe mode and went straight to
>> DISM/ I restarted the computer and ran it, and I got:
>>
>> Deployment Image Servicing and Management tool
>> Version: 10.0.19041.844
>>
>> Image Version: 10.0.19042.844
>>
>> ==== It got to 55.4%.
>>
>> Error: 4448
>>
>> The WOF driver encountered a corruption in the compressed file's
>> Resource Table.
>>
>> The DISM log file can be found at C:\windows\Logs\DISM\dism.log
>>
>> So this is the middle of that file, and I think the error is noted in
>> the middle of this excerpt, especially in those lines that you can find
>> by Finding the word error . There are 7 such lines, but I don't
>> think they show exactly where the error is or what do next. The error
>> message above mentions the compressed file's Resource Table. But it
>> doesn't say which compressed file. ???
>>
>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>> to add the commands from provider: OfflineSetupManager
>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>> PID=4624 TID=12652 Finalizing the servicing provider(AppxManager) -
>> CDISMProviderStore::Internal_DisconnectProvider
>
>So there's a reference to CBS.log in there.
>
> %WINDIR%\logs\CBS\cbs.log
>
> Paul
>

I've posted two replies to this post already, one a couple hours ago,
and they don't show up. Maybe they will.

Anyhow, right now I'm trying to use step 5 of
https://answers.microsoft.com/en-us/windows/forum/all/i-keep-getting-error-0x8007025d-when-doing/97f5e767-dbdc-4031-b0f9-b6e20348151a
Download the update manually from the Microsoft Update Catalog website
and install it manually. Make sure you download the correct update for
your Windows 10 version and architecture.

I had the idea I should be up to 22H2, but winver says it's only 20H2,
build 19042, 844 and that it's copyright 2020!!! Have I not noticed
that for almost 2 years that it's not installing? ... possible.

So reading from bottom to top of the list, and discounting the ones for
ARM64 (since I googled and checked msinfo32 and I don't have that) there
is the
2021-10 Dynamic update for Windows 10 20H2 x64 --- Safe OS. from Oct
26, 2021, and the
2021-11 Dynamic update for Windows 10 20H2 x64 --- Safe OS. from Nov
22, 2021. KB numbers on request.

If I try the first one, and the first one has already been installed, no
harm done, right?

So I should try the first one and if it works, then try the automatic
update. And if auto still doesn't work, I shoudl run the 2nd one,
right?

There are also update packages for 21H2 and 22H2, but nothing for H1.
But I think after I do one or two by hand, the others will work
automatically.

In alt.comp.os.windows-10, on Mon, 02 Oct 2023 02:26:37 -0400, micky
<NONONOmisc07@fmguy.com> wrote:

>
>I've posted two replies to this post already, one a couple hours ago,
>and they don't show up. Maybe they will.

They were already there. I had a filter on for posts with bodies.

On 10/2/2023 2:26 AM, micky wrote:
> In alt.comp.os.windows-10, on Thu, 28 Sep 2023 17:15:51 -0400, Paul
> <nospam@needed.invalid> wrote:
>
>> On 9/28/2023 4:17 PM, micky wrote:
>>> In alt.comp.os.windows-10, on Thu, 28 Sep 2023 12:08:03 +0100, Philip
>>> Herlihy <PhillipHerlihy@SlashDevNull.invalid> wrote:
>>>
>>>> In article <uf2oov$3ghbd$1@dont-email.me>, GlowingBlueMist wrote...
>>>>>
>>>>> On 9/27/2023 3:34 PM, micky wrote:
>>>>>> In alt.comp.os.windows-10, on Wed, 27 Sep 2023 21:16:41 +0100, Ed Cryer
>>>>>> <ed@somewhere.in.the.uk> wrote:
>>>>>>
>>>>>>> micky wrote:
>>>>>>>> On my desktop which has win10 Pro, for the last week I've tried over 10
>>>>>>>> times to install a feature update and it won't finish. Does that really
>>>>>>>> matter? I have a lot of features already. :-)
>>>>>>>>
>>>> ...
>>>>
>>>>> A few times with problem updates doing a sfc /scannow fixed things.
>>>>>
>>>>
>>>> If SFC fails, try using DISM first.
>>>>
>>>> https://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/
>>>
>>> Thanks. It also suggests restarting your PC in Safe Mode and running sfc
>>> again. I always forget safe mode.
>>>
>>> And it summarizes things at the start:
>>>
>>> Key Takeaways
>>> Open Command Prompt or PowerShell as administrator, then run "sfc
>>> /scannow" to fix corrupted Windows System Files. If SFC fails to run
>>> properly or cannot repair the files, run "DISM /Online /Cleanup-Image
>>> /RestoreHealth" to fix any remaining issues.
>>>
>>> Well, for now, I skipped running sfc in safe mode and went straight to
>>> DISM/ I restarted the computer and ran it, and I got:
>>>
>>> Deployment Image Servicing and Management tool
>>> Version: 10.0.19041.844
>>>
>>> Image Version: 10.0.19042.844
>>>
>>> ==== It got to 55.4%.
>>>
>>> Error: 4448
>>>
>>> The WOF driver encountered a corruption in the compressed file's
>>> Resource Table.
>>>
>>> The DISM log file can be found at C:\windows\Logs\DISM\dism.log
>>>
>>> So this is the middle of that file, and I think the error is noted in
>>> the middle of this excerpt, especially in those lines that you can find
>>> by Finding the word error . There are 7 such lines, but I don't
>>> think they show exactly where the error is or what do next. The error
>>> message above mentions the compressed file's Resource Table. But it
>>> doesn't say which compressed file. ???
>>>
>>> 2023-09-28 15:52:38, Info DISM DISM.EXE: Attempting
>>> to add the commands from provider: OfflineSetupManager
>>> 2023-09-28 15:55:15, Info DISM DISM Provider Store:
>>> PID=4624 TID=12652 Finalizing the servicing provider(AppxManager) -
>>> CDISMProviderStore::Internal_DisconnectProvider
>>
>> So there's a reference to CBS.log in there.
>>
>> %WINDIR%\logs\CBS\cbs.log
>>
>> Paul
>>
>
> I've posted two replies to this post already, one a couple hours ago,
> and they don't show up. Maybe they will.
>
> Anyhow, right now I'm trying to use step 5 of
> https://answers.microsoft.com/en-us/windows/forum/all/i-keep-getting-error-0x8007025d-when-doing/97f5e767-dbdc-4031-b0f9-b6e20348151a
> Download the update manually from the Microsoft Update Catalog website
> and install it manually. Make sure you download the correct update for
> your Windows 10 version and architecture.
>
> I had the idea I should be up to 22H2, but winver says it's only 20H2,
> build 19042, 844 and that it's copyright 2020!!! Have I not noticed
> that for almost 2 years that it's not installing? ... possible.
>
> So reading from bottom to top of the list, and discounting the ones for
> ARM64 (since I googled and checked msinfo32 and I don't have that) there
> is the
> 2021-10 Dynamic update for Windows 10 20H2 x64 --- Safe OS. from Oct
> 26, 2021, and the
> 2021-11 Dynamic update for Windows 10 20H2 x64 --- Safe OS. from Nov
> 22, 2021. KB numbers on request.
>
> If I try the first one, and the first one has already been installed, no
> harm done, right?
>
> So I should try the first one and if it works, then try the automatic
> update. And if auto still doesn't work, I shoudl run the 2nd one,
> right?
>
> There are also update packages for 21H2 and 22H2, but nothing for H1.
> But I think after I do one or two by hand, the others will work
> automatically.
>

It's as I feared. Your Windows Update has been busted for several
years, and you've stopped getting Windows Updates.

Microsoft issues WU for a limited number of OS versions.
It's possible the Windows Defender updates last longer,
but I don't know that for sure.

Why not try an Upgrade install with W10 22H2 disc ?
That will bring the machine back into support.
You do the Upgrade Install, from the running OS.

Paul

In alt.comp.os.windows-10, on Mon, 2 Oct 2023 06:04:14 -0400, Paul
<nospam@needed.invalid> wrote:

>
>>
>> I've posted two replies to this post already, one a couple hours ago,
>> and they don't show up. Maybe they will.

Turns out 3 or all of the ngs I'm following had a With Bodies filter
turned on, even though I only did this for one ng. I've upgraded to
Version 4 and I don't know its idiosyncracies.
>
>> Anyhow, right now I'm trying to use step 5 of
>> https://answers.microsoft.com/en-us/windows/forum/all/i-keep-getting-error-0x8007025d-when-doing/97f5e767-dbdc-4031-b0f9-b6e20348151a
>> Download the update manually from the Microsoft Update Catalog website
>> and install it manually. Make sure you download the correct update for
>> your Windows 10 version and architecture.
>>
>> I had the idea I should be up to 22H2, but winver says it's only 20H2,
>> build 19042, 844 and that it's copyright 2020!!! Have I not noticed
>> that for almost 2 years that it's not installing? ... possible.
>>
>> So reading from bottom to top of the list, and discounting the ones for
>> ARM64 (since I googled and checked msinfo32 and I don't have that) there
>> is the
>> 2021-10 Dynamic update for Windows 10 20H2 x64 --- Safe OS. from Oct
>> 26, 2021, and the
>> 2021-11 Dynamic update for Windows 10 20H2 x64 --- Safe OS. from Nov
>> 22, 2021. KB numbers on request.
>>
>> If I try the first one, and the first one has already been installed, no
>> harm done, right?
>>
>> So I should try the first one and if it works, then try the automatic
>> update. And if auto still doesn't work, I shoudl run the 2nd one,
>> right?
>>
>> There are also update packages for 21H2 and 22H2, but nothing for H1.
>> But I think after I do one or two by hand, the others will work
>> automatically.
>>
>
>It's as I feared. Your Windows Update has been busted for several
>years, and you've stopped getting Windows Updates.

I was reading another post of mine here and it reminded me that two
years ago during automatic update, I'm 95% sure, I had received a bad
file from Microsoft. It took me almost 3 months to fix it. I know the
first update after that worked, but I stopped paying attention.

I'd turned my laptop into my primary computer, and it still has my email
and newsgroups and the desktop is just for extra webpages and watching
videos, so if the desktop wasn't have successful updates, I probably
didn't notice it. If I paid attention at all, I don't remember numbers,
and I can't remember if it's supposed to be 19, 20, or 22.
>
>Microsoft issues WU for a limited number of OS versions.
>It's possible the Windows Defender updates last longer,
>but I don't know that for sure.
>
>Why not try an Upgrade install with W10 22H2 disc ?

So I can skip the earlier ones, that would be great.

>That will bring the machine back into support.
>You do the Upgrade Install, from the running OS.

Okay, I ran it, from the Microsoft Update Catalog website

It says Version 10.0.19041.844 -- is this the version to be installed?
Image Version: 10.0.19042.844 -- or is this?

The second one, the image version, is the version I already have, and
the first one is 1 less than that, so it does't seem like it could be a
productive update.

It took only about 5 seconds and it says it completed successfully. How
could 5 seconds be enough?

It's kb5012419: Compatibility update for installing and recovering
Windows 10, version 20H2, 21H1, and 21H2: March 8, 2022
https://support.microsoft.com/en-au/topic/kb5012419-compatibility-update-for-installing-and-recovering-windows-10-version-20h2-21h1-and-21h2-march-8-2022-9d78ba78-80f4-4948-9bb5-3c3667f5b0c7
You don't have to restart your device after you apply this update.

This update makes improvements to the "safe operating system" (SafeOS)
that is used to update the Windows recovery environment (WinRE) for
Windows 10, version 20H2, 21H1, and 21H2.

-- Sounds like just what I needed.

But maybe I have to run win update or wait until it runs again, so I ran
it, and it checked just a minute earlier and the update was available.
And it downloaded verrrry quickly and then stalled at 20% like before
but for less time and now it says 100%. Exhilaration, but followed by
sadness, because it says "Error encountered. There were some problems
installing updates but we'll try again later. .. 0x8007025d

I think I have to go to step 6 of the instructions in the link at the
top:

If none of the above solutions work, you can try resetting your
Windows Update components. To do this, open an elevated command prompt
and run the following commands:

sqlCopy codenet stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc

Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Ren C:\Windows\System32\catroot2 Catroot2.old

net start bits
net start wuauserv
net start appidsvc
net start cryptsvc

This will stop the necessary services, rename the
SoftwareDistribution and Catroot2 folders, and restart the services.
This should reset the Windows Update components and allow you to install
the update.

He adds: I hope one of these solutions works for you!

Alternatively, what if I do nothing and just don't have updates. Havent'
they found all the security flaws in win10 by now?
Are they making improvements even after they've stopped support?
>
> Paul
>
>