Windows 10: Cumulative Update KB4056890 Windows 10 v1607 Build 14393.2007

Source: https://support.microsoft.com/en-us/help/4056890


*Arrow Download KB4056890 MSU for Windows 10 Version 1607 32-bit (x86) - 630.8 MB

*Arrow Download KB4056890 MSU for Windows 10 Version 1607 64-bit (x64) - 1202.3 MB

:)

 

Repeated failure to update to install update for Windows 10 Version 1607 for x64-based Systems (KB4049411) and (KB4033631)

Those updates should be included in the latest cumulative update for Windows 10 1607. Try downloading and make sure the latest cumulative update - January 3, 2018—KB4056890 (OS Build 14393.2007) - is installed:

http://catalog.update.microsoft.com/v7/site/Sea...

See how to download and install it:

https://www.groovypost.com/howto/manually-insta...

 

Please Help. My PC will not boot properly. Keeps turning itself off at login screen.

Sounds like you are running Windows 10 Anniversary Update version 1607.

January 3, 2018—KB4056890 (OS Build 14393.2007) has since succeeded KB4053579.

You can download and install it from
http://catalog.update.microsoft.com/v7/site/Sea...

 

It seems odd but after this update the media streaming options were turned off, I had to turn it back on before
I could access my media stored on the PC from my TV. First time I've seen this. Coincidence?

Surprised to see this update on this date. Something important it had to be out of band?

 

Hello Dave, *Smile

It's to help with this below:

Kernel memory leaking Intel processor design flaw - Windows 10 Forums

Windows Client Guidance against speculative execution vulnerabilities - Windows 10 Forums

 

I'm running an older AMD processor, the 4300 FX. It's unclear to me from what I've read
whether I'm going to take a performance hit or not. The following quote implies that AMD is not affected.

Thomas Lendacky, a member of the Linux OS group at AMD, posted the following over at LKML:
AMD processors are not subject to the types of attacks that the kernel page table isolation feature protects against. The AMD microarchitecture does not allow memory references, including speculative references, that access higher privileged data when running in a lesser privileged mode when that access would result in a page fault.

 

You could run the PowerShell script from below to see what it reports to help be sure.

*Arrow Windows Client Guidance against speculative execution vulnerabilities - Windows 10 Forums

 

Interesting here's my output. It says hardware support is not available and Windows support is not enabled.
Guess that makes sense. Do I have to now do something to "undo" anything powershell did ?
I do have a system restore point set I did just prior to it's use.

PS C:\Windows\system32> Set-ExecutionPolicy Unrestricted -Scope Process -Force
PS C:\Windows\system32> Install-Module SpeculationControl -Force

NuGet provider is required to continue
PowerShellGet requires NuGet provider version '2.8.5.201' or newer to interact with NuGet-based repositories. The NuGet
provider must be available in 'C:\Program Files\PackageManagement\ProviderAssemblies' or
'C:\Users\davex\AppData\Local\PackageManagement\ProviderAssemblies'. You can also install the NuGet provider by running
'Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force'. Do you want PowerShellGet to install and
import the NuGet provider now?
[Y] Yes [N] No Suspend [?] Help (default is "Y"): y
PS C:\Windows\system32> Get-SpeculationControlSettings
Speculation control settings for CVE-2017-5715 [branch target injection]

Hardware support for branch target injection mitigation is present: False
Windows OS support for branch target injection mitigation is present: True
Windows OS support for branch target injection mitigation is enabled: False
Windows OS support for branch target injection mitigation is disabled by system policy: False
Windows OS support for branch target injection mitigation is disabled by absence of hardware support: True

Speculation control settings for CVE-2017-5754 [rogue data cache load]

Hardware requires kernel VA shadowing: False

Suggested actions

* Install BIOS/firmware update provided by your device OEM that enables hardware support for the branch target injectio
n mitigation.
* Follow the guidance for enabling Windows support for speculation control mitigations are described in https://support
.microsoft.com/help/4072698


BTIHardwarePresent : False
BTIWindowsSupportPresent : True
BTIWindowsSupportEnabled : False
BTIDisabledBySystemPolicy : False
BTIDisabledByNoHardwareSupport : True
KVAShadowRequired : False
KVAShadowWindowsSupportPresent : True
KVAShadowWindowsSupportEnabled : False
KVAShadowPcidEnabled : False



PS C:\Windows\system32>

 

Nothing is needed to do to undo anything from the PowerShell script.

 

It seems this update has caused my desktop to behave very weird.

Most of the time the start menu doesn't work, all programs from Windows take ages to open and when clicking on something a lot they all pop-up immediately and closing them is another pita.

I restored Windows with my 2nd most recent backup.

 

Defer updates selected in settings + Wushowhide from before Jan CU failed to stop 1703 update being downloaded again, and now defer updates greyed out and unavailable. Wushowhide will not run now. Changed the Defer feature updates to enabled with Gpedit.msc.

(when 1703 upgrade runs and installs, Network, Audio, USB, and all except the Generic graphics adapter drivers all fail to work, whilst having worked OK in 1607 - second computer in specs, very old and not worth bothering about, but still usable for general use.)