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
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.
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 CryerA few times with problem updates doing a sfc /scannow fixed things.
<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.
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:16:41 +0100, Ed Cryer <ed@somewhere.in.the.uk> wrote:A few times with problem updates doing a sfc /scannow fixed things.
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 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.
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)
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.
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.
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 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/
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
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.
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:17 PM, micky wrote://..... truncated
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
So there's a reference to CBS.log in there.
%WINDIR%\logs\CBS\cbs.log
Paul
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:15:51 -0400, Paul ><nospam@needed.invalid> wrote:
On 9/28/2023 4:17 PM, micky wrote://..... truncated
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
I should have read farther and noticed this. Mild shame on me.
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?
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.
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
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: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.
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.
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
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
In alt.comp.os.windows-10, on Mon, 02 Oct 2023 14:56:35 -0400, micky <NONONOmisc07@fmguy.com> wrote:
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
This step didn't work because I didn't have sqlcopy. I googled,
downloaded, unzipped, and moved sqlcopy.exe and nothing else to the
Path. Ran it,
in a box with administrative powers,
and got:
*** NOTE: this is an unreleased direct table copy application, please
verify the copy results (i.e. with Database Compare) ***
Unhandled Exception: System.NullReferenceException: Object reference not
set to an instance of an object.
at SQLCopy.Config.Init()
at SQLCopy.Program.Main(String[] args)
net stop wuauserv
The Windows Update service is not started. --- no problem
More help is available by typing NET HELPMSG 3521
net stop appidsvc
The Application Identity service is not started. --- no problem
More help is available by typing NET HELPMSG 3521.
C:\Users\admin>NET HELPMSG 3521
The *** service is not started. --- Tricked me.
net stop cryptsvc
The following services are dependent on the Cryptographic Services
service.
Stopping the Cryptographic Services service will also stop these
services.
AVG Tools
AVG Antivirus
Do you want to continue this operation? (Y/N) [N]: y
The requested pause, continue, or stop, is not valid for this service.
--- Huh? Answers.microsoft said to do this.
Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Good!
Ren C:\Windows\System32\catroot2 Catroot2.old
Access is denied. --- If I can't rename this, that might sabotage the
whole thing.
net start bits
The BITS service was started successfully.
net start wuauserv
... was started successfully.
net start appidsvc
... was started successfully.
net start cryptsvc
... has already been started. --- Is this why catroots couldn't be
renamed.
Tried to update, after 5 minutes at 20%, went to 100%; after 3 minutes
there, Error encountered. same as before.
On 10/2/2023 5:42 PM, micky wrote:
In alt.comp.os.windows-10, on Mon, 02 Oct 2023 14:56:35 -0400, micky
<NONONOmisc07@fmguy.com> wrote:
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
This step didn't work because I didn't have sqlcopy. I googled,
downloaded, unzipped, and moved sqlcopy.exe and nothing else to the
Path. Ran it,
in a box with administrative powers,
and got:
*** NOTE: this is an unreleased direct table copy application, please
verify the copy results (i.e. with Database Compare) ***
Unhandled Exception: System.NullReferenceException: Object reference not
set to an instance of an object.
at SQLCopy.Config.Init()
at SQLCopy.Program.Main(String[] args)
net stop wuauserv
The Windows Update service is not started. --- no problem
More help is available by typing NET HELPMSG 3521
net stop appidsvc
The Application Identity service is not started. --- no problem
More help is available by typing NET HELPMSG 3521.
C:\Users\admin>NET HELPMSG 3521
The *** service is not started. --- Tricked me.
net stop cryptsvc
The following services are dependent on the Cryptographic Services
service.
Stopping the Cryptographic Services service will also stop these
services.
AVG Tools
AVG Antivirus
Do you want to continue this operation? (Y/N) [N]: y
The requested pause, continue, or stop, is not valid for this service.
--- Huh? Answers.microsoft said to do this.
Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Good!
Ren C:\Windows\System32\catroot2 Catroot2.old
Access is denied. --- If I can't rename this, that might sabotage the
whole thing.
net start bits
The BITS service was started successfully.
net start wuauserv
... was started successfully.
net start appidsvc
... was started successfully.
net start cryptsvc
... has already been started. --- Is this why catroots couldn't be
renamed.
Tried to update, after 5 minutes at 20%, went to 100%; after 3 minutes
there, Error encountered. same as before.
sqlCopy code <=== Is this actually part of the script ????? No.
net stop bits <=== these three words together, make sense
This is the first line of the script (as originally posted)
You don't have to putz with that code, because that script is
in a Troubleshooter. Can you guess which troubleshooter that is ?
Troubleshooters are in Control Panels. Control Panels can be accessed
via Start : Run : control.exe .
[Picture]
https://i.postimg.cc/xdJvf6fB/control-exe-control-panels-troubleshooting-windows-update-W10.gif
It's unclear who invented the script. The script first appeared on a
web page or posted to USENET, and was making the rounds. Later, it
was discovered inside a Troubleshooter, the same code.
This version is augmented, with return code analysis. If you used
archive.org and walked this page backwards, you might find the original >version (looks like yours).
https://www.tenforums.com/tutorials/24742-reset-windows-update-windows-10-a.html
The procedure is marginally easier to do from Linux, as there are no permissions
involved, and no third-party antivirus running to foul the results. I'm not proposing
you do that, as I have no idea of your Linux skillz. The only thing that fouls
up an attack from Linux, is NTFS files with New Style Compression, they can't be
accessed. The files you need to work on, I do not think they are protected that way.
I probably have a copy of the original version on the other machine,
but it is basically the same lines as the one you show.
Some troubleshooters on Windows, have been reduced to an onboard EXE file. >Something like "wsreset.exe" for Windows Store Reset. But the Troubleshooters >in Control Panel, could be hiding in a package of their own. It's even possible,
if you have Indexing enabled and are fully indexing the contents of C: , using
lines from the script, in a search, would find the .ps1 module doing it.
In any case, you can do it from a GUI.
However, since your AV is going to interfere, maybe there really is a reason to
hand-edit a .ps1 file in Notepad, to achieve your objective.
With Microsofts sloppy maintenance skill, it's unlikely a lot of stuff
still works properly. The "SetupDiag.exe" utility, for analyzing why
an Upgrade did not work, it does fuck all. This means, the logic no longer >matches the log file structure or something. Yet, they have not corrected their
error. There was also a script that converted an ETW log into a text log >humans could read -- and that was broken for years, without getting fixed. >This is why I cannot express a lot of optimism about the tools you're
using right now. Nobody seems to "own anything" at Microsoft. Nobody
fusses over stuff to make sure it works.
Paul
I think I had run the troubleshooter already, because it's step 3 in
that same answer. But to be sure I ran it after I read your post. it
found a problem in the first section of potential issues, implied that
it fixed it, but then the Update didn't run any better. Stopped at 20%, eventually went straight to 100%, but gave the same error message and
had not updated winver's version.
And I just ran it again and this time it finished very quiekcly saying Troubleshooter couldn't identify the problem. but in the details it says "Probem with BITS service: The requested service has already been
started. System.Management.automation.remoteException More help is avaialble by typing NET HELPMSG 2182.
But when I type that, all it says is The requested service has alrady
been started.
*******
I was ready to just skip updates. After all, are they really improving
win10 these days? But then:
I went to https://www.medstarhealth.org/request-an-appointment
and the page was imcomplete.
I tried the same page in my laptop and it made sense, looked complete.
NEVER MIND, NEVER MIND, Never mind. I tried to load it 3 times an hour
ago and even though other pages were working fine, only half this page loaded. Just now, it all loaded.
So now I'm back to thinking about just skipping updates.
I never consciously turned on Indexing. Does that mean I don't have
it?
Or could I turn off the AV? That's what I did one of the times I
tried to run Update, because the url answer at the top of this post said
to do that.
I ran it after turning off my AVs, and it didn't work.
It asks if I want to stop Cryptographic services even though that will
stop AVG tools and antivirus, and I said Y, and then it said
The requested pause,continue, or stop is not valid for this service. How
can that be? Did they write the script wrong? i don't think so.
Then it asks the same question again -- up to now it's looked a lot like
I did manually -- and this time it says Cannot reset WU since criptsvc
failed to stop
Restart the computer and try again.
And even though I had several things to do it restarted automatyically.
After it instructed me to do it, IT did it. Very bad. If I'd seen
that coming I would have ended the script in the middle. I will take
this part out.
I don't know what you have against a Repair Install (same version)
or Upgrade Install (use media for 22H2), as that's one way to fix up
a WinSxS. It should not have a heavy reliance on Windows Update, except
it does insist for some reason on "updating stuff" before it begins.
One thing they like to pull in, is the latest graphics driver, but then typically, they don't seem to use it, then they download the damn driver again later.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 00:41:09 |
| Calls: | 6,666 |
| Calls today: | 4 |
| Files: | 12,212 |
| Messages: | 5,335,396 |
