KB4474419 will not install

Does anyone know something about this?

I got the same problem and already tried

• manually downloading and installing it (.msu from the Update Catalog)
• performing a clean restart (only Microsoft services and so on)
• installing it with "administrator" account (.msu)
• installing it in safe mode, which of course doesn't work anyway (.msu)
• deleting the latest folders from Windows\Software Distribution\Download, but not its entire content
• well, guess that's it ...

All of this did not work for me.

As sometimes before I encountered problems when USB devices such as cellphones, sticks, HDDs or stuff like that were plugged in when installing some updates, I made sure nothing was connected during these steps.

Any ideas?

Thanks!

Does anyone know something about this?

I got the same problem and already tried

• manually downloading and installing it (.msu from the Update Catalog)
• performing a clean restart (only Microsoft services and so on)
• installing it with "administrator" account (.msu)
• installing it in safe mode, which of course doesn't work anyway (.msu)
• deleting the latest folders from Windows\Software Distribution\Download, but not its entire content
• well, guess that's it ...

All of this did not work for me.

As sometimes before I encountered problems when USB devices such as cellphones, sticks, HDDs or stuff like that were plugged in when installing some updates, I made sure nothing was connected during these steps.

Any ideas?

Thanks!

Same there, Win7 32bit Sp1

Hi,

Same problem on my "Windows 7 - 64 bits".

===============================

Récipient d’erreurs 1944507597, type 433785125

Nom d’événement : CbsPackageServicingFailure2

Réponse : Non disponible

ID de CAB : 0

Signature du problème :

P1 : 6.1.7601.24383

P2 : Package_for_KB4474419

P3 : 6.1.1.8

P4 : amd64

P5 : unknown

P6 : 80004005

P7 : GC

P8 : Staged

P9 : Installed

P10 : WindowsUpdateAgent

Fichiers joints :

C:\Windows\Logs\CBS\CbsPersist_20190219200850.cab

C:\Windows\Logs\CBS\CbsPersist_20190314190835.cab

C:\Windows\Logs\CBS\CbsPersist_20190314212052.cab

C:\Windows\Logs\CBS\CbsPersist_20190315134116.cab

C:\Windows\Logs\CBS\CbsPersist_20190315154251.cab

C:\Windows\Logs\CBS\CBS.log

C:\Windows\servicing\Sessions\Sessions.xml

C:\Windows\winsxs\poqexec.log

C:\Windows\inf\setupapi.dev.log

===============================

Meanwhile - also without any success - I

• uninstalled my virus protection (AVAST Free) - both usual uninstall and removal tool
• did a disk cleanup via Windows, including all the "system files" or how they call it (sorry, I use it in German ... not sure how it's called in English)
• ran sfc /scannow

... and still get the 80004005.

Some thoughts:

The update is about SHA2, as far as I know. So might this maybe be related to any kind of system wide security settings? In the internet options or such?

I'm just wondering as the problem doesn't seem to be user related or to depend on whether an anti virus is active or not.

Still open for ideas. ;)

Oh, and here the link to the Update Catalog, so you don't have to search.

Funny thing ... it seemingly worked for me now.

The problem is that I cannot tell you how.

Here's what I did - maybe it can help someone to think of things to try:

As I said, I removed my AVAST Free. Instead I installed Microsoft Security Essentials, which didn't make much of a difference regarding this issue. So I tried to install KB4474419 a few more times and then thought like "screw that, W7 won't be supported for long anyway, let's get Windows 10".

But as I tried earlier (version 1703 or sth like that) and encountered several problems (older hardware), I first booted up Acronis True Image 2016 and got myself a clone of my entire system disk.

So I installed Win 10, had the same problems as last time and decided to go back to 7.

During the installation of W10 I also came to remember I got this old small HDD plugged in on which I once had Ubuntu running. And yeah, right, the GRUB loader always appeared for like a second when booting. Now it didn't, as the Win 10 installation routine must have overwritten it in the boot sector or whatever.

So I disconnected the Linux HDD, booted Acronis again, recovered my system disk using the clone I created before and - more or less just for fun - started the installation of KB4474419 from the .msu on my desktop again.

Well ... it just worked this time.

The system asked for a reboot, I confirmed, it rebooted and no "error" and stuff ... it seems to be installed.

Sorry, German. Just for you to see I don't make up stories or such. ;)