MS SQL Server 2008 Service Pack 2 (KB2285068) Error Code 84C40007

Anonymous
2010-11-23T19:55:18+00:00

I've been trying to install this update via Windows Update, however, every time it begins the installation, it gives me this Error Code 84C40007. When I check the update history, it shows this update has "Failed" to install.

I haven't done anything beyond this, however, I have downloaded the same update from the MS site and am thinking of just installing it manually. However, I'd like to find out why it keeps failing to install through Windows Update and what this error code means?

I've never had problems installing Windows updates before so am not sure why this suddenly came up. I would appreciate any help.

Just to add, I did install one other update (KB2447568) at the same time through Windows Update and everything went smoothly. That update installed with no problems at all.

My specs:

Operating System: Win 7 Professional

System Type: 32 bits

Anti-virus: Microsoft Security Essentials (the most current virus and spyware definitions)

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2010-11-23T22:35:17+00:00

You need Microsoft .NET Framework 4: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9cfb2d51-5ff4-4491-b0e5-b386f32c0992&displaylang=en

I had gotten the same error so I downloaded the full install from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=8fbfc1de-d25e-4790-88b5-7dda1f1d4e17.  When I tried to install the Service Pack I recieved an error asking for .NET Framework 4.  I installed the framework and re-ran windows update, everything installed fine.  Didn't even use the full service pack install.

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

55 additional answers

Sort by: Newest
  1. Anonymous
    2010-12-21T20:00:52+00:00

    I don't know how my last comment has been marked as a proposed answer. I didn't do it (or didn't intend to). I see no way to remove that. Am I missing something obvious in these forums? Pardon the noob issue.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-12-21T17:57:43+00:00

    Thanks for the thread, to all involved. And Peter, are you saying that instead of .NET 3.5 sp1, as you said in an earlier message, that we really do need 4.0 and the "Extended" version at that, even if we are just updating the Express edition?

    Is the problem that the installer is one, for all versions of SQL Server? And we using Express are just being forced to have .NET 4.0 extended, even though we don't need it?

    If that's the case, does anyone know if perhaps MS is working on a new build of the installer that does NOT require this, for those just wanting to update Express?

    Also, FWIW, I checked and see that (per the file system), I do have C:\Windows\Microsoft.NET\Framework\v4.0.30319, so I do have .NET 4.0 installed. Can anyone offer how I'd know if I had the "Extended" version? (Sure, I could just grab the link above and install it. I'm asking because a) some readers in my boat may not want to and b) we may not need to if MS comes out with an installer that does not require that for updates only to SQL Server Express.)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-12-20T20:10:19+00:00

    I had the same problem installing SQL Server 2008 SP2 with .NET Framework 4 Client Profile previously installed. It seems that SQL Server 2008 SP2 requires .NET Framework 4 "Extended", which is installed by the .NET Framework 4 "full" setup package referenced above.

    After installing the .NET Framework 4 "full" setup package, the SQL Server 2008 SP2 installed successfully for me.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2010-12-15T08:51:17+00:00

    Thank you

    This worked for me as well

    Was this answer helpful?

    0 comments No comments