Page 10 of 17 FirstFirst ... 89101112 ... LastLast
  1.    02 Apr 2017 #91
    Join Date : Oct 2014
    Posts : 2,456
    W10 Pro + W10 Preview

    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.
    Attached Thumbnails Attached Thumbnails image.jpg   winver.jpg  
      My ComputersSystem Spec
  2.    02 Apr 2017 #92
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,947
    Windows 10 Pro

    Quote Originally Posted by dencal View Post
    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:

    Click image for larger version. 

Name:	image.png 
Views:	104 
Size:	128.2 KB 
ID:	127849

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

    Click image for larger version. 

Name:	image.png 
Views:	104 
Size:	161.5 KB 
ID:	127850

    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
      My ComputerSystem Spec
  3.    02 Apr 2017 #93
    Join Date : Oct 2014
    Posts : 2,456
    W10 Pro + W10 Preview

    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.
      My ComputersSystem Spec
  4.    02 Apr 2017 #94
    Join Date : Oct 2015
    Posts : 2,021
    Windows 10 Pro X64

    Hi,

    Quote Originally Posted by dencal View Post
    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,
    Last edited by fdegrove; 02 Apr 2017 at 16:46.
      My ComputersSystem Spec
  5.    02 Apr 2017 #95
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,947
    Windows 10 Pro

    Quote Originally Posted by fdegrove View Post
    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.


    Quote Originally Posted by fdegrove View Post
    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
      My ComputerSystem Spec
  6.    02 Apr 2017 #96
    Join Date : Oct 2014
    Posts : 2,456
    W10 Pro + W10 Preview

    See my posts #81 and #89......good night
      My ComputersSystem Spec
  7.    02 Apr 2017 #97
    Join Date : Oct 2015
    Posts : 2,021
    Windows 10 Pro X64

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

    Cheers,
      My ComputersSystem Spec
  8.    02 Apr 2017 #98
    Join Date : Oct 2015
    Posts : 2,021
    Windows 10 Pro X64

    Hi,

    Quote Originally Posted by dencal View Post
    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.
    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,
      My ComputersSystem Spec
  9.    02 Apr 2017 #99
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,947
    Windows 10 Pro

    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


    Quote Originally Posted by dencal View Post
    ......good night
    I wish the same to you

    Kari
      My ComputerSystem Spec
  10.    02 Apr 2017 #100
    Join Date : Sep 2014
    Posts : 448
    10 preview 64bit

    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
      My ComputerSystem Spec

 
Page 10 of 17 FirstFirst ... 89101112 ... LastLast


Similar Threads
Thread Forum
Cumulative Update KB3197356 for Windows 10 PC build 14393.223
Source: https://support.microsoft.com/en-us/kb/3197356 Windows Update - Check for and Install in Windows 10 - Windows 10 Forums
Windows 10 News
Insider Cumulative Update KB3194496 for Windows 10 PC Build 14393.222
UPDATE: Download Windows 10 1607 Script fix to unblock update for Windows Insiders from Official Microsoft Download Center Source: Cumulative Update Build 14393.22 for PC and Build 14393.221 for Mobile now available - Feedback Hub How...
Windows 10 News
Cumulative Update KB3189866 Windows 10 build 14393.187
UPDATE: September 20th 2016 Source: Windows 10 update history - Microsoft
Windows 10 News
Cumulative Update KB3176938 Windows 10 build 14393.105
Source: https://support.microsoft.com/en-us/help/12387/windows-10-update-history?ocid=update_setting_client Windows Update - Check for and Install in Windows 10 - Windows 10 Forums
Windows 10 News
Windows 10 Build 10240 - Cumulative Update KB3147461
Windows 10 Build 10240 - Cumulative Update KB3147461 Manually download: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB3147461 Direct download links: x64:...
Windows 10 News
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 16:35.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums