Windows 10 Servicing Options for Window 10 Pro update blurb  

Hello,
Running Windows 10 Pro 1511 10586.545. On the 10th the system updated :
Security Update for Windows 10 Version 1511 for x64-based Systems (KB3172729)

Windows Malicious Software Removal Tool for Windows 8, 8.1, 10 and Windows Server 2012, 2012 R2 x64 Edition - August 2016 (KB890830)

Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3176493).

I had updates on automatic. Subsequently I one Blue apology screen, otherwise all seemed fine until this morning. I left the computer for about 10 minutes and upon my return, it was rebooting. Nothing I had been doing should have caused that. The rebooting process was quite overly long as if it was installing an update. Once back up, I checked for any updates and none were shown. I began investigating and identified that I had 1511 and the Windows update info page show it correctly and another version ?Anniversary Version? 1607. I noticed this section:

Not knowing if the 1607 upgrade would cause the loss of my Pro version I looked and could not understand the above Windows 10 Servicing policy.................................... Why should/would I defer upgrades ???

I decided to solicit some help here on the forum. Unfortunately while typing my first attempt question, my computer did another Blue Apology screen crash.

I am mainly concerned about the unsolicited and as yet unexplained lengthy restart. Also about why the Servicing Policy would mention Windows 10 Pro and the difference from I am assuming a normal Windows 10 upgrade.
I hope someone will take the time to assist or explain.
glennc

As I understand things, Windows 10 Pro gives users the ability to kinda, sorta customize how updates and upgrades are handled. I'm running 10 Pro v1511. When I click Start > Settings > Update & security > Advanced options, I see this dialog box:



You can choose to have updates installed automatically (recommended by Microsoft) or you could have Microsoft notify you to schedule a restart when it's most convenient for you. You can also select how updates are delivered. You can select to receive updates from one source (Microsoft) or from more than one source. (Microsoft says this could speed up app and update downloads.)

But also on the above dialog box is an option to Defer upgrades. An upgrade is when Windows 10 receives a major overhaul (like going from v1511 to v1607.) Some folks want to wait a while to make sure the bugs are ironed out and they don't want updates downloading/installing the latest upgrade.

As far as a lengthy restart after installing the latest updates, all I can tell you is my computers took an average of 30 minutes to finish the process. I'm guessing that was due in part to my ISP's download speed as well as the scan done by Microsoft's monthly Malicious Malware Removal Tool.

I hope this helps a bit. If not, I apologize for taking up your time.

Hello marsmimar,
Thank you for your time and your response. My system is the same as yours! Thanks for clarifying the update features. I am afraid that the unusual and lengthy restart is not explained as yet.
Do you know when v1511 was released? Also my wife's Windows 10 laptop did a update to 1607 after I wrote the first post of this thread.
Still confused. Thanks again!
glenn

Update - another blue screen and another internal error message and reboot

glennc said:

Hello marsmimar,
Thank you for your time and your response. My system is the same as yours! Thanks for clarifying the update features. I am afraid that the unusual and lengthy restart is not explained as yet.
Do you know when v1511 was released? Also my wife's Windows 10 laptop did a update to 1607 after I wrote the first post of this thread.
Still confused. Thanks again!
glenn

If I may: Version 1511 was released in November 2015. The latest is Version 1607 for July 2016, actually released on August 2, 2016 [after the weekend?]. Version 1607 is somewhat slower reaching everyone than some released builds have been.

Berton said:

If I may: Version 1511 was released in November 2015. The latest is Version 1607 for July 2016, actually released on August 2, 2016 [after the weekend?]. Version 1607 is somewhat slower reaching everyone than some released builds have been.

Thank you Berton! My system didn't show any updates. I am still concerned about the lengthy reboot and the blue screen error increase. Hope it sorts itself out......... Take Care

I checked my reliability history and it showed multiple "Windows improperly shutdown" as Critical Events, on the day of the inertial incident and numerous days since. This would explain my unusual reboots and the beginning of this series of events.
What is the Microsoft .Net Native Framework Package 1.2.23205.0? It shows, if I am reading it correctly, that on 8/22/16 the incident day, that it was successfully updated. The same time my problems began.
Any ideas?
Thanks for any assistance

Microsoft's .net framework and its various components have been a source of problems for many years, specifically during updates. Your issue could be the result of a failed, damaged, or corrupted .net framework update. I found this old Ten Forums thread that links to a Microsoft Answers thread in post # 3. The Microsoft Answers thread gives two possible methods to fix things. (The author is a Microsoft Forum Moderator and a Microsoft Support Engineer so the info should be valid.)

Method 1 uses the built-in Windows Troubleshooter. Method 2 uses more of a brute force work around to reset Windows Update components. Please note that there appears to be a typo in Method 2, Step 3. There should be a space in between ...SoftwareDistribution and SoftwareDistribution.bak (in other words the correct command line should look like:
Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak)

As always I suggest that anyone making systgem changes create a new System Restore Point, or better yet, a System Image, just in case.

A quick google search for "Microsoft .Net Native Package 1.2.23205.0 constantly updates" showed this to be a fairly widespread issue. Most of the comments point to a bug with the Windows Store. The general consensus is it's harmless (albeit, annoying) and Microsoft will someday fix it after fixing more pressing problems with Windows 10.

Several of these websites offer specific tools or utilities to fix the constant updates but I would be hesitant to try any of them without a new restore point or system image. In the alternative, Microsoft has released a specific troubleshooter for the Windows Store. This article gives more info.