Cumulative Update KB4016250 for Windows 10 v1703 Build 15063.11 Insider

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.

dencal said:

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

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.

Hi,

dencal said:

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.

Pls. reread @Kari's posting. He is correct. Running a tool such as DISM will show its own build number not necessarily the current Windows build version and updates (the decimals).

That is quite often the case. An update to a build does not update every single file or program of that build. Hence the version numbering discrepancies.

The fix for WD refusing to update correctly is unrelated to this actually.

Cheers,

fdegrove said:

Running a tool such as DISM will show its own build number not necessarily the current Windows build version and updates (the decimals).

Exactly. In case of tools like Command Prompt or DISM and such, it's rather a version number than a build number. Fact is that DISM version in Windows 10 Creators Update version 1703 (currently in build 15063.11) is 10.0.15063.0.

Apples and oranges.

fdegrove said:

The fix for WD refusing to update correctly is unrelated to this actually.

My point exactly. I have none whatsoever issues with Defender definition updates on any of my 10+ Hyper-V virtual machines running a mix of clean installed and upgraded 15063.11, nor have I any issues in physical machines. Why some users have issues, to that I have no explanation.

I just know for 100% that each and every of us running Windows 10, its latest build fully updated is using build 15063.11 with some tools like DISM version being 10.0.15063.0.

Nobody, I repeat: nobody outside Microsoft developer teams, regardless which edition of Windows 10 and if clean or upgrade installed is currently using a DISM version greater than 10.0.15063.0.

That's a fact.

Kari

See my posts #81 and #89......good night

I give up after these facts:

• Current Windows 10 Insider Preview build was released as 15063.0, cumulative update KB4016250 updated it to 15063.11
• Windows 10 Creators Update version 1703 Pre-release version is the same than current Insider build, 15063.0 when released, now after KB4016250 updated to 15063.11. Exactly the same
  
• DISM version on both original release 15063.0 and updated 15063.11 is 10.0.15063.0. No one, not Dencal nor anybody else outside MS developer teams have nor can have DISM version 10.0.15063.11 because such a version of DISM is not released to Insiders or general public
• The Defender definition issue has nothing to do with if user is running 15063.0 or 15063.11 nor has the issue anything to do if Windows 10 is clean or upgrade installed

dencal said:

......good night

I wish the same to you :)

Kari

The
MPSTUB removal is purely a temporary file removal, and CREATED during the D/L install of the definitions file

IT's been a "fix" for at least 7 years that i know of

AND because its only a TEMPORARY file DISM will NOT find it

ITS NOT A W10 PROBLEM -its purely MS AV, there still using the old format

Roy