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.
KB4474419 will not install
KB4474419 will not install - error code 80004005
Windows for home | Previous Windows versions | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
77 answers
Sort by: Most helpful
-
Anonymous
2019-03-17T21:09:15+00:00 -
Anonymous
2019-03-17T20:05:11+00:00 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.
-
Anonymous
2019-03-16T22:04:11+00:00 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. :)
-
Anonymous
2019-03-16T21:15:10+00:00 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!
-
Anonymous
2019-03-16T16:30:18+00:00 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. ;)