Windows Server TechCenter > Windows Server Forums > WSUS > Force Unistall WSUS 3.0 SP1
Ask a questionAsk a question
 

AnswerForce Unistall WSUS 3.0 SP1

  • Wednesday, April 16, 2008 2:34 PMCarlos A Morales Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi, i have error to unistall WSUS. The log file have the following information:
    A idea for unistall?
     
    2008-04-15 10:49:01  Success   MWUSSetup          Validating pre-requisites...
    2008-04-15 10:49:05  Success   MWUSSetup          Removing Wsus...
    2008-04-15 10:49:06  Success   CustomActions.Dll  The system language ESM is not supported. Using English resources...
    2008-04-15 10:49:06  Success   CustomActions.Dll  Successfully set propery of WSUS admin groups' full names
    2008-04-15 10:49:06  Error     CustomActions.Dll  SetWyukonInstallDirProperty: Failed to open WYUKON registry key: SOFTWARE\Microsoft\Microsoft SQL Server\MICROSOFT##SSEE\Setup (Error 0x80070002: The system cannot find the file specified.)
    2008-04-15 10:49:06  Error     CustomActions.Dll  SetUnInstallProperties: Failed to set WYUKON install directory (Error 0x80070002: The system cannot find the file specified.)
    2008-04-15 10:49:06  Error     MWUSSetup          RemoveWsus: MWUS Uninstall Failed (Error 0x80070643: Fatal error during installation.)
    2008-04-15 10:49:06  Error     MWUSSetup          Wsus MSI uninstallation failed. (Error 0x80070643: Fatal error during installation.)
    2008-04-15 10:49:06  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2008-04-15 10:49:07  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)
    2008-04-15 10:49:25  Success   MWUSSetup          Validating pre-requisites...
    2008-04-15 10:49:42  Success   MWUSSetup          Removing Wsus...
    2008-04-15 10:49:42  Success   CustomActions.Dll  The system language ESM is not supported. Using English resources...
    2008-04-15 10:49:42  Success   CustomActions.Dll  Successfully set propery of WSUS admin groups' full names
    2008-04-15 10:49:43  Error     CustomActions.Dll  SetWyukonInstallDirProperty: Failed to open WYUKON registry key: SOFTWARE\Microsoft\Microsoft SQL Server\MICROSOFT##SSEE\Setup (Error 0x80070002: The system cannot find the file specified.)
    2008-04-15 10:49:43  Error     CustomActions.Dll  SetUnInstallProperties: Failed to set WYUKON install directory (Error 0x80070002: The system cannot find the file specified.)
    2008-04-15 10:49:43  Error     MWUSSetup          RemoveWsus: MWUS Uninstall Failed (Error 0x80070643: Fatal error during installation.)
    2008-04-15 10:49:43  Error     MWUSSetup          Wsus MSI uninstallation failed. (Error 0x80070643: Fatal error during installation.)
    2008-04-15 10:49:43  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2008-04-15 10:49:44  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)
    2008-04-15 10:53:11  Error     MWUSSetup          ParseCommandLine: Failed to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key (Error 0x80070002: The system cannot find the file specified.)

Answers

  • Thursday, April 17, 2008 9:51 AMEric Zhang - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi Carlos,

    Please try the following steps to remove WSUS 3.0:

    1. Download the SDK to obtain MSIZAP

       http://download.microsoft.com/download/e/9/d/e9d80355-7ab4-45b8-80e8-983a48d5e1bd/msicuu2.exe

    2. From a command prompt, type:
    MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}

    3. From a command prompt, type: sc delete wsusservice

    4. Again, From a command prompt, type:

        MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}

    5. From a command prompt, type: iisreset

    The MSIZAP switch "T" removes all info for given product code

    P.S.
    For WSUS 3.0: MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}


    For Microsoft SQL Server 2005 Embedded Edition

    1) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
         Edit the "InstalledInstances" value and remove "MICROSOFT##SSEE"

    2) Remove the "MICROSOFT##SSEE" subkey under
         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

    3) Remove the "MSSQL.2005" subkey under
         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

    4) Rename the following folder:
          \%Windir%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data  to   \%Windir%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data.old

      (If \MSSQL\Data lock , you can removing the "Windows Internal Database" from Add/remove programs)

    --------------------
    Regards,
    Eric Zhang




All Replies

  • Thursday, April 17, 2008 9:51 AMEric Zhang - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hi Carlos,

    Please try the following steps to remove WSUS 3.0:

    1. Download the SDK to obtain MSIZAP

       http://download.microsoft.com/download/e/9/d/e9d80355-7ab4-45b8-80e8-983a48d5e1bd/msicuu2.exe

    2. From a command prompt, type:
    MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}

    3. From a command prompt, type: sc delete wsusservice

    4. Again, From a command prompt, type:

        MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}

    5. From a command prompt, type: iisreset

    The MSIZAP switch "T" removes all info for given product code

    P.S.
    For WSUS 3.0: MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}


    For Microsoft SQL Server 2005 Embedded Edition

    1) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
         Edit the "InstalledInstances" value and remove "MICROSOFT##SSEE"

    2) Remove the "MICROSOFT##SSEE" subkey under
         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

    3) Remove the "MSSQL.2005" subkey under
         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

    4) Rename the following folder:
          \%Windir%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data  to   \%Windir%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data.old

      (If \MSSQL\Data lock , you can removing the "Windows Internal Database" from Add/remove programs)

    --------------------
    Regards,
    Eric Zhang




  • Thursday, April 17, 2008 2:54 PMTimothy Berry Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Eric,

     

    I am having the same problems. When I try to uninstall 3.0 I get the "unable to find registry key" error.

     

    I am running Windows Server 2003, would the above instruction work for me also?

     

    Tim Berry

  • Friday, April 18, 2008 1:43 AMEric Zhang - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Tim,

    The above steps are also available for your situation.

    --------------------
    Regards,
    Eric Zhang



  • Wednesday, April 23, 2008 7:45 AMEric Zhang - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Carlos,

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios.

    If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks!
    --------------------
    Regards,
    Eric Zhang

  • Friday, May 23, 2008 4:12 PMTravisJ Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hello,

     

    This fixed a portion of my issue.  After following the above steps I was able to upgrade to WSUS 3.0SP1, however, I am not able to get a syncronization after the new installation.


    I am having the same issue on 2 servers that I manage for 2 different companies that update from Microsoft.

     

    Any tips on where to look for a cause or is this a known issue?

     

    Thanks in advance

    Travis