locked
WSUS 3.0 SP2 failed RRS feed

  • Question

  • Logged in as domain admin to member Server 2003 R2 Std. SP2 (DC: Server 2008 R2 SP1)

    Downloaded WSUS install package WSUS30-KB972455-x86.exe from Microsoft download site.

    Ran the install using all default selections...Next..Next.... etc....

    Install failed to complete. Got this error:

    There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.

    Here is the error log:

    2012-02-17 11:44:32  Success   MWUSSetup          Validating pre-requisites...
    2012-02-17 11:44:33  Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
    2012-02-17 11:44:33  Error     MWUSSetup          WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
    2012-02-17 11:44:39  Success   MWUSSetup          ReportViewer is not installed on this machine
    2012-02-17 11:44:39  Success   MWUSSetup          ReportViewer is not installed on this machine
    2012-02-17 11:45:43  Success   MWUSSetup          Initializing installation details
    2012-02-17 11:45:43  Success   MWUSSetup          Installing ASP.Net
    2012-02-17 11:46:07  Success   MWUSSetup          ASP.Net is installed successfully
    2012-02-17 11:46:07  Success   MWUSSetup          Installing wYukon using MSI on Win2k3
    2012-02-17 11:46:07  Success   MWUSSetup          Installing wYukon...
    2012-02-17 11:48:34  Success   MWUSSetup          wYukon Installed Successfully
    2012-02-17 11:48:37  Success   MWUSSetup          Installing WSUS...
    2012-02-17 11:48:46  Success   CustomActions.Dll  Unable to get INSTALL_LANGUAGE property, calculating it...
    2012-02-17 11:48:47  Success   CustomActions.Dll  Successfully set propery of WSUS admin groups' full names
    2012-02-17 11:48:47  Success   CustomActions.Dll  .Net framework path: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
    2012-02-17 11:48:50  Success   CustomActions.Dll  Creating user group: WSUS Reporters with Description: WSUS Administrators who can only run reports on the Windows Server Update Services server.
    2012-02-17 11:48:50  Success   CustomActions.Dll  Creating WSUS Reporters user group
    2012-02-17 11:48:50  Success   CustomActions.Dll  Successfully created WSUS Reporters user group
    2012-02-17 11:48:50  Success   CustomActions.Dll  Creating user group: WSUS Administrators with Description: WSUS Administrators can administer the Windows Server Update Services server.
    2012-02-17 11:48:50  Success   CustomActions.Dll  Creating WSUS Administrators user group
    2012-02-17 11:48:50  Success   CustomActions.Dll  Successfully created WSUS Administrators user group
    2012-02-17 11:48:50  Success   CustomActions.Dll  Successfully created WSUS user groups
    2012-02-17 11:48:50  Success   CustomActions.Dll  Succesfully set binary SID property
    2012-02-17 11:48:50  Success   CustomActions.Dll  Succesfully set binary SID property
    2012-02-17 11:48:50  Success   CustomActions.Dll  Successfully set binary SID properties
    2012-02-17 11:55:19  Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)
    2012-02-17 11:55:19  Error     MWUSSetup          CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)
    2012-02-17 11:55:19  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)

    Any help to resolve would be appreciated.

    Cheers,

    Ian.

    Friday, February 17, 2012 8:07 PM

Answers

  • In addition to the logpath point, there are also notable considerations that could contribute to the behavior in a similar environment:
    2012-05-09 14:08:47  Success   CustomActions.Dll  .Net framework path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319

    This can be part of the problem.

    WSUS is designed for installation on a .NET Framework v2.0 environment.

    It will install, and is supported, on a .NET Framework v3.5 SP1 environment.

    It is NOT supported on a .NET Framework v4.0 environment, and without some behind-the-scenes manual configuration of the .NET4 environment, installing WSUS on .NET4 will have issues.

    2012-05-09 14:08:48  Success   CustomActions.Dll  WSUS Reporters user group already exists
    2012-05-09 14:08:48  Success   CustomActions.Dll  WSUS Administrators user group already exists

    Second, this was NOT a VIRGIN installation of the operating system and WSUS. WSUS was previously installed on this system, as evidenced by these two log entries.

    And thus two possible causes for your installation failure

    1. WSUS was previously installed and not properly uninstalled
    2. The .NET Framework v4 is installed.

    Property(S): COMPLETE_SQLINSTANCE = SCCM-1\SCCM

    Property(S): NetFxPath = C:\Windows\Microsoft.NET\Framework64\v4.0.30319

    Is there any significance to the fact that the machine is named SCCM-1 or that the database instance is named SCCM?

    Have you confirmed with the WSUS Deployment Guide that the database instance SCCM is WSUS-compatible. For example, quite often SCCM databases are installed with Mixed Mode Authentication. WSUS does not install into Mixed Mode Authentication; it must be configured for Windows Authentication.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin


    Thursday, May 10, 2012 9:59 PM

All replies

  • Hi,

    Did you have any old website running on your IIS? Try to check whether the old/empty website exists.

    If not,then WSUS install was performed trying to use a domain admin account via Builtin\Administrators.Did you use the SQL server instead of WID? Builtin\Administrators were NOT sa priviledged.Added sa priviledge back to the group.NOTE: Also made sure that nt authority\network service account was there and had SA priviliges.

    Also check .net framework,iis, whether satisfy WSUS 3.0 Installation Requirements: http://technet.microsoft.com/en-us/library/cc708484(v=ws.10).aspx

    Regards,
    Clarence
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contacttnmff@microsoft.com.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Monday, February 20, 2012 8:43 AM
  • Hi Clarence,

    I checked IIS and found only the "default web site". No old/empty website exists.  I used the default WID.

    Not sure what you mean by "SA privileged"? 

    WSUS 3.0 req'ments met: IIS6.0, .Net 2.0, MMC3.0, installed report viewer 2005, etc.

    Ian.

    Monday, February 20, 2012 10:24 PM
  • The possible cause for this issue is that SUSDB and SUSDB_log already existed.

    So please perform the following actions:
    1. Uninstall Windows Internal Database.
    2. Delete SUSDB and SUSDB_Log files.
    3. Attempte WSUS installation again.

    If the above steps can't resolve the issue, please check if any error events in Event Viewer(especially System and Application events)


    Thanks
    Zero
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, February 21, 2012 10:12 AM
  • Performed Steps 1 2 3 above.

    Step 1: WID removed sucessfully.

    Note: Step 2 - Search for SUSDB* files: none found.

    Step 3: WSUS install failed again. Same original issue logged.

    Check System events: 1 error, event 7023, WMI Performance Adapter terminated with the following error: Unspecified error.

    Check Application events: multiple errors found, events 2002 W2Ctrs, 1001 IISInfoCtrs, 11722 MsiInstaller, 3002 LoadPerf, 1008 Perflib, 8317 MSSQL$Microsft..., 3011 LoadPerf, 3012 LoadPerf, 1 SQLBrowser, 1053 Userenv

    Where to start?

     
    Wednesday, February 22, 2012 8:38 PM
  • 1. SUSDB means the WSUS database, usually the files are in C:\WSUS\SUSDB\UpdateServicesDbFiles.
    So please check if any files in that folder.

    2. Check if you have Cisco Monitor Service (csmon.exe), if yes, please stop it and try again.

    3. Please check if you can find errors like "failed to create Group" in the event viewer.

    4. Try the following:
    a. delete C:\Windows\SysMsi\SSEE folder
    Check the permissions of C:\Windows folder:
    -- Users : Read and Execute (this folder and subfolders)
    -- Creator owner : Full Control (this folder and subfolders)
    b. Repair(or reinstall) .NET Framework.
    c. Reboot the server and try again.


    Thanks
    Zero
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, February 23, 2012 12:37 PM
  • Just checking if you have tried the steps and if any update.

    Thanks
    Zero
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Saturday, February 25, 2012 6:26 AM
  • 1. SUSDB means the WSUS database, usually the files are in C:\WSUS\SUSDB\UpdateServicesDbFiles.

    The correct folder is \WSUS\UpdateServicesDBFiles -- there is no 'SUSDB' folder in that tree.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Saturday, February 25, 2012 6:14 PM
  • If not,then WSUS install was performed trying to use a domain admin account via Builtin\Administrators.Did you use the SQL server instead of WID? Builtin\Administrators were NOT sa priviledged.Added sa priviledge back to the group.NOTE: Also made sure that nt authority\network service account was there and had SA priviliges.

    This is an entirely irrelevant discussion. WSUS uses Windows Authentication with SQL Server; the 'sa' account is irrelevant. Furthermore, Domain Administrators *DO* have full permissions to install any version, edition, or instance of SQL Server on any system -- in fact, in most instances, the Domain Admin account MUST be used! As for what database he used -- that question was already answered -- he took ALL of the defaults in the installer -- which would include the installation of the Windows Internal Database -- and the LOGFILE shows that as fact!

    2012-02-17 11:46:07  Success   MWUSSetup          Installing wYukon using MSI on Win2k3
    2012-02-17 11:46:07  Success   MWUSSetup          Installing wYukon...
    2012-02-17 11:48:34  Success   MWUSSetup          wYukon Installed Successfully


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Saturday, February 25, 2012 6:19 PM
  • The possible cause for this issue is that SUSDB and SUSDB_log already existed.

    Not possible at all. The installation logfile demonstrates unequivocally that this was a VIRGIN instalation of WSUS. Furthermore, WSUS is a perfectly happy camper to re-link to an existing SUSDB database, but if that were the case -- we would have seen log entries showing that the WID was already installed, that that the security groups (WSUSAdministrators and WSUS Reporters) already existed, or that the Report Viewer was already installed.

    The *correct* response to this inquiry is to ask for the OTHER installation logfile to be posted, so that we can determine exactly what failed in the installation -- rather than GUESSING (and incorrectly, at that)!


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Saturday, February 25, 2012 6:23 PM
  • Any help to resolve would be appreciated.

    Please post the TAIL of the other installation logfile -- WSUSSetupmsi_120217_114x.log -- which should be located in the TEMP folder of the userprofile of the actual account you used to install WSUS. It may be fairly large (on my successful installation it is over 2MB). Specifically we're interested in the entries related to the failed installation.

    Also in that folder there should be a WSUSCa_120217_114x.log, which will contain the details related to the attempt to create the SUSDB database. Please post that complete log in a separate message -- it will be <100KB


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin


    Saturday, February 25, 2012 6:30 PM
  • Hello Everyone,

    I have been working on installing WSUS 3.0 SP2 on Windows Server 2003, 2008 and 2008 R2 with errors and the same log details as above. After looking around the internet, I thought of giving up and then found a forum on Installing Windows Home Server 2011 with WSUS (Just to find a answer) and I did, if don't install MS Report Viewer 08 WSUS setup fails but if MS Report Viewer 08 is installed WSUS installs perfectly no errors on Windows Server 2008 Standard.

    Matt

    Saturday, April 14, 2012 3:56 AM
  • Hello Everyone,

    I have been working on installing WSUS 3.0 SP2 on Windows Server 2003, 2008 and 2008 R2 with errors and the same log details as above. After looking around the internet, I thought of giving up and then found a forum on Installing Windows Home Server 2011 with WSUS (Just to find a answer) and I did, if don't install MS Report Viewer 08 WSUS setup fails but if MS Report Viewer 08 is installed WSUS installs perfectly no errors on Windows Server 2008 Standard.

    Matt

    Report Viewer is not required to install WSUS. Report Viewer is only required if you wish to use the reports provided by the WSUS application.

    Now I cannot speak to what happens on WHS, because WHS is not a supported installation platform for WSUS, and has not been tested. It's quite possible that RV is installing something on WHS that is NOT present by default, that is already present on a standard Windows Server installation.

    It's also possible that the environments you were working with had something 'fixed' by installing RV2008, but I have successfully installed several WSUS servers on Win2008R2, Win2008SP2, and Win2003SP2, without Report Viewer, and experienced no installation issues whatsoever.

    If anybody can reproduce the behavior on a virgin installation of Windows Server from media or Microsoft-published ISO, I'm certainly interested in seeing those installation logfiles.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Saturday, April 14, 2012 6:16 PM
  • Can do.  I have a VM running Windows Server 2008 R2 SP1 with SQL Server 2008 R2 Standard (10.50.1617).  This thread matched perfectly to the issue I am having.

    Here is the WSUSSetup file:

    2012-05-09 14:08:02  Success   MWUSSetup          Detected that setup was launched through Server Manager
    2012-05-09 14:08:03  Success   MWUSSetup          Validating pre-requisites...
    2012-05-09 14:08:03  Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
    2012-05-09 14:08:03  Error     MWUSSetup          WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
    2012-05-09 14:08:47  Success   MWUSSetup          Initializing installation details
    2012-05-09 14:08:47  Success   MWUSSetup          Skipping Asp.Net install since not running on win2k3...
    2012-05-09 14:08:47  Success   MWUSSetup          Installing WSUS...
    2012-05-09 14:08:47  Success   CustomActions.Dll  Unable to get INSTALL_LANGUAGE property, calculating it...
    2012-05-09 14:08:47  Success   CustomActions.Dll  Successfully set propery of WSUS admin groups' full names
    2012-05-09 14:08:47  Success   CustomActions.Dll  .Net framework path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319
    2012-05-09 14:08:48  Success   CustomActions.Dll  Creating user group: WSUS Reporters with Description: WSUS Administrators who can only run reports on the Windows Server Update Services server.
    2012-05-09 14:08:48  Success   CustomActions.Dll  Creating WSUS Reporters user group
    2012-05-09 14:08:48  Success   CustomActions.Dll  WSUS Reporters user group already exists
    2012-05-09 14:08:48  Success   CustomActions.Dll  Successfully created WSUS Reporters user group
    2012-05-09 14:08:48  Success   CustomActions.Dll  Creating user group: WSUS Administrators with Description: WSUS Administrators can administer the Windows Server Update Services server.
    2012-05-09 14:08:48  Success   CustomActions.Dll  Creating WSUS Administrators user group
    2012-05-09 14:08:48  Success   CustomActions.Dll  WSUS Administrators user group already exists
    2012-05-09 14:08:48  Success   CustomActions.Dll  Successfully created WSUS Administrators user group
    2012-05-09 14:08:48  Success   CustomActions.Dll  Successfully created WSUS user groups
    2012-05-09 14:08:48  Success   CustomActions.Dll  Succesfully set binary SID property
    2012-05-09 14:08:48  Success   CustomActions.Dll  Succesfully set binary SID property
    2012-05-09 14:08:48  Success   CustomActions.Dll  Successfully set binary SID properties
    2012-05-09 14:09:15  Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)
    2012-05-09 14:09:15  Error     MWUSSetup          CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)
    2012-05-09 14:09:15  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2012-05-09 14:13:57  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)

    And here is the tail of the WSUSSetupmsi_120509_1408 file:

    Property(S): LANGUAGE_ID = 1033
    Property(S): COMPLETE_SQLINSTANCE = SCCM-1\SCCM
    Property(S): LARGEST_NTFS_DRIVE = F:\
    Property(S): ROOTDRIVE = f:\
    Property(S): CostingComplete = 1
    Property(S): OutOfDiskSpace = 0
    Property(S): OutOfNoRbDiskSpace = 0
    Property(S): PrimaryVolumeSpaceAvailable = 0
    Property(S): PrimaryVolumeSpaceRequired = 0
    Property(S): PrimaryVolumeSpaceRemaining = 0
    Property(S): NetFxPath = C:\Windows\Microsoft.NET\Framework64\v4.0.30319
    Property(S): SOURCEDIR = f:\a2526f7f1294a4375a364a\SUS\
    Property(S): SourcedirProduct = {77846B52-14C9-4FC4-BE63-FE06AF501442}
    Property(S): WS_ACCOUNT_SID = 010100000000000514000000
    Property(S): WUS_ADMINISTRATORS_SID = 010500000000000515000000C08F72E820AE661C4C255C74ED030000
    Property(S): ProductToBeRegistered = 1
    MSI (s) (7C:D4) [14:09:15:161]: Note: 1: 1708
    MSI (s) (7C:D4) [14:09:15:161]: Product: Windows Server Update Services 3.0 SP2 -- Installation failed.

    MSI (s) (7C:D4) [14:09:15:163]: Windows Installer installed the product. Product Name: Windows Server Update Services 3.0 SP2. Product Version: 3.2.7600.226. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

    MSI (s) (7C:D4) [14:09:15:166]: Deferring clean up of packages/files, if any exist
    MSI (s) (7C:D4) [14:09:15:166]: MainEngineThread is returning 1603
    MSI (s) (7C:78) [14:09:15:168]: RESTART MANAGER: Session closed.
    MSI (s) (7C:78) [14:09:15:168]: No System Restore sequence number for this installation.
    === Logging stopped: 5/9/2012  14:09:15 ===
    MSI (s) (7C:78) [14:09:15:169]: User policy value 'DisableRollback' is 0
    MSI (s) (7C:78) [14:09:15:169]: Machine policy value 'DisableRollback' is 0
    MSI (s) (7C:78) [14:09:15:169]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (7C:78) [14:09:15:169]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (7C:78) [14:09:15:169]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (7C:78) [14:09:15:170]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (7C:78) [14:09:15:170]: Restoring environment variables
    MSI (s) (7C:78) [14:09:15:172]: Destroying RemoteAPI object.
    MSI (s) (7C:18) [14:09:15:172]: Custom Action Manager thread ending.
    MSI (c) (78:60) [14:09:15:175]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (78:60) [14:09:15:176]: MainEngineThread is returning 1603
    === Verbose logging stopped: 5/9/2012  14:09:15 ===

     I really don't know if I got enough of the end of this file but I would be happy to tranfer the whole thing (2.5 MB) if you have a way to receive it.

    Thanks,

    Doug.

    Wednesday, May 9, 2012 6:24 PM
  • BTW: This install came from an ISO off the VLSC site.  SP1 was included in the original ISO - I did not try to slipstream it.
    Wednesday, May 9, 2012 6:27 PM
  • Ok - the answer for me was pretty simple.  I was installing into an existing SQL Server instance and during the SQL Server install, I changed the log path to a different volume.  I restarted the SQL server instance as directed but I did not verify that SQL Server auto creates the missing path if necessary.  It did not and therefore when the WSUS installer tried to create the SQL log file using the path given, it could not because the path did not exist.  Hence, a failed install...

    I changed the log file path back to its default and reran the WSUS installer without incident.

    I suspect there is something similar happening in both instances above.

    Doug.

    • Proposed as answer by dougz1 Wednesday, May 9, 2012 7:08 PM
    Wednesday, May 9, 2012 7:08 PM
  • In addition to the logpath point, there are also notable considerations that could contribute to the behavior in a similar environment:
    2012-05-09 14:08:47  Success   CustomActions.Dll  .Net framework path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319

    This can be part of the problem.

    WSUS is designed for installation on a .NET Framework v2.0 environment.

    It will install, and is supported, on a .NET Framework v3.5 SP1 environment.

    It is NOT supported on a .NET Framework v4.0 environment, and without some behind-the-scenes manual configuration of the .NET4 environment, installing WSUS on .NET4 will have issues.

    2012-05-09 14:08:48  Success   CustomActions.Dll  WSUS Reporters user group already exists
    2012-05-09 14:08:48  Success   CustomActions.Dll  WSUS Administrators user group already exists

    Second, this was NOT a VIRGIN installation of the operating system and WSUS. WSUS was previously installed on this system, as evidenced by these two log entries.

    And thus two possible causes for your installation failure

    1. WSUS was previously installed and not properly uninstalled
    2. The .NET Framework v4 is installed.

    Property(S): COMPLETE_SQLINSTANCE = SCCM-1\SCCM

    Property(S): NetFxPath = C:\Windows\Microsoft.NET\Framework64\v4.0.30319

    Is there any significance to the fact that the machine is named SCCM-1 or that the database instance is named SCCM?

    Have you confirmed with the WSUS Deployment Guide that the database instance SCCM is WSUS-compatible. For example, quite often SCCM databases are installed with Mixed Mode Authentication. WSUS does not install into Mixed Mode Authentication; it must be configured for Windows Authentication.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin


    Thursday, May 10, 2012 9:59 PM
  • Even I had a similar issue while installing WSUS SP2 on windows 2008 OS. Spent more a weeks time in identifying the root cause.

         InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)

        CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)

     CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)

    This issue got resolved after uninstalling the dot net 4.0 and higher version.

    Friday, August 26, 2016 7:13 PM
  • Thanks, my issue turned out to be the .net framework version, changed from version 4 to version 3.5 and its working now!
    Wednesday, January 25, 2017 2:05 PM
  • I also had a .NET framework issue - installing on Windows Home Server 2011. When I looked in Server Manager under Features Summary, I saw the reference to .NET Framework 3.5.1 and assumed this was the latest install. Upon opening Programs and Features I saw .NET Framework 4.7.1. This was also referred to in my WSUS log file, so I uninstalled this .NET version and tried again. It worked!

    I had previously tried an abundance of tricks including LODCTR /R but this was the fault all along.

    Friday, May 4, 2018 11:35 AM
  • Thanks, it's worked for me.
    Sunday, January 5, 2020 10:37 PM