Repeatedly failed windows updates: Cumulative for Windows 10 Version 1703 x64 KB4056891 and Windows

Djosch

As for the first case, KB4056891, Windows support states:

https://support.microsoft.com/sv-se/help/4056891

 

Due to an issue with some versions of Anti-Virus software, this fix is only being made applicable to the machines where the Anti virus ISV has updated the ALLOW REGKEY.

Contact your Anti-Virus AV to confirm that their software is compatible and have set the following REGKEY on the machine Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc" Type="REG_DWORD” Data="0x00000000”

 

Can this be solved by you?

Djosch

Needless to say, perhaps, I use F-Secure Safe

Ukko

Hello,

 

Looks like that noted Windows Update (KB4056891; for Windows 10 1703 ?!) is related with next one:

https://community.f-secure.com/t5/F-Secure-SAFE/F-Secure-SAFE-and-KB4056892/td-p/103474

with 'KB4056892'-name (for Windows 10 1709).

https://support.microsoft.com/en-gb/help/4056892/windows-10-update-kb4056892

 

So, does it possible to add information about:

-> with your experience -> there is not visible such Registry Entry/Key with your system(?):

Key="HKEY_LOCAL_MACHINE"
Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"
Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc"
Type="REG_DWORD"
Data="0x00000000"

 

If no -> maybe good to re-check build of F-Secure SAFE.

And possible to contact direct F-Secure Support Channels like chat or phone:

https://www.f-secure.com/en/web/home_global/contact-support

for proper clarification or advice.

 

Thanks!

Djosch

I have F-Secure SAFE 17.2 and all updates are done, including the critical Ultralight Core update 2018-01-04_1.

 

So maybe my problem is another one? The repeated failures to install Windows 10 version 1709 either could hint to that direction?

Ukko

---

@Djosch wrote:

I have F-Secure SAFE 17.2 and all updates are done, including the critical Ultralight Core update 2018-01-04_1.

 

So maybe my problem is another one? The repeated failures to install Windows 10 version 1709 either could hint to that direction?

---

Hello,

 

Potentially, yes. But just as clarification -> I'm also only F-Secure user (their home solutions) - so, it is only my own unofficial feelings.

Maybe with your situation possible to re-check Windows Journal about events and their strings about certain 'trouble' (like error codes). And then maybe good to re-check Microsoft/Google Search about such information.

For example, random search query like ""failed 1709"" with some articles and discussions. Where possible to see too much different explanation and reasons for stuck. For example, not enough space on drive; broken Windows Update; and so on.

 

Maybe possible to try this page (as first try):

https://support.microsoft.com/en-gb/help/10164/fix-windows-update-errors

 

Thanks!