There will be no more individual updates like there are now, instead there will be 'Monthly Rollups' as there are on Win 10
So the ability to pick and choose updates will go it seems.
Latest info here...
There will be no more individual updates like there are now, instead there will be 'Monthly Rollups' as there are on Win 10
So the ability to pick and choose updates will go it seems.
Latest info here...
Ahhh, well.
Will now be even MORE difficult to avoid microsoft sponsored PUPs.
- That article points to this webpage with info on the .NET software.
https://blogs.msdn.microsoft.com/dotnet/2016/08/15/introducing-the-net-framework-monthly-rollup/
July 2016 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
--> 103 MB
optional update includes following kbs
August 2016 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
--> 29 MB
optional update
- My personal opinion is that MS should release a new Service Pack for both Win 7 & Win 8 BEFORE it starts releasing those "Monthly Roll Up" updates. That would provide a clean solid foundation for those new monthly rollups. Especially because e.g. Win 7 is still supported until 2020 (???).
sp2 is long overdue
- Agree. A new Service Pack for both Win 7 & Win 8 is indeed long overdue. But I fear we won´t get it.
- More info on those "Roll Ups" and the Win 10 update policy/policies.
https://blogs.technet.microsoft.com/askpfeplat/2016/08/30/a-bit-about-the-windows-servicing-model/
Remove software related to the Windows 10 free upgrade offer (kb3184143 for w8.1) --> 23.6 MB
This update replaces the following previously-released software:
KB 3035583 – Update installs Get Windows 10 app in Windows 8.1 and Windows 7 SP1
KB 3064683 – Windows 8.1 OOBE modifications to reserve Windows 10
KB 3072318 – Update for Windows 8.1 OOBE to upgrade to Windows 10
KB 3090045 – Windows Update for reserved devices in Windows 8.1 or Windows 7 SP1
KB 3123862 – Updated capabilities to upgrade Windows 8.1 and Windows 7
KB 3173040 – Windows 8.1 and Windows 7 SP1 end of free upgrade offer notification
KB 3146449 – Updated Internet Explorer 11 capabilities to upgrade Windows 8.1 and Windows 7
Key changes include:
Using this setting is not recommended because it may cause problems for your applications.
The default value for the timeout is two minutes. To change the timeout use the WinHttpSetOption function with dwOption set to 135. This option can only be set on a session handle before any connection handles or requests are created for the session. Once connection handles or requests are created, this value can’t be modified. For more info, see WinHttpSetOption function.
Log Name : Security
Source : Microsoft-Windows-Security-Auditing
Date : date time
Event ID : 4656
Task Category : task category
Level : Information
Keywords : keywords
User : N/A
Computer : computername
In addition to installing this update on the KMS Host, a KMS generic volume license key (GVLK) that is designed to support the Windows 10 Anniversary Update-based LTSB or Windows Server 2016 clients also needs to be installed. Information about the associated KMS GVLKs for these products will be listed in Appendix A: KMS Client Setup Keys, when they become available.
The KMS GVLKs that support the new versions of Windows will also support previous volume licensing editions of Windows that are acting as KMS clients. For more info about using a Customer Support Volume License Key (CSLVK) for installation, see this article.
August 2016 update rollup for Windows 8.1 and Windows Server 2012 R2 (kb3179574)
Key changes include:
This problem may occur if the selected domain controller has security update KB3161561 installed, and if the SmbServerNameHardeningLevel registry entry is configured to a non-zero value on the domain controller.
September 2016 update rollup for Windows 8.1 and Windows Server 2012 R2 (kb3185279)
Key changes include:
July 2016 update rollup for Windows 7 and Server 2008 R2 SP1 (kb 3172605)
Key changes include:
August 2016 update rollup for Windows 7 and Server 2008 R2 SP1 (kb 3179573)
Key changes include:
This problem may occur if the selected domain controller has security update KB3161561 installed, and if the SmbServerNameHardeningLevel registry entry is configured to a non-zero value on the domain controller.
September 2016 update rollup for Windows 7 and Server 2008 R2 SP1 (kb 3185278)
Key changes include:
Windows 7 ,8 and 8.1 users really should read this to try and understand the big change that is coming tomorrow. It is big. It will affect you.
And, as it is Microsoft, it is a bit complicated so cup of coffee and start reading.... it could help you in the future.
- That article (See post #17) contains an interesting piece of text:
"Microsoft’s been working on the mechanics of the patching process for the past few months. You might not have noticed, but Microsoft already has support pages with the details for Win7 and for Win8.1.
Win7 and 8.1 patching has already started morphing. So far we’ve seen three Windows 7 nonsecurity update rollups -- KB 3172605 in July, KB 3179573 in August, and KB 3185278 in September -- that first appeared as Optional/unchecked patches, then were later updated to Recommended patches. As I explained a couple of weeks ago: “the general pattern is to have a cumulative update (er, patch rollup) released as Optional, wait a month to see if anything explodes, and if not, then change it to Recommended the next month.""
Did you have any issues with the install Corona?