When installing .NET Framework 3.5 on Vista what does the .NET Framework 2.0 SP1 on Vista error code 1058 mean and how do I work around it?

If you see an error like:

[05/20/08,14:05:17] Microsoft .NET Framework 2.0SP1 (CBS): ***ERRORLOG EVENT*** : Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (CBS). MSI returned error code 1058

[05/20/08,14:05:17] Setup.exe: GetGlobalCustomProperty - Property: {BBE1827C-F2FD-4FDA-A6D6-C83B62FFFDCA} - PropertyName: compfailed - Value: 0

Then that is a known issue with your machine having the IIS server turned off and it needs to be turned on.  The reason is that some of the ASP.NET updates require the Server to be running during install.

 After installing .NET Framework 3.5 (which applies the .NET Framework 2.0 SP1 and 3.0 SP1 Updates) then you can turn the IIS server service back off.


For a more detailed description of how to find this type of error see the following:

When analyzing .NET FX 1603 errors, start with the dd_dotnetfx35install.txt log file.

Search for “1603” in the log.

In your case:


[07/17/07,13:44:29] Microsoft .NET Framework 3.5 'package': ***ERRORLOG EVENT*** : Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603


Scroll up a few lines and note the name of the MSI log:


[07/17/07,13:44:09] Microsoft .NET Framework 3.5 'package': Enabling MSI log file: C:\DOCUME~1\username\LOCALS~1\Temp\dd_NET_Framework35_MSI69C8.txt


Open that log file.

Search for “return value 3”. This is what typically results in a 1603 error.


Action ended 13:44:25: InstallExecute. Return value 3.


Scroll up a few lines to see the actual error:


07/17/07 13:44:24 DDSet_Error: The Commandline '"C:\WINDOWS\Microsoft.NET\Framework\v3.5\WFServicesReg.exe" /c /v /m /i' returned non-zero value: -2147023838.


In this case, there is more:


DDSet_Warning: CScriptMapsComponent::Initialize m_spAdminBase.CoCreateInstance failed. Error code: 0x80070422

DDSet_Warning: CFxInstaller::SetupScriptMapsIIS6 Failed to initialize IIS6 APIs. Error code: 0x80070422

DDSet_Status: CScriptMapsComponent::Close

DDSet_Error: CFxInstaller::SetupComponents SetupScriptMaps failed. Error code: 0x80070422


Find out what the error code means:


# as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x422

# for decimal 1058 / hex 0x422

  ERROR_SERVICE_DISABLED                                         winerror.h

# The service cannot be started, either because it is

# disabled or because it has no enabled devices associated

# with it.

# 1 matches found for "-2147023838"


The installation needs the IIS Service running on your machine.


Comments (7)
  1. GRussell31 says:

    I thought you’d fixed my problem there, but unfortunately not.

    I get the error below when installing .Net Framework Sp1 (Pre req for Sql 2008) on my Vista machine:

    [08/14/08,11:12:33] Microsoft .NET Framework 2.0SP1 (CBS): [2] Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (CBS). MSI returned error code 1058

    [08/14/08,11:12:35] WapUI: [2] DepCheck indicates Microsoft .NET Framework 2.0SP1 (CBS) is not installed.

    Any ideas?


  2. GRussell31 says:

    Found the answer – Windows Update service needs to be enabled (and not disabled).

    Not sure as to why though!

  3. Robs2107 says:

    Thank you, using the method above I isloated the problem to the WIC (Windows Imaging Component) Installation failing. I went down the hole with this and the help of a MSKB article and it turned out to be an incoreectly registered DLL that supported the Cryptography Service.

    A long process but thanks for starting me down the right road.


  4. DWalker says:

    Huh?  "some of the ASP.NET updates require the [IIS] Server to be running during install".

    Vista Home Basic doesn’t HAVE the IIS server component, so how in the world can we get this update installed on Vista Home Basic?  I’m trying to fix this for a friend.

    I can’t turn the IIS server on because it doesn’t exist on Home Basic.

  5. Hussain Khalaf says:


    just enable "Windows Update" Service

    this shuld fix the problem


Comments are closed.

Skip to main content