Updates will not install

[plaguesville]

Hi,

I have an HP Pavilion laptop, spec at attachment CBSc.

Attachment CBS: when this was saved, it weighed in at 47MB. It looked as though it had accumulated several CbsPersist files and then amalgamated them into yet another file. I've weeded out all but the latest one.
I trust I have followed the instructions acceptably and that you can make sense of it.

I live in hope.
x
p

Edit:
Since making the posting, I've done a few circuits of chasing my tail, see attachments CBSd and CBSe. Attempts at installation produce the same (non)result.
x
e

 

[rvcjew]

This is not my expertise but from looking though some of it I would try this first most. https://support.microsoft.com/en-us/gp/windows-update-issues/en-us

 

[NoelDP]

Here's the error-list from CheckSUR...

Summary:
Seconds executed: 2441
 Found 9 errors
  CBS MUM Corrupt Total count: 5
  CBS Catalog Corrupt Total count: 4
Unavailable repair files:
 servicing\packages\Package_32_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_33_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_33_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_56_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_56_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_57_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_57_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_58_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_58_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_32_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_33_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_33_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_56_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_56_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_57_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_57_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_58_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_58_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat

I'll post a fix later.

 

[NoelDP]

I've uploaded a file - pgvaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\pgvaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\pgvaa
or
DIR E:\pgvaa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\pgvaa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[plaguesville]

rvcjew,

Thanks for response but I encountered that hurdle on one of my circuits.
Fortunately they were not ever decreasing circles or I would have disappeared days ago.
x
p

 

[plaguesville]

NoelDP,

Thanks for your thorough instructions. I've read them a couple of times. I have yet to learn and inwardly digest them before embarking on implementation.

Over the past few weeks I have read your similar postings, trying to figure out what is going on whilst obeying the caution NOT to try it on my machine. I was hoping that my request would come to your attention.

Such is my respect for, or fear of, the technology, it might take me a couple of days to study some more and work up the nerve to give it a go. I shall report at the earliest possible.
x
p

 

[NoelDP]

That's OK - no hurry

 

[plaguesville]

Hi, Noel,

I'm reliving a nightmare.

I've been transported back some 25 years to when I was middle aged but the least unsuccessful person struggling with (I think) Windows 3.0: "dir", "mcopy", "xcopy" and the rest; most of which I have managed to forget.

I read your directions closely and printed them but, when attempting to implement them, I did not receive the predicted responses for "extract ..."
I rummaged about and finally blundered into getting \pgvaa into C:\ but it was "not found" in the command prompt, see attachment.

Sorry for being so dim. Can you deduce where I have failed to follow the plot?
x
p

 

[NoelDP]

Did you try the other drive letters with the DIR C:\pgvaa command? from the looks of it, your could need to use D: E: or F: to find the right one.

 

[plaguesville]

Oh, that was quick. Ta.

Thinking about it, the file downloaded twice. Perhaps I got it all confused. I persuaded the file into C drive and thought I'd called it up from there.

I'll clear the decks and start again from scratch, when I get back later.
x
e