Discussion in 'other software & services' started by Daveski17, Nov 12, 2014.
Your 2 other machines are smart, maybe your 3rd machine should learn from them
My other machines aren't smart they are just different.
Unfortunately your comment doesn't really give any insight as to what may be causing this Win Updates issue.
My machine uses Emsisoft. I tried with Emsisoft "down protection" mode and the update still failed.
I use Emsisoft on the 2 machine that don't get the error.
Microsoft Patch Alert: January patches include a reprisal of KB 4023057 and a swarm of lesser bugs by Woody Leonhard.
Successful update to W10 v.1809 via Update Assistant. No issues. No settings changed.
Some additional info here =
Thanks for that link anon.
I downloaded the latest Defender definition update from here and it shows as updated to latest version inn the Security Center/Virus and Threat info.
However it still shows the same error in the main Windows Update page. So it would seem that it is an error in how Defender is interacting with Win Updates.
No problem here with Store app updating on Win 10 x(64) 1809. Maybe everyone should just "dump" WD and install a third party AV.
Lots more people affected than first thought.
Apparently changing your DNS might help solve the issue.
Do you still get an error? Have you tried the above?
I changed my DNS settings to use cloudflare 126.96.36.199 and 188.8.131.52 and check for updates worked successfully (though there were no updates).
Will keep it like that for now until BT's UK DNS server is fixed, then will switch back to them.
No I haven't. I am leaving it alone so I can tell when it gets auto fixed by Microsoft. They cannot expect all affected users to change their DNS, a lot of folk don't even know what DNS is.
In the mean time I am just downloading latest Defender defs and installing them. They show up in the Security Center's Virus and Protection info as being installed.
Windows 10 updates are broken again, but this time it's not Microsoft's fault
Per the zdnet.com article:
I would say the SmartScreen issue is the most serious issue to WD users. As AV lab tests have shown, WD protection capability is significantly reduced w/o SmartScreen active.
The January Windows and Office patches are good to go by Woody Leonhard.
Windows 10 Update Continues Having Issues After DNS Fixes
February 4, 2019
Windows Update problems: Fixed now but here's what went wrong, says Microsoft
February 5, 2019
Wow, good info. Thanks mood.
For those that can't disable Win 10 virtualization via BIOS/UEFI, I found a reg. setting that might turn it off. Worth a shot. The screen shot is from Win 10 x(64) 1809 but I assume the same key also exists on 1803:
The value of that is 0 for me, yet task manager says I have virtualization enabled (cpu tab from performance tab), and I have activated it from bios. Hmm...
Appears this registry setting controls UAC file and registry virtualization write failures. What that really means I am not sure at this point. Appears the recommended setting is "0" but this might be dependent upon if Hyper-V is fully enabled which it is not on my PC? Also the reference is for Win 8.1 and things might have changed in regards to Win 10.
Per Microsoft, the setting should show disabled: https://docs.microsoft.com/en-us/windows/desktop/sysinfo/registry-virtualization . Go figure?
Might be useful for some.
It's time to block Windows Automatic Updating
Separate names with a comma.