Share via

windows update encountered an error code 84B30002

Anonymous
2012-09-14T02:47:48+00:00

The Help and Support and Microsoft online could not find this error code '84B30002'. I have no idea why this update to SQL Server 2008 SP2 (KB2285068) repeatedly fails. This is a large update. I have downloaded and tried the SQL Server 2008 SP3 (cumulative) and it fails with an error that there are no instances ... on this machine.

I do not understand exactly what the server software is doing on my machine except that the June 2012 IMPROVEMENTS to WIndows Update required. I have worked with Answerdesk.microsoftstore.com and gotten the WIndows Update find updates after m0ore than a month of problem solving. After 4 or 5 updates did dowdnlaod and run in the last couple of days, this one just will not run. I also have hidden 3 pthers that will not run successfully.

Vista Home Premium SP2 64 bit.

Microsoft's help site listed forums as one place to try to get an answer.

This update is listed as optional but it is always there like the ones I hid. If I set WINdwos Update to Auto download and run, the hidden updates will come out of hiding and try to run, then fail. One of them ties thr machine up and I have had to power down, then it return at the restart as a blue screeen 'do not turn off the power while this update is running. Installing 1 of 1'

How can I get rid of these updates that show up and will not install and are optional? Also is there a way to get rid of updates that are 'Important' but will not install?

I appreciate any help I can get to solve these problems. I really would like to get on with doing my work.

TigerWizard - Brenda

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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-09-14T18:14:29+00:00

    Hi,

    Try the methods provided and check.

    **Method 1:**This problem may occur if the Windows Update, Software distribution folder has been corrupted. Follow steps to rename this folder. Note that the folder will be re-created the next time the computer is started.

    1. Click the "Start" Button,
    2. In the "Start Search" box, type in " %windir%" (without the quotes) and press Enter.
    3. In the opened folder window, look for the folder named "SoftwareDistribution".
    4. Right-click on the folder, select "Rename" and type " Softold " (without the quotes) to rename this folder.

    **Method 2:**Try the steps provided here and check if it helps.

    Step 1:

    Reset the Windows Components. Refer the link.

    How do I reset Windows Update components?http://support.microsoft.com/kb/971058

    **Step 2:**If any 3rd party anti-virus or Windows Firewall is installed on your computer then disable the same and then try to install the update. Refer the links

    Disable antivirus softwarehttp://windows.microsoft.com/en-US/windows7/Disable-antivirus-software

    Turn Windows Firewall on or offhttp://windows.microsoft.com/en-US/windows7/Turn-Windows-Firewall-on-or-off

    Disclaimer: If you have to temporarily disable it to install other software, you should re-enable it as soon as you're done. If you're connected to the Internet or a network while your antivirus software is disabled, your computer is vulnerable to attacks.

    **Method 3:**Perform a clean boot and then try to install the updates. Visit link and follow the steps.

    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7http://support.microsoft.com/kb/929135

    Note: After the troubleshooting is done, follow the step 7 from the article to set the computer to start in Normal startup.

    10+ people found this answer helpful.
    0 comments
  2. Anonymous
    2017-02-26T07:04:25+00:00

    Having seen this with SQL version 2008 to 2014 on all versions of Windows including the Server OSs, the easiest way to resolve it is to download the current update for the version of SQL manually from the MS site and apply it. It seems to be the only reliable way

    9 people found this answer helpful.
    0 comments