Can't install KB4474419 -it fails and reverts

It is about Windows7-sp1-64bit.
Microsoft information says it is for SHA-2, important for subsequent updates.
Also information said I will not need a restart after installing this KB4474419 update. It did need a restart.
Update window screen said it was doing system restore and it was a successful installation.
But after restart it failed configuring and they were reverting changes.
I tried installing this update about a month ago. It failed then. It failed today.

Questions:
1. why is it failing?
2. do I really need this update?
3. if yes, how to make it work?

Edited by tos226, 27 April 2019 - 09:59 PM.

Try to download it from here and install it manually: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4474419

When you check the Windows Update history and right click the afflicted update, View details is there no error code associated with the failure:

[attachment=212857:Untitled.jpg]

Describe your antivirus/antimalware environment.

A third suggestiion:

Open an administrator Command prompt. At the prompt type the following and press Enter:

SFC /Scannow

Once done, attempt Windows Updates. If the updates fail, Zip and upload the C:\Windows\Logs\CBS folder to any of the following services.

Microsoft OneDrive
Google Drive
Dropbox
DataFileHost
ExpireBox
SendSpace
WeTransfer

Post the link to the zipped folder.

Try to download it from here and install it manually: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4474419

Will do - but the date in the catalog is the same so I suspect it won't help. Should I do it before of after sfc scan suggested below?

When you check the Windows Update history and right click the afflicted update, View details is there no error code associated with the failure:

 

Untitled.jpg

 

Describe your antivirus/antimalware environment.

Error is 80004005. I spent much of the day browsing about it and unfortunately there are as many suggestions as posters.

AV is MSE declares me clean. EEK on demand also clean. Firewall is Outpost without AV but with HIPS. AntiExploit is Malwarebytes Antiexploit.

A third suggestiion:

 

Open an administrator Command prompt. At the prompt type the following and press Enter:

 

SFC /Scannow

 

Once done, attempt Windows Updates. If the updates fail, Zip and upload the C:\Windows\Logs\CBS folder to any of the following services.

 

Microsoft OneDrive
Google Drive
Dropbox
DataFileHost
ExpireBox
SendSpace
WeTransfer

Post the link to the zipped folder.

That's one of the suggestions I've seen on the web. I have to do an image before I let Windows mess me up. I'm scared of running such things. Will image tomorrow.

Thank you all for your suggestions.

BTW I tripple boot (windows 7, 10, and Linux Mint, all in partitions on one disk) and I hope that sfc won't mess with the grub2 loader.

Also I managed to read setupapi.dev and setupapi.app logs - they mumble something about cpu.inf higher version reflected. No idea what that means.

Edited by tos226, 28 April 2019 - 10:13 PM.

Errors that end with 005 are rights/permissions/access denied kinds of things and with Windows Update the issue is often a third party AV that is "protecting" your system from changes the update wants to apply.

This is why sometimes the updates seem to go okay until the system is restarted, then on restart the update can't be applied and the update is backed out/reverting.

Any kind of third party protection software that is running real time (except MSE) would be a suspect.

I can't think of a case where MSE has ever been a problem but it could be, don't know what EEK on demand is, I thought Outpost was EOL, and don't know much about MBAM Antiexploit.

You may be able to disable anything providing real time protections or uninstall them completely and install the update, then reinstall the AV.

Your CBS logs folder could have several huge useless files in it so I would whack the old ones and get one fresh log file but that's probably just me.

A Google search (you can change the search criteria) reveals some cases and you might want to look at and weed out the scores of suggestions that begin with the word "try" and suggestions that actually work.

[attachment=212896:Untitled.jpg]

Edited by joseibarra, 29 April 2019 - 12:29 AM.

@joseibarra,

Outpost is EOL, but it is packet filtering and the internet hasn't changed. I see no blocks to any system files by Outpost's HOSTS section.
AntiExploit injects into web-facing applications when they run (pdf readers, browsers ...), so no possible conflict here.
EEK is Emsisoft emergency kit - much recommended here.
I'm reading the sort of threads you suggested. One thing I don't want to mess with is grub - some have done it and it didn't help.
I deleted several CBS files, indeed they're huge when unzipped. And beyond my comprehension.
I'll be back after I decide on a path to take. Considering that I haven't seen such update failure in years, and that Win7 on my system is stable and not changing, it's rough to decide what to do, especially that the system is just fine. I suspect M$ might issue a patch to this update after they suck up more wermgr logs.
Thanks for your posts.

A third suggestiion:

 

Open an administrator Command prompt. At the prompt type the following and press Enter:

 

SFC /Scannow

 

Once done, attempt Windows Updates. If the updates fail, Zip and upload the C:\Windows\Logs\CBS folder to any of the following services.

 

Microsoft OneDrive
Google Drive
Dropbox
DataFileHost
ExpireBox
SendSpace
WeTransfer

Post the link to the zipped folder.

- I ran SFC but with /verifyonly switch and it saw no issues.
- From the MS catalog I downloaded into my own data directory
windows6.1-kb4474419-x64_6acf139f1eb84f60fcdeef3d4f81285e1edb45f9.msu
- I turned off Outpost from starting at boot time before running this KB.
- Clicked on .msu to run as admin, allowed in UAC.
It installed, failed, restarted, it reverted, just as before.
- \CBS.log file is enormous, means nothing to me. In case this will help you, the 4474419 installation started at 13:57.
Windows objected with Access denied to zipping \CBS folder, but I ran 7zip as admin and then it worked.
- Switched to Windows10 to be able to use Dropbox which I don't have on 7.
- CBS directory you requested is here:
https://www.dropbox.com/s/trkgj786s7f2jgc/2019-04-29-w7-CBS.zip?dl=0

That log is too old. Open the CBS.log file and clear it. Attempt to update. That should produce another CBS.log. Attach its contents.

That log is too old. Open the CBS.log file and clear it. Attempt to update. That should produce another CBS.log. Attach its contents.

Ouch. I logged in as admin so can open it and see that it started yesterday.

If you're willing, you can actually see today's work in the cbs.log - just use Find for "2019-04-29 13:57" no quotes.
But I saw something totally surprising: I don't even think it was installing the file I downloaded from the catalog.
Instead (?) it was using something from the cache which I saw few lines under that 13:57 time stamp. I searched looking for a file on volume M: where I placed it and haven't found it in the log
Software distribution report says it failed at 14:08:48.

I'm back as limited user now. Please advise what and how to do next step.
Not clear if to do select all/delete text in that file or to delete the entire file.
Also should I be zipping the entire CBS directory again for you or just cbs.log file?

Edited by tos226, 29 April 2019 - 09:16 PM.

Attempt to update and if it fails, upload the CBS.log and the WindowsUpdates.log located in the Windows folder.
 
Lets clean-up also the installer:
 
Download and run the Windows Installer CleanUp Utility 7.2. Once done try the updates again.

Attempt to update and if it fails, upload the CBS.log and the WindowsUpdates.log located in the Windows folder.
 
Lets clean-up also the installer:
 
Download and run the Windows Installer CleanUp Utility 7.2. Once done try the updates again.

Is there a way to run Notepad as admin, or do I have to login to admin account? I suppose you just want me to delete all text in the cbs.log file, right?

I guess I should try that cleanup and then try update again, right?

 

Attempt to update and if it fails, upload the CBS.log and the WindowsUpdates.log located in the Windows folder.
 
Lets clean-up also the installer:
 
Download and run the Windows Installer CleanUp Utility 7.2. Once done try the updates again.

Is there a way to run Notepad as admin, or do I have to login to admin account? I suppose you just want me to delete all text in the cbs.log file, right?

I guess I should try that cleanup and then try update again, right?

 

That is correct. All tools should be ran as an Administrator.

 

 

Attempt to update and if it fails, upload the CBS.log and the WindowsUpdates.log located in the Windows folder.
 
Lets clean-up also the installer:
 
Download and run the Windows Installer CleanUp Utility 7.2. Once done try the updates again.

Is there a way to run Notepad as admin, or do I have to login to admin account? I suppose you just want me to delete all text in the cbs.log file, right?

I guess I should try that cleanup and then try update again, right?

 

That is correct. All tools should be ran as an Administrator.

 

last question for today - how to make sure it uses MY file the one from the catalog and not some cashed version?

It will only work on the mounted volume.