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

How to install after download?

 

WD updated this morning normally after registry fix that Vincentwindows suggested and posted. (Post #75)
Thanks Vencent and welcome to TF, started with a bang.

 

Have not had any problems updating Windows Defender on the Insider version....Build 15063.11
It is the Creator Preview which is having problems.....Build 15063.11
Same build different drivers and setup.?

 

I had this issue too. I'm working in a VirtualBox VM so I restored back to the pre-update snapshot and applied the CU again. This time it seems to be clean. Ho Hum!

 

- I am still getting this failed update message for Defender:








- these are the current definition details from Defender
- am I up to date or what?

- the original update Error keeps coming back..!!*Confused

 

After an update this morning:




Try the fix from Vincent's post, worked for me:
Delete following registry key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MpSigStub
Restart computer.
Run update again.

 

- that did it..
- thanks, Mike..

 

I found the update waiting when I shut down last night, it completed successfully when I turned on just now.
Everything seems hunky dory.

 

It seems to have fixed by itself or by Windows Updates.
I have tried it this morning and nothing, now it is installed.

 

Depends on which version installed....Creator Preview will not allow updating Windows Defender unless you delete mpsigstub in the directory.
A clean install Build 1703 from an ISO will allow even though they have the same winver, as it is based on Insider, which is a more advanced O/S.

 

No problems with .11 or with WU. Scannow just completed with no errors. If you have the iso 15063 might suggest a repair reinstall (run it like you were upgrading) from the iso, and see if that will straighten it out...*Wink

 

I am running 15063.11, last clean install 15060, upgraded through 10561 to 15063.0 and now as said .11 yet I have no issues updating Defender definitions with MpSigStub present. I have never removed nor edited it:

 

Here is proof that there are two different version....Creator Preview and Build 1703.
Do note although my Creator version passed scannow it failed dism.
My winver number is different to that in the powershell.

 

I am sorry Dencal but you have now misunderstood something.

Windows 10 Creators Update version 1703 is and will be build 15063. When released, it as most Windows 10 main builds have been when released was .0 version, 15063.0.

Since that we have received the first Cumulative Update for version 1703. As it is only a cumulative update, not new build per se, it only changed the decimal part of the build number bringing it to 15063.11.

Cumulative updates do not change everything in Windows, every tool, app and such. Of course the version numbers only change for those parts that the update has changed. As the Cumulative Update for Windows 10 Version 1703 for x64-based systems KB4016250 did not update for instance DISM tool, it is only natural and logical that its build / version number remained unchanged.

That's what was seen in your PowerShell screenshot.

Short: We are (almost) all running Windows 10 version 1703 build 15063.11:





... but some of its tools are still version 15063.0:





These version numbers are not the same thing than Windows build number. They do usually only change with a build upgrade, not with a cumulative update just patching parts of the system. Current DISM version in Windows 10 version 1703, in its current build 15063.11 is 15063.0.

 

Kari You are vastly more knowledgeable, but taking two of your quotes.

Short: We are (almost) all running Windows 10 version 1703 build 15063.11:
... but some of its tools are still version 15063.0:

Which to my mind mean there are differences.

Going back as far as post #4 reveals problems encountered by many trying to update Defender and install.
The fix was posted post #75.....it worked for others as well as myself.