May 14, 2019 - KB4499175 (Security-only update) for Windows 7

[Brink]

May 14, 2019 - KB4499175 (Security-only update)

Applies to: Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1

---

Improvements and fixes

This security update includes quality improvements. Key changes include:

• Provides protections against a new subclass of speculative execution side-channel vulnerabilities, known as Microarchitectural Data Sampling, for 64-Bit (x64) versions of Windows (CVE-2018-11091, CVE-2018-12126, CVE-2018-12127, CVE-2018-12130). Use the registry settings as described in the Windows Client and Windows Server articles. (These registry settings are enabled by default for Windows Client OS editions, but disabled by default for Windows Server OS editions).
• Addresses an issue that may prevent applications that rely on unconstrained delegation from authenticating after the Kerberos ticket-granting ticket (TGT) expires (the default is 10 hours).
• Security updates to Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Storage and Filesystems, Windows Cryptography, Windows Wireless Networking, Windows Kernel, Windows Server, and the Microsoft JET Database.

For more information about the resolved security vulnerabilities, please refer to the Security Update Guide.

Known issues in this update

Microsoft is not currently aware of any issues with this update.

How to get this update

Before installing this update

Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest Rollup. SSUs improve the reliability of the update process to mitigate potential issues while installing the Rollup and applying Microsoft security fixes.

If you are using Windows Update, the latest SSU (KB4490628) will be offered to you automatically. To get the standalone package for the latest SSU, search for it in the Microsoft Update Catalog.

Install this update

This update is now available for installation through WSUS.

To get the standalone package for this update, go to the Microsoft Update Catalog website.

Source: https://support.microsoft.com/en-us/help/4499175

Direct download links for KB4499175 MSU file from Microsoft Update Catalog:

:ar: Download KB4499175 MSU for Windows 7 32-bit (x86) - 72.3 MB

:ar: Download KB4499175 MSU for Windows 7 64-bit (x64) - 100.5 MB

 

[Brink]

See also (included in KB4499175):

Prevent a worm by updating Remote Desktop Services (CVE-2019-0708) – MSRC

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0708

 

[lehnerus2000]

Hi Brink
Thanks for the links.

These W7 Security Only updates are cumulative, aren't they?
I don't need to keep copies of every patch?

See also (included in KB4499175):

Thanks for this link too.

 

[Brds7t7]

Hi Brink
Thanks for the links.

These W7 Security Only updates are cumulative, aren't they?
I don't need to keep copies of every patch?

Thanks for this link too.

The Security-only updates aren't cumulative, you need to install every patch one after the other. Best to make a batch script to automate the task if you need to install many in one go.
If it's a clean install you can also slipstream the updates into the ISO, or use WSUSOffline with the "Use Security-only updates instead of monthly rollups" option ticked.

The monthly rollups are cumulative, so you only need the latest of those.

The IE updates are cumulative too, so again you only need the latest.

 

[lehnerus2000]

Thanks Brds7t7

The Security-only updates aren't cumulative, you need to install every patch one after the other. Best to make a batch script to automate the task if you need to install many in one go.
If it's a clean install you can also slipstream the updates into the ISO, or use WSUSOffline with the "Use Security-only updates instead of monthly rollups" option ticked.

The monthly rollups are cumulative, so you only need the latest of those.

The IE updates are cumulative too, so again you only need the latest.

Thanks Brds7t7.

I was just wondering if I could clear out some space in my Downloads partition.
I haven't installed any updates after December 2017 (since a lot of them have been defective).

Whilst I have successfully created new XP ISOs, I've never had any success creating W7 ones.

 

[Brds7t7]

I don't bother slipstreaming the updates anymore. I just keep WSUSOffline up to date every few months.
If I do a clean install, I just run that after to get the Security-only updates installed, then do the optional updates I want later on.

It does add about an hour on to the install time, but I'm not that bothered, I just leave it running and go do something else instead of waiting.

I've kept backups of every Security-only update since the servicing model change, organised by year/month. Just in case I ever need any in future.

Once 7 is EOL next year, I'll probably create a final ISO with all updates included.

 

[lehnerus2000]

I've kept backups of every Security-only update since the servicing model change, organised by year/month. Just in case I ever need any in future.

Same here.

 

[SIW2]

Same here.

Easier to use Simplix - he has done the work for you.

 

[Brds7t7]

My only issue with Simplix is that I can't see any option of installing the Security-only updates. Only the latest rollups seem to be included in the list of updates.

WSUSOffline has the option of selecting whether you want the Rollups or the Security-only updates, so that's the one I've always stuck with.

Unless I'm missing something on the website, but I couldn't find any details regarding installing the Security-only updates.

 

[Brink]

Windows 7 patch warning: Antivirus clash causing PCs to freeze | ZDNet

 

[c1wffe]

I don't bother slipstreaming the updates anymore. I just keep WSUSOffline up to date every few months.
If I do a clean install, I just run that after to get the Security-only updates installed, then do the optional updates I want later on.

It does add about an hour on to the install time, but I'm not that bothered, I just leave it running and go do something else instead of waiting.

I've kept backups of every Security-only update since the servicing model change, organised by year/month. Just in case I ever need any in future.

Once 7 is EOL next year, I'll probably create a final ISO with all updates included.

Hi Brds,

I am attempting to use WSUSOffline and have managed to download the security only updates for for my Windows 7 pro along with runtime libraries and Net frameworks.

I think I pretty much understand most of it but I have little to no experience when it comes to file permissions. According to the directions, specifically, "The WSUS Offline Update folder where the files are extracted to must be configured as a shared folder with read permissions granted to the Anonymous security group. (This is the only change that must be made manually, all others below will be made automatically by WSUS Offline Update)."

Would you be so kind as to give me some idea as to what I must do per the above to have the system reboot when necessary and have WSUSOffline continue the update where it left off after the reboot. Perhaps this not necessary I don't have a clue.

 

[Brds7t7]

Strange, I haven't come across that error before. Are you running the downloader (Updategenerator.exe) or the installer (Updateinstaller.exe)?

Also, are you running it from an Admin account or standard user account? When I run it from an admin account, it just downloads/installs automatically. You need to have the option for "Auto reboot and recall" checked when running the installer, it then sets up an account called WOUTEMP, runs the installer from that account, then deletes the account.

 

[c1wffe]

Strange, I haven't come across that error before. Are you running the downloader (Updategenerator.exe) or the installer (Updateinstaller.exe)?

Also, are you running it from an Admin account or standard user account? When I run it from an admin account, it just downloads/installs automatically. You need to have the option for "Auto reboot and recall" checked when running the installer, it then sets up an account called WOUTEMP, runs the installer from that account, then deletes the account.

I think I created some confusion, my bad.

This is not an error I received but rather a quote from the "how to use... " at this link: How to use WSUS Offline Update for Windows clients and servers - TechRepublic

I managed to get as far as the completed download of the Security Updates to a thumb drive but have not yet attempted an install yet. The above and not understanding what I should do brought me to a stop.

I ran the downloader from an Admin account per the aforesaid linked instructions. It would seem that I am more confused then I thought. I wouldn't run the installer until after a full image of my drive.

Thanks for taking the time to reply.

 

[Brds7t7]

Ah sorry, I thought that was an error you were encountering while the installer was running!

I wouldn't worry about shared folders. It's an easy program to use. Just download the updates (which you've already done), then on a new install all you have to do is open the client folder, click updateinstaller and go grab a drink and let it do its thing!

 

[c1wffe]

Ah sorry, I thought that was an error you were encountering while the installer was running!

I wouldn't worry about shared folders. It's an easy program to use. Just download the updates (which you've already done), then on a new install all you have to do is open the client folder, click updateinstaller and go grab a drink and let it do its thing!

As usual I'm over thinking this. I'll go with your suggestion. However, this will not be on a new install but rather a catch up on security updates for an existing install. I'm way behind.

Thanks again for the taking your time to explain this.

 

[Brds7t7]

However, this will not be on a new install but rather a catch up on security updates for an existing install. I'm way behind.

I haven't actually used it on an existing install, as I usually keep mine up to date (although, I do wait a few weeks before installing any MS updates these days). But, I believe it works just as well for keeping existing installs up to date.

 

[c1wffe]

I haven't actually used it on an existing install, as I usually keep mine up to date (although, I do wait a few weeks before installing any MS updates these days). But, I believe it works just as well for keeping existing installs up to date.

I'll probably give it a go over the weekend. I'll let you know how it went. I quit updates when things didn't seem to work and never updated since. The results should be interesting.

 

[c1wffe]

After resolving some life things that just had to be done I finally got up the nerve to try this and all seems to have worked out well. However it did give a few times that I wondered if I would regret it. During the up date the monitors stopped working off and on, mostly off but everything seems to be OK after a reboot only time will tell. This maybe because I ran the updates from a thumb drive with resume after restart. It also should be noted that this is a HP machine with most everything HP removed.

I checked for windows updates through the standard method and it returned two important updates, KB 4487078 and KB 4503292. Any word as to problems with these? I'm not sure if KB 4503292 is just a security update or not which is all I want.

Thanks for your help Brds, I appreciate it.

 

[Brds7t7]

No problem mate
KB4503292 is the June Windows monthly rollup. I don't install those and just stick with the Security-only updates.

The other is a .NET Framework rollup, those I do install every month.

 

[johnhoh]

During the up date the monitors stopped working off and on

That happens when the display adapter driver is being updated