Cumulative Update KB4016250 for Windows 10 v1703 Build 15063.11 Insider

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.

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.

waltc said:

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... (And finally, the world sleeps....ZZZZzzzzzz.... G'night, all!)

Right, until next update.

fdegrove said:

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,

Do reread my post #89
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.

CountMike said:

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.

Like yourself I did the registry change which seemed to have sorted the problem, unfortunately this morning it again refuses to update.
I think Hawkman,s post #101 .....a valid explanation.

Just checked registry....Mpsigstub has reinstalled itself

Sometimes it is a clever move to unsubscribe a thread to avoid bad mood, possibly insulting or hurting your virtual friends, or just to be sure you do not post a comment using vocabulary that makes you seem a heartless son of ....

Time for me to make that clever move. See you geeks in other threads.

Kari said:

Sometimes it is a clever move to unsubscribe a thread to avoid bad mood, possibly insulting or hurting your virtual friends, or just to be sure you do not post a comment using vocabulary that makes you seem a heartless son of ....

Time for me to make that clever move. See you geeks in other threads.

I sincerely hope you are not referring to me ....I have accepted your explanation, but I believe an "Updated Creator Preview" and a clean ISO installation give different results, this based on my use of both.