Windows 10: Cumulative Update KB4016250 for Windows 10 v1703 Build 15063.11

Fed up with manually updating Defender.
Not wishing to compromise computer with its M$ account details plus other safety concerns have installed my preferred Free Anti-virus.

 

- here also..*Confused

 

Don't understand, worked once but still a problem. I'd like to compare some notes. I think it went like this: At the time I got a notice that 15063.11 was available, notice that there was an WD definition update was already there in the list above 15063.11 notice but this update installed first and only than WD update refused to work. It may be that WD update was meant for 16063.0 and people that installed it earlier don't have such a problem.
I would also like to know if ones having problem with WD update also have a problem with sfc /scannow ? It may be some connection there.

 

I think that every time an update of Defender appears the same error will reappear, in my case I have no problem with sfc /scannow.

 

See post #14

 

Using alternative AV no longer have update problem.

 

So, you think there's no connection ?



And log seems to show that everything was fixed. Ok, those things may get fixed up with next update, will not fret about it as all other things are good.

 

I turn Wds defender OFF for now ....
But NO "Cumulative Update for Windows 10 Version 1703 (KB4016250)(15063.11)" show up yet" ...?

 

Think Defender is buggy.
Only other malfunction have had was shut down did not work, it kept reopening so had to pull the plug, restarted, messed about with power options, this seemed to settle it after switching different settings before reverting to default...reported it.

 

The definitions for the failures

0x80246007 -2145099769 WU_E_DM_NOTDOWNLOADED The update has not been downloaded.

0x80070643 -2147023293 ERROR_INSTALL_FAILURE


Roy

 

Your attachments are Build 1605....We are dealing with Build 1703...see attachment....yours is Windows Defender....now its Windows Defender Antivirus.

 

Temp fix:
Delete following registry key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MpSigStub
Run update again.

 

Making temporary fix's does not stop the problem in the first place.

Need to find out what the root cause is .
from the CBS log


Roy

 

That did it, just have to restart after reg change.

 

Peculiar how systems differ as my 15063.11 WD updates have never faltered.