Microsoft announced the next service pack for Office 2010, rolling out over the next few months.
Office 2013 users have lots of nonsecurity updates to install now, and it’s time for all Windows users to update .NET Framework.
Microsoft Office 2010 gets Service Pack 2
As noted on an Office Sustained Engineering Team blog, Microsoft has just released Service Pack 2 for Office 2010. The entire list of fixes and changes, available in a downloadable Excel spreadsheet, includes rollups of all cumulative updates through April plus public updates released through May.
Microsoft plans to roll out Office 2010 SP2 through Microsoft/Windows Update over the next 90 days. You should see the update offered, but not checked for downloading and installing. If you’re using Office 2010′s “Click to run” deployment (typically, retail versions of Office), Service Pack 2 will be streamed to you beginning in August.
Admins who use the Windows Software Updating Service (WSUS) should find the update synched with their servers, ready for approval and deployment.
In additional to Office 2010 SP2, expect service packs for Access 2010 runtime, SharePoint 2010, Groove Server, various Office filter packs, tools, language packs, etc.
Also keep in mind that even though you might be running a 64-bit version of Windows, you probably have a 32-bit version of Office 2010. So don’t be surprised if you receive the 32-bit version of SP2 (see Figure 1).
Figure 1. Most users are running a 32-bit version of Office 2010 — even on 64-bit Windows.
What to do: Service packs always have lots of components. For that reason, I recommend not installing KB 2687455 immediately after it’s offered. We need a couple of weeks to see whether there are reports of problems with the update.
MS13-057 (2803821, 2834904), MS13-052 (2840628)
Rehashing problems from July’s Patch Tuesday
In last week’s special Patch Watch Update, I discussed three patches — two for Windows Media Format and one for .NET — that are unexpectedly causing difficulties for some video-editing and customer-relations management apps.
In its support documentation for KB 2803821, Microsoft noted that Adobe’s After Effects, Photoshop, Prelude, and Premiere Pro — plus Camtasia Studio, Serif MoviePlus, and YouTube Movie Maker — are affected by the Windows Media Format flaw. The related KB 2834904 is causing problems with Adobe Prelude, Camtasia Studio, Serif Movie Plus, and YouTube Movie Maker.
KB 2840628, a .NET 4 update, isn’t playing well with applications that use SQL Server 2012, as detailed in MS Support article 2872041.
What to do: At this time, there are no fixes from Microsoft for these updates, though the company is undoubtedly working on some. For now, take a pass on KB 2803821 and KB 2834904 (MS13-57) as well as KB 2840628 (MS13-52).
.NET 3.5.1 patch impacts SharePoint 2010
MS13-052 includes numerous .NET Framework fixes, but one in particular is causing headaches for Small Business Server 2011 admins who have made changes to SharePoint 2010 Web components. As noted on the TechChucker blog, after applying the patch, SharePoint 2010 throws out errors.
What to do: There’s currently no updated version of the patch; admins should uninstall KB 2840628 or put it on hold and wait for a new version.
All other .NET updates get a green light
It looks like a relatively good month for .NET patching. I know of no issues with the following updates:
KB 2832407 for .NET 4 on Windows XP and Vista
KB 2832411 for .NET 3.0 SP2 on XP
KB 2832414 for .NET 3.5.1 on Win7 SP1
KB 2833940 for .NET 2.0 SP2 on XP
KB 2833941 for .NET 1.1 SP1 on XP and Vista
KB 2833946 for .NET 3.5.1 on Win7 SP1
KB 2833951 for .NET 1.1 SP1 on XP and Vista
KB 2833957 for .NET 4.5 on Vista SP2 and Win7 SP1
KB 2835393 for .NET 4 on XP, Vista, and Win7
KB 2836942 for .NET 3.5.1 on Win7 SP1
KB 2840629 for .NET 3.5 SP1 on XP and Vista
KB 2840631 for .NET 3.5.1 on Win7 SP1
KB 2840642 for .NET 4.5 on Vista SP2 and Win7 SP1
KB 2844285 for .NET 2.0 SP2 on XP
KB 2844286 for .NET 3.5.1 on Win7 SP1
Windows 8 users should see .NET 4.5 packages and possibly .NET 3.5 updates. Also, if you have Microsoft’s Silverlight installed, expect to see KB 2847559.
If you have any installation issues, use Aaron Stebner’s famous .NET Framework Cleanup Tool (site) to remove problematic .NET updates — then try a reinstall.
What to do: See MS13-052 for details. Install all .NET updates listed above, separately from non-.NET patches.
Tackling a long list of fixes for Office 2013
The July Patch Tuesday saw a slew of nonsecurity fixes for updates for Office 2013 — obvious teething pains for the new productivity suite. I always recommend holding off on nonsecurity fixes for a couple of weeks so we can ensure that essential security patches install correctly. Assuming you’re done with security updates, the July nonsecurity Office 2013 updates are OK to install — except for one: KB 2817468, which can cause Office crashes when users try to open encrypted messages. The update’s MS Support article states that Microsoft is investigating the problem.
KB 2767851: Fixes crashes in Office and Office Home & Student RT
What to do: Install all offered Office 2013 patches except KB 2817468.
Regular updates that are always ready to roll
Every Patch Tuesday, you should see one or more updates for the Windows Malicious Software Removal Tool and Outlook’s junk-mail filters. I’ve never seen nor heard of problems with these updates, so you’ll typically not see them listed in the problem-patch chart. The following patch numbers are static; the same number is used month after month.
KB 890830: Windows Malicious Software Removal Tool
KB 2760587: Junk email filter update for Office 2013
KB 2817523: Junk email filter update for Outlook 2003
KB 2817563: Junk email filter update for Outlook 2007
What to do: Always install these updates as soon as offered.
MS13-049 (2845690), MS13-053 (2850851)
Two Windows kernel updates ready to install
Kernel updates can have compatibility issues with third-party applications — antivirus software, for example — that work deep within Windows. Kernel update KB 2845690 was released June 11, and KB 2850851 came out July 9. To date, I’ve not seen any reports of problems with either one. Also, AV vendors have had time to update their products to make them fully compatible with these two patches (another good reason to ensure you are always completely up to date with your AV software).
What to do: Install KB 2850851 and KB 2845690.
Still on hold for Internet Explorer 10
Many of you might now be running IE 10, either because you chose to or because it was automatically installed with other updates — even if you have automatic updating turned off. But if you’ve managed to keep this browser at bay, I recommend continuing to do so for a while longer. Some websites still have lingering problems with IE 10.
If you have IE 10 installed, or are going to do so soon, check that you have updates KB 2834140 and KB 2836502 installed. Both fix problems that could show up after installing KB 2670838, a troubled patch designed to prepare systems for IE 10. (KB 2834140 corrects a Stop error, and KB 2836502 corrects a JPEG display flaw.)
What to do: If you install IE 10, check that important websites you visit (such as bank sites) are working correctly. I recommend holding off on IE 10 for a bit longer, giving websites time to become fully compatible.
Regularly updated problem-patch chart
This table provides the status of recent Windows and Microsoft application security updates. Patches listed below as safe to install will typically be removed from the table about a month after they appear. For Microsoft’s list of recently released patches, go to the MS Security TechCenter page.
See our “Windows Secrets master Patch Watch chart” post for a more extensive list of recent updates.
SSL-certification hardening; optional for admins
Internet Explorer 10 prep; must be installed before IE 10
Windows Media Format; see MS13-057 for complete list
Office 2003 SP3; also KB 2848689 for Office for Mac 2011
IE cumulative update
Windows print spooler
Windows kernel-mode driver
Windows Defender for Win7 SP1
GDI+; see MS13-054 for complete list
Windows kernel-mode driver
.NET Framework; see MS13-052 for complete list
Status recommendations: Skip — patch not needed; Hold — do not install until its problems are resolved; Wait — hold off temporarily while the patch is tested; Optional — not critical, use if wanted; Install — OK to apply.