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. ;)

La cosa divertente ... a quanto pare ha funzionato per me ora.

Il problema è che non posso dirti come.

Ecco cosa ho fatto - forse può aiutare qualcuno a pensare a cose da provare:

Come ho detto, ho rimosso il mio AVAST gratuito. Grazie di Microsoft Security Essentials, che non ha fatto molta differenza in merito a questo problema. Così ho provato a farlo "avvitiamo, W7 non sarà supportato a lungo comunque, prendiamo Windows 10".

Ma come ho provato in precedenza (versione 1703 o sth in quel modo) e ho riscontrato diversi problemi, Acronis True Image 2016 e mi sono procurato un clone del mio intero disco di sistema.

Così ho installato Win 10, ho avuto gli stessi problemi dell'ultima volta e ho deciso di tornare al 7.

Durante l'installazione di W10 sono anche venuto a ricordare questo vecchio piccolo HDD su cui una volta avevo Ubuntu in esecuzione. E sì, giusto, il caricatore GRUB è sempre apparso per un secondo all'avvio. Ora non è così, come la routine di installazione di Win 10 deve averla sovrascritta nel settore di avvio o altra cosa.

Quindi ho disconnesso l'HDD Linux, ho riavviato Acronis, ho recuperato il mio disco di sistema usando il clone che ho creato e - più o meno solo per divertimento - ho installato l'installazione di KB4474419 dal .msu sul mio desktop .

Beh ... ha funzionato da solo questa volta.

Il sistema ha chiesto il riavvio, l'ho confermato, il riavvio e nessun errore e cose ... sembra essere installato.

Siamo spiacenti, tedesco. Solo per farvi vedere che non inventano storie o cose del genere. ;)

You are great!

Confirm, remove ubuntu disk from first boot device and all work fine!

Wow, great news. I never thought that could really help anyone but yeah ... seems like the Linux disk could be the problem.

Thanks for the feedback. :)

I also have a dual boot (Linux / Windows) on 2 independant disks.

I don't plan to change that.
Still wondering how to fix the windows update problem ...

... maybe disable the dual boot until the update works.

I also have a triple boot (Windows 7/Linux/FreeBSD) and I do not plan to change that, and I am sick of Windows expecting to be the only operating system running on the machine... There has to be a way to update Windows without destroying the rest of my system. This update is supposed to be just a new feature making it possible to use SHA-2 code signing support for Windows Update. I don't see why sharing the computer with other operating systems would be an issue for such a thing.

For me worked setting the disk with windows as first boot device.