June 9th 2015 Windows Updates

Today, as part of Update Tuesday, we released 8 security bulletins.

We encourage customers to apply all of these updates. For more information about this month’s security updates, including the detailed view of the Exploitability Index (XI), visit the Microsoft Bulletin Summary webpage. If you are not familiar with how we calculate the XI, a full description can be found here.

We released one new Security Advisory:
One Security Advisory has been revised:
For the latest information, you can follow the Microsoft Security Response Center (MSRC) team on Twitter at @MSFTSecResponse.

MSRC Team


Source: June 2015 Updates - Microsoft Security Response Center - Site Home - TechNet Blogs

See also: Microsoft Security Bulletin Summary for June 2015
 
Mine were 7 updates and almost a GB in total. Take a look at IE security update:eek:. Everything went smooth as usual for me:).

Image 1.png
 
All seems to have gone well for me, other than the Windows Update process remaining running (and starting back up after killing the process...) after the updates were finished and having to disable Automatic Updates and re-enable them to stop the process so it resumes its original behaviour of ending the Windows Update service 15 minutes after its no longer needed.

But that's a minor thing that's happened only a few times. Should be fine by tomorrow. If not I can just do a system restore to the day before and try again.

Other than that? No major issues, no crashes, nothing.
 
This is probably why the IE 11 update was so large:
In February, we released the first preview of HTTP Strict Transport Security in Internet Explorer 11 in the Windows 10 Insider Preview. The HTTP Strict Transport Security (HSTS) policy protects against variants of man-in-the-middle attacks that can strip TLS out of communications with a server, leaving the user vulnerable.

With today’s monthly security updates (KB 3058515), we’re bringing the protections offered by HSTS to Internet Explorer 11 on Windows 8.1 and Windows 7. HSTS is also available in both Internet Explorer 11 and Microsoft Edge on Windows 10.

Source: HTTP Strict Transport Security comes to Internet Explorer 11 on Windows 8.1 and Windows 7
 
All installed OK today, but as so often happens my free space took a dive and is now 0.9gb down following these.
 
All installed OK today, but as so often happens my free space took a dive and is now 0.9gb down following these.
New restore point? 545MB here on one of the 8.1 laptops.

All well with the updates, and no w10 spam this time ! :O)
 

Attachments

  • rrest.PNG
    rrest.PNG
    13.3 KB · Views: 99
7 updates.

Dism seems to be fixed but not sfc. :(
Will run them again to test.

Dism is fixed.
Sfc only showed 2 errors.

Code:
 Cannot repair member file [l:24{12}]"utc.app.json" 

Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json"

Everything else was repaired.

View attachment 62571

Good enough.

Need to try DISM because it fixed SFC problem i had with past update for Diagnostic Tracking, although i removed KB3022345 in past.

tried, all fine !
Untitled.jpg
 
Last edited:
I had to remove KB3022345 also to stop scf /scannow from being unable to fix files'

Did some research on MS site and seems their official response is it is false error that will be fixed in a future update. It basically means sfc is unreliable as long as the KB3022345 update is installed so I decided to uninstall and hide it.
 
I had to remove KB3022345 also to stop scf /scannow from being unable to fix files'

Did some research on MS site and seems their official response is it is false error that will be fixed in a future update. It basically means sfc is unreliable as long as the KB3022345 update is installed so I decided to uninstall and hide it.

:thumb: !!!!! And updates tuesday reactivated Diagnostic tracking on me, but no integrity violations. Hopefully be resolved by July 29th, :sleepy:
 
7 updates.

Dism seems to be fixed but not sfc. :(
Will run them again to test.

Dism is fixed.
Sfc only showed 2 errors.

Code:
 Cannot repair member file [l:24{12}]"utc.app.json" 

Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json"

Everything else was repaired.

View attachment 62571

Good enough.
David you're not going to be able to clean those two up. They come from KB3022345 DiagTrack update and they are false positives. See this post. It's about another subject but the same info.
 
All updates on so far 2 tablets 2 laptops installed fine, tomorrow i do the 3 desktops
 
David you're not going to be able to clean those two up. They come from KB3022345 DiagTrack update and they are false positives. See this post. It's about another subject but the same info.

Yep.
Microsoft is supposed to fix it soon.

Just posted all this because I think a new update fixed dism.
Could be wrong but it started working again after the updates. :)
 
Back
Top