Skip Ribbon Commands
Skip to main content

Quick Launch

Todd Klindt's home page > Todd Klindt's SharePoint Admin Blog > Posts > Don’t Install SharePoint 2013 Service Pack 1
April 03
Don’t Install SharePoint 2013 Service Pack 1

This morning Microsoft updated the KB article for SharePoint Service Pack 1 with this notice:

We have recently uncovered an issue with this Service Pack 1 package that may prevent customers who have Service Pack 1 from deploying future public or cumulative updates. As a precautionary measure, we have deactivated the download page until a new package is published.

If you haven’t installed this in your Production environment yet, please hold off. If you have it in a Test or Dev environment go ahead and keep testing it. I’ll update this blog post as I get more information.

Bill Baer (he's a big deal at Microsoft) has stated that the MSDN ISO that has SP1 included is not impacted by this issue.

To keep up on all the SharePoint 2013 patch happenings you can check out my SharePoint 2013 Builds page. You can also follow my SP2013Patches Twitter account where I tweet out SharePoint 2013 patch related information.

FAQs (added 4/7/2014)

Q1) I was going to install SharePoint 2013 in a new farm with Service Pack 1 in a week (a day, 17 minutes, etc). This seems scary, should I still do it?

A2) First, breathe, it's gonna be okay. :) If I were installing a new farm in the next couple of days I would not install it with Service Pack 1. I would either install the farm with the March 2013 Public Update, or I'd wait a few days to see what Microsoft says about how to fix existing farms with Service Pack 1.

Q2) But, but, but I already have Service Pack 1 installed in my Production farm. Woe is me! Am I screwed? Am I going to have to quit SharePoint and become a Notes administrator? My family will be so ashamed!

A2) I would, never, ever recommend anyone take drastic action like becoming a Notes administrator. That's the kind of shame that doesn't wash off. If you currently have a Production farm with Service Pack 1 on it you're fine. Microsoft will fix this. They promise, and I believe them. I know, I know, "patching the patch that makes it so you can't install another patch" is pretty funny to think about, but I'm sure they can pull it off.

Q3) What if I have Service Pack 1 in a Test farm? Can it infect my Production farm?

A3) Test farms are fine. If you're currently testing Service Pack 1 in a Test farm, keep on keepin' on. When the Service Pack 1 fix comes out drop it into your Test farm and see what happens. I would still plan on putting Service Pack 1 on your Production farm eventually.

Q4) I installed a new SharePoint 2013 farm using the MSDN ISO that had Service Pack 1 baked in. Am I in trouble, too?

A4) No, you're fine. Bill Baer told me that this issue only affects farms that were patched to Service Pack 1. Farms that were installed with the MSDN ISO are not affected. If you used an RTM ISO and slipstreamed Service Pack 1 in you are affected. But like I said in A2, you'll be fine.

tk

http://www.toddklindt.com/SP2013SP1kaput

Edit: Added piece about the MSDN ISO

Edit (4/7/2014): Added the FAQs

Comments

Question

Does this apply also to fresh installs using the iso with SP1?
 on 4/3/2014 11:19 AM

What if we had deployed it to production?

What if we had deployed it to production?
 on 4/3/2014 11:40 AM

April fools was 2 days ago dude

blame the IT Pros this time!!
 on 4/3/2014 12:53 PM

Impact on new deployment

Hope this doesn't affect new install using the 2013 with SP1 iso.
 on 4/3/2014 1:11 PM

SP1 Woes

For new deployments do you recommend installing the March, 2013 PU and stopping there?
 on 4/3/2014 1:49 PM

Re: Question

No, installs done with the MSDN ISO that has SP1 built in are not affected.

tk
Todd O. KlindtNo presence information on 4/3/2014 4:17 PM

Re: What if we had deployed it to production?

Microsoft will have a patch to fix the "You can't install a patch after SP1" bug. :) Hang tight. I'll update this blog post and the SP1 notes page once it's out.

tk
Todd O. KlindtNo presence information on 4/3/2014 4:18 PM

Re: April fools was 2 days ago dude

I did wonder if they found about this on Tuesday would they have told us then or would they have waited? :)

tk
Todd O. KlindtNo presence information on 4/3/2014 4:19 PM

Re: Impact on new deployment

Nope. Bill says it doesn't and I believe him. He's a good guy.

tk
Todd O. KlindtNo presence information on 4/3/2014 4:19 PM

Re: SP1 Woes

For now I recommend hanging tight. If you were already testing SP1 in Test keep doing that. It will be valuable. I wouldn't put anything on Production until we find out what the fix for SP1 looks like.

tk
Todd O. KlindtNo presence information on 4/3/2014 4:20 PM
1 - 10Next

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.

Title


Body *


Today's date *

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

Twitter


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

Attachments

 

 Please Support my Sponsors