Windows 7 SP1 & Windows 8.1 Rollup Update August 2016

[Jordan]

 

Windows 7 SP1 & Windows 8.1 Rollup Update August 2016

 

The August 2016 update rollup includes some new improvements and fixes for the Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1 platform. We recommend that you apply this update rollup as part of your regular maintenance routines.

 

For Windows 8.1, the new update KB3179574 does not replace the previously released KB3172605. The change log is as follows:

• Addressed issue that causes Windows Gateway to remain disconnected instead of failing over when a failure occurs.
• Addressed an issue that didn’t prevent other applications from using the desktop area used by application desktop toolbar (also called “appbar”) when run as a RemoteApp.
• Addressed an issue with OLE drag and drop in SharePoint after installing KB3072633, that prevents the download of a file by dragging and dropping it from Internet Explorer to Windows Explorer.
• Addressed issue in the Windows kernel that causes Skype for Business (previously known as Lync) to stop working.
• Addressed issue that prevents the disabling of read or write access to removable storage media when the Audit Removable Storage Group Policy is enabled and prevents applying a Group Policy at the user level.
• Addressed issue that causes the loss of available memory when running queries using the domain name service (DNS).
• Improved performance by addressing an issue that was causing duplicate broadcast data packets to be received by each network interface card (NIC) and sent to applications, when NIC Teaming or Load Balancing/Failover (LBFO) is set-up in active/passive mode.
• Addressed issue that prevents the automatic deletion of Extensible Storage Engine (ESE) transaction logs after reaching the threshold. The issue can occur if ESE transaction logs are being taken periodically such as Dynamic Host Configuration Protocol (DHCP).
• Addressed issue that sometimes causes backups to fail or servers to hang with drivers that use the IoVolumeDeviceToDosName() routine.
• Addressed issue that was resulting in a spike in DNS entries, when DNSSEC validation is enabled in an environment where there were queries for nonexistent DNS records in domains where the DNS servers have conditional forwarders.
• Addressed issue with domain controllers that periodically reboot after a Local Security Authority Subsystem Service (LSASS) module fault, causing the interruption of application and services that are bound to the domain controller at that time.
• Addressed issue with DNS servers that get stuck in a loop and stop responding to DNS queries.
• Addressed issue with cluster services that stop working when network loss logging occurs. This occurs when a network connection is down and virtual machines (VM) are configured with one possible owner.
• Addressed issue that allows users to change a password from an external network via Wireless Application Protocol (WAP) when Proxy Enabled is set to No. This happens in an environment that uses Active Directory Federation Services (ADFS) and Web Application proxy (WAP) for authentication.
• Addressed issue with data loss if a failover occurs when a Network File System (NFS) client tries to write data to an NFS server.
• Addressed issue in Server Message Block (SMB) server that causes the server to crash intermittently with error 0x50.
• Certificate logon fails with error code 0xC000006D (error message: “The attempted logon is invalid. This is either due to a bad username or authentication information.”) or 1326 (error message: “Logon failure: unknown user name or bad password.”) This problem may occur if there are multiple certificate logon attempts being processed simultaneously by a Windows Server 2012 R2 Domain Controller.
• Addressed issue that causes the server to bugcheck when mounting an NFS share after installing KB3025097.
• Addressed issue with users seeing an “Access Denied” error message, when trying to access a domain DFS namespace (for example, \\contoso.com\SYSVOL) on a computer that is configured to require mutual authentication (by using the UNC Hardened Access feature).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.
• Addressed issue that causes domain controllers (DC) to stop working when generating compounded tickets.

 

 

For Windows 7, the update got the KB3179573 patch ID. It includes the following changes:

• Improved performance on specific networks that have a high-bandwidth and low latency.
• Addressed issue with users encountering a bugcheck, when trying to access a domain DFS namespace
• (for example, \\contoso.com\SYSVOL) on a computer that is configured to require mutual authentication (by using the UNC Hardened Access feature).

 

DOWNLOAD=========================================================================

 

Download Windows 7 SP1 Update Rollup (2016-08-16) for x86-based Systems

Download Windows 7 SP1 Update Rollup (2016-08-16) for x64-based Systems

Download Windows Server 2008 R2 SP1 Update Rollup (2016-08-16) for x64-based Systems

Download Windows Server 2008 R2 SP1 Update Rollup (2016-08-16) for Itanium-based Systems

Download Windows 7 Service Pack 1 RTM DVD [ISO]

Download Windows 7 Service Pack 1 (32-bit)

Download Windows 7 Service Pack 1 (64-bit)

 

DOWNLOAD=========================================================================

 

Download Windows 8.1 Update Rollup (2016-08-16) for x86-based Systems

Download Windows 8.1 Update Rollup (2016-08-16) for x64-based Systems

Download Windows Server 2012 R2 Update Rollup (2016-08-16) for x64-based Systems

 

===================================================================================

 

Homepage – http://www.microsoft.com

 

SOURCE:

https://www.softexia.com/windows/windows-7

https://www.softexia.com/windows/windows-8-1

http://winaero.com/blog/august-2016-update-rollup-for-windows-7-sp1-and-windows-8-1/

[ben01]

I have a question for you : do these windows 7 SP1 update rollups include telemetry or not ?

 

Thanks for your answer.

[SPECTRUM]

4 minutes ago, ben01 said:

I have a question for you : do these windows 7 SP1 update rollups include telemetry or not ?

 

Thanks for your answer.

 

Windows 7 have telemetry by default even without updates installed.

 

Telemetry was implemented on Windows since XP.

[ben01]

I know. I meant GWX crap.

[Dusktilldawn]

thank you for your effort

but I have a question about those rollups

I applied Convenience Rollup before which size was 477 mb/ for win7 x64 (windows6.1-kb3125574-v4-x64)

aren't those new rollups sizes too small for a rollup

thanks in advance

[D1v1n3D]

Spying on fellow Americans has been around since like 1970 between wiretap and network Taps it's been around before we even got online they've always been on we always go through a hub that goes through their networks that monitors everything we do they just don't enforce everything there's money to be made they are not going 2 enforce having people arrested for the small things that includes piracy but Hollywood has made it a serious issue the government could have given the shit less

[steven36]

23 minutes ago, Dusktilldawn said:

thank you for your effort

but I have a question about those rollups

I applied Convenience Rollup before which size was 477 mb/ for win7 x64 (windows6.1-kb3125574-v4-x64)

aren't those new rollups sizes too small for a rollup

thanks in advance

Non-Security, Update Rollup hotfixes only thats why its so small

Quote

 

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Improved performance on specific networks that have a high-bandwidth and low latency.
• Addressed issue with users encountering a bugcheck, when trying to access a domain DFS namespace (for example, \\contoso.com\SYSVOL) on a computer that is configured to require mutual authentication (by using the UNC Hardened Access feature).
  
  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.

For more info about how to get this update and a complete list of affected files, see KB3179573.

 

https://support.microsoft.com/en-us/help/22801/windows-7-and-windows-server-2008-r2-update-history

[Karlston]

Some more detail from Woody...

Yesterday’s three patches -- KB 3177723, 3179573, and 3179574 -- give clues to what we can expect in October with Microsoft's new Windows updating process

Microsoft's release yesterday of three out-of-band patches -- an "update rollup" for Windows 7, another for Windows 8.1, and a weird time zone change for Egypt -- offers a taste of the problems and advantages of the company's "streamlined" Windows updating procedure unveiled Monday.

 

Microsoft didn't post documentation for the patches until many hours after they went out the automatic update chute, and in the intervening time we discovered a lot about what Win7/8.1 updating will look like starting in October.

 

The patches themselves are remarkable for several reasons. The documentation trail is also worth a gander for experienced Win7 and 8.1 customers.

 

First, the oddball patch: KB 3177723 makes adjustments to Windows to get rid of Daylight Savings Time in Egypt, which canceled DST on July 4, three days before it was scheduled to start. While it's undoubtedly difficult to program time zone changes, Microsoft has done it hundreds of times. The time zone change made it into the latest Windows 10 cumulative updates, released on Aug. 9, so why weren't the Win7/8.1 changes also issued on that day? And -- pardon me, those of you who live in Egypt -- what's so important about a time zone change that it has to appear in an out-of-band patch?

 

The other two patches are remarkable in that both are update rollups, which is like a test flight for cumulative updates. The Win 7 update rollup, KB 3179573, contains a couple of fixes that don't matter to most people. The Win 8.1 update rollup, KB 3179574, has dozens of fixes -- most of which won't matter to you, either.

 

What's notable about these patches: Microsoft has started documenting the changes in a master post. There's no description of the changes in the KB articles; to see what's being changed, you have to go to the Win 7 update history page or the Win 8.1 update history page. That's a big improvement.

 

Those of you who fought for the Windows 10 update history page should feel vindicated. Microsoft didn't start posting Win10 changelogs until the 12th cumulative update for version 1511, build 10586.318 -- a full 10 months after Win10's release. Now it seems we're going to get a changelog for Windows 7 and 8.1's cumulative updates from the get-go. Well done.

 

(Yes, I see where the Win7 history page says "Last Review: Aug. 10, 2016 - Revision: 20" and the Win 8.1 page claims "Last Review: Aug. 10, 2016 - Revision: 32." That's hogwash. In both cases there are two entries on the page, one for July 21 and one for Aug. 16 -- and if they first appeared before Aug. 16, I sure didn't see them.)

 

Also worthy of note: Both the Win 7 and the Win 8.1 update rollups contain fixes for earlier, botched Windows patches. The Win 7 update history page says this latest patch fixes a bug in KB 3161561, a June security patch. The Win 8.1 history page says the latest patch fixes bugs in that same June security patch, as well as KB 3072633, a July security patch.

 

If this is the start of a trend, that's another piece of good news. In the past, it often took a full month before bugs in Windows and Office were fixed -- Win10 cumulative updates appear infrequently and Office 365 security patches are only supposed to get updated once a month. As I've said many times, that's intolerable. A week ago, we found a printer bug in the Windows 10 cumulative updates. If Microsoft sticks to its once-a-month security patching strategy, that bug won't get fixed until September. Similarly, it took Microsoft a month to fix the Excel bug that prevented certain kinds of files from being opened correctly.

 

A acceptability of a one-month lag between security updates is debatable, but a one-month delay in fixing bad patches is inexcusable. Having that delay built into your patching procedure just doesn't make any sense. Perhaps we're seeing a softening of that self-destructive stance by Microsoft.

 

To be sure, many questions about the October change to Windows 7 and 8.1 updating remain unanswered. For example, I don't have any idea what Microsoft is going to do about Internet Explorer. In one of the comments to his "Further simplifying servicing models for Windows 7 and Windows 8.1" TechNet post yesterday, Nathan Mercer says:

We are working to get IE included in the monthly rollup and security-only update but do not have a confirmed schedule yet.

So we now have known exceptions to this new cumulative update vision, with exemptions for .Net, Flash, and IE.

 

For those who wish to retain control of their Win7 and 8.1 systems, the future may not be as bleak as it appears. In that same article, Mercer states:

Unlike the Monthly Rollup, the Security-only update will only include new security patches that are released for that month. Individual patches will no longer be available. The Security-only update will be available to download and deploy from WSUS, SCCM, and the Microsoft Update Catalog.

If I read that correctly, it means that folks who want to keep their PCs patched with security updates may be able to do so, without ceding all control over patching to Microsoft. The mechanism for controlling your own machine would involve blocking all updates and downloading each month's security patches: one month, one download. You wouldn't be able to pick and choose your security patches, but once that month's patches seem to be working, you could download and install them without using Windows Update.

 

There are a million questions about that approach. What if Microsoft pulls a bad patch? What about precedence and fixes for botched patches? The lack of individual patches may drive some third-party patch programs to distraction, if not oblivion. But in general, it may be possible for Windows 7 and 8.1 customers to install only the security updates and ignore all the nonsecurity stuff.

 

Maybe, just maybe, we'll see a time when Win7 and 8.1 users can patch their PCs without also installing the next "Get Windows 10."

 

Tip o' the hat to Susan Bradley

 

Source: A peek at the future of Windows 7 and 8.1 patching (InfoWorld - Woody Leonhard)

 

InfoWorld - Woody on Windows

 

AskWoody.com - Woody Leonhard's no-bull news, tips and help for Windows and Office

[steven36]

There getting ready for Oct they already got the Windows 10 style update pages for Windows 7 and 8.1  there just practicing now,,  the real cumulative updates will come  soon only one more patch Tuesday witch patches after that it will be cumulative update Tuesday 

[LordTemplair]

Sorry, but RollUp = Cumulative Update patch?

 

Edit:

 

For Windows 8.1, the new update KB3179574 does not replace the previously released KB3172605.

 

Solved:   These updates are not cumulative.

[straycat19]

1 hour ago, steven36 said:

There getting ready for Oct they already got the Windows 10 style update pages for Windows 7 and 8.1  there just practicing now,,  the real cumulative updates will come  soon only one more patch Tuesday witch patches after that it will be cumulative update Tuesday 

 

Haven't they had enough practice screwing up the updates and f*cking the users?  They need more practice?  Phew!  Glad I stopped this update nonsense over a year ago. On new machines I am just installing Windows 7 SP1 and applying our GPE and System Center CM lockdowns and they work fine.

[steven36]

55 minutes ago, straycat19 said:

 

Haven't they had enough practice screwing up the updates and f*cking the users?  They need more practice?  Phew!  Glad I stopped this update nonsense over a year ago. On new machines I am just installing Windows 7 SP1 and applying our GPE and System Center CM lockdowns and they work fine.

There not going to stop screwing over Windows 7 and Windows 8.1 users over tell it runs out of updates or you stop doing them like you say . these roll ups show up  as a optional update in windows update anyway next time check for updates they will be there if you want them ,  but once October the 11th comes. all  Windows updates will be like Windows 10 were you get only 2 updates a big giant  cumulative.update and a  malicious software removal tool .

 

If they ever decide to fight piracy everyone is screwed. they can send something through updates that Ajax wont wipe off  like when  they put Watt  in windows 7 and  the only option  you would have is too never update .

[vitorio]

Great effort.

[SPECTRUM]

10 hours ago, ben01 said:

I know. I meant GWX crap.

 

GWX stopped in July 29, is not offered anymore, because the free upgrade to Windows 10 already ended.