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

Hi,

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, *Wink

 

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.

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.

 

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

 

Hi,
@dencal : yes we did see those postings but the same answer still applies.

Cheers, *Wink

 

Hi,

Furthermore, this is simply not true.
I have this issue on one machine yet not so on another one even both were clean installed using the same MS IP ISO so, YMMV, right ?

Cheers, *Wink

 

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

I wish the same to you *Smile

 

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

 

Crazy, meaningless "How many angels can dance on the head of a pin" polemicals!

The only system executable in 15063.11 that has changed its version from 15063.0 to 15063.11 and its date from 18th March 2017 to 25th March 2017 is ntoskrnl.exe.






All the others are exactly as installed with the datestamp18th March 2017, and the version 15063.0

Winver (and desktop app Help About dialogs) get their data from various registry entries including the UBR value in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion

UBR=Update Build Revision

I believe if you wish, you can edit entries on that page at your peril.

 

Download this regkey to make it easy.
After downloading the zipfile, open the zipfile and click the reg key “add to right click menu“.
Once that’s done, you have an install function for updates in your right click menu.
Advertisement



It makes updating a bit easier.

Download: install-update-to-right-click-menu

 

That WD definition update refused to install before cumulative update and after so cumulative update is probably not to blame. I installed it manually (twice) and system refused it on next auto update try. After that registry change (fix) it was accepted and further updates went thru.

 

By my last count, since I am the only human capable of duplicating this feat with recurring precision, the number of angels that can *comfortably* sit on the head of a # 5 pin is....4,776. Note I said "comfortably." There are several definitions of "comfortable"--some of which result in the number reducing to 3,433 and some increasing the number to a shade over 5,000 ASOTHOAP. Scientists differ, of course, according to their various predilections about these things--like whether global warming amounts to climate change or simply amounts to cyclical weather patterns dependent on the behavior of our sun. At any rate, the controversy over what is "15063" and what is "15063.11" seems to have finally been resolved, at long last...*Wink (And finally, the world sleeps....ZZZZzzzzzz....*Wink G'night, all!)

 

Right, until next update.