Skip Ribbon Commands
Skip to main content

Quick Launch

Todd Klindt's home page > Todd Klindt's Office 365 Admin Blog > Posts > Changes to SharePoint 2013 Cumulative Updates
January 01
Changes to SharePoint 2013 Cumulative Updates

For the last few years I’ve tried to keep up with the patches released for SharePoint 2010 and SharePoint 2013. Some days it feels like a full time job. This December had one of those days.

Patching got substantially easier when SharePoint 2010 came out. Patching SharePoint 2007 had some pitfalls, and patching SharePoint 2003 was downright confusing. It was not for people with weak hearts. For the most part, all the problems went away in SharePoint 2010. The biggest improvement was the introduction of the single file upgrades. What that meant was regardless of which SharePoint product you were using; Foundation, Server, or Project Server, you installed one patch and that was it. In SharePoint 2007 if you had MOSS you had to install the WSS patch and then the MOSS patch, and there were no errors if you didn’t. The first indication you got that something was wrong was MOSS being broken after the patch was installed. That was just not soon enough for most folks. Some people are really impatient.

Like I said, SharePoint 2010 fixed all that. Regardless of your version of SharePoint 2010, you downloaded one file and you were done. That spectacularness carried over to SharePoint 2013. For both versions you could go to either my SharePoint 2010 Builds page or the SharePoint 2013 Builds page and grab the file you needed. Life was good.

Then came “The Big Patch Rejiggering of December 2013.” Starting in December 2013, the patches for SharePoint 2013 are no longer a single file for each product. There have been two important changes:

1) SharePoint Server patch is now two files and you need them both. Microsoft published a KB article explaining the change. When you go to the download page you see this:


You need to download both files and extract them in the same directory to successfully install the CU. The reason given for this is because the size of the patch has gotten too large for one file. The first file is 441 MB and the second file is 1.717 GB. Together they exceed that magical number of 2 GB, which I’m guessing is the boundary. The October 2013 CU was 2144916952 bytes which comes out to 1.997 GB after you divide by 1024 a couple of times. Currently the largest SharePoint 2010 CU (December 2013 CU for Project Server) clocks in at a modest 1.2 GBs, so it’ll be a while until we have a problem there.

2) Project Server has been demoted from Cumulative Update to Hotfix. With SharePoint 2010, and SharePoint 2013 August 2013 and earlier, there was a separate CU for Project Server, and it contained the Foundation and Server components along with the Project components. October 2013 did not have a Project Server CU. The SharePoint Server CU was 1.997 GBs, so I’m guessing they couldn’t make a Project Server CU under 2 GB. Starting in December 2013 Project Server is a Hotfix that must installed in addition to the SharePoint Server CU. The December 2013 Project Server 2013 Hotfix requires the Project Server component be at at least the March 2013 PU level. After your farm is at that level you can install the December 2013 Project Server hotfix with or without the December 2013 SharePoint Server CU, though I’d recommend you keep them in sync. It doesn’t seem to matter which one you install first.

I hope that clears up the changes in the SharePoint 2013 patches. If you have any questions, leave a comment below.





This is a very unwelcome change! :-(
 on 1/1/2014 2:16 PM

AutoSPSourceBuilder Updated

AutoSPSourceBuilder was updated today to account for the separate files in the Dec 2013 CU.

 on 1/2/2014 3:47 PM


Thanks you Todd for the CU update changes.  If it wasn't for your simplified blog, I would have to read the boring MS KB! -Roger
 on 1/8/2014 3:35 PM

Free NSE Tips Intraday Trading Stock Market Tips

Share Market Investment made profitable by SHRISTOCKTIPS- Get NSE/BSE Tips via SMS and Yahoo Messenger. We give daily stock market tips for future and cash segments. As said last time we made a sell position in NIFTY around 6350-6400 we booked the profit at 6100 level. Our all paid & trial clients made a very handsome profit. Now for the coming week we<a href="" title="Stock market">SHARE, STOCK TIPS</a>suggest all the traders to make a buy position in NIFTY around 5950-6050 for the target of 6300-6400 with stoploss of 5800. Traders can also make a buy position in all NIFTY 50 stocks according to the level of NIFTY. Please trade with strict stoploss because there may be a high volatility in the market. For Further update keep following our website & you can also avail our two days trial to check our accuracy.
 on 2/12/2014 1:06 AM

Thanks for the info

I didn't know about it. Thanks for the information. I have just signed up for a  free SharePoint site with Is this applicable for a Foundation version as well?
 on 5/1/2014 11:27 PM


Intradaylivetips is a investing tips Organization which often renders safe strategies for your present significant opportunity from the note down regarding equity Market, having a influential hold within given that the majority of perfect advice in stock research along with NSE Currency investigation. Our breakdown Partners goal totally on the market where we can provide proper, multi-process along with where we can leverage the firm’s central competencies that can help clients assemble customer along with his money.

 on 8/14/2014 9:32 AM

Share Tips

Thank for your info, We are also provide share tips as well as commodity tips that make you remain abreast of the stock and commodity market without any sort of problem at all. With other important features like NSE tips, BSE tips, MCX tips, NCDEX tips, it helps in making the perfect decision at the best time
 on 9/1/2014 10:48 AM

Nifty Options Tips

Very Good Site and awesome writing too , and great thanks to the writer

<a href="" >Nifty Options Tips</a>
 on 10/21/2014 5:57 AM

Add Comment

Items on this list require content approval. Your submission will not appear in public views until approved by someone with proper rights. More information on content approval.


Body *

Today's date *

Select a date from the calendar.
Please enter today's date so I know you are a real person


Want a message when I reply to your comment? Put your Twitter handle here.