Share via

'Microsoft.VisualStudio.IISExpress.Msi,version=15.8.27729.1,chip=x64' failed to install

  • Article

Question

Tuesday, January 15, 2019 10:06 PM

When i am trying to Install Missing Features, the package fails. Here is the log:

Something went wrong with the install.

You can troubleshoot the package failures by:

    1. Search for solutions using the search URL below for each package failure
    2. Modify your selections for the affected workloads or components and then retry the installation
    3. Remove the product from your machine and then install again

If the issue has already been reported on the Developer Community, you can find solutions or workarounds there. If the issue has not been reported, we encourage you to create a new issue so that other developers will be able to find solutions or workarounds. You can create a new issue from within the Visual Studio Installer in the upper-right hand corner using the "Provide feedback" button.

================================================================================

Package 'Microsoft.VisualStudio.IISExpress.Msi,version=15.8.27729.1,chip=x64' failed to install.
    Search URL
        https://aka.ms/VSSetupErrorReports?q=PackageId=Microsoft.VisualStudio.IISExpress.Msi;PackageAction=Install;ReturnCode=1601
    Details
        MSI: C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualStudio.IISExpress.Msi,version=15.8.27729.1,chip=x64\iisexpress_amd64_en-US.msi, Properties:  REBOOT=ReallySuppress  INSTALLEDBY="VisualStudio"  VSVERSION="15.0.27729.01" 
        Return code: 1601
        Return code details: The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
    Log
        C:\Users\v720166\AppData\Local\Temp\2\dd_setup_20190115155643_025_Microsoft.VisualStudio.IISExpress.Msi.log
    Impacted workloads
        .NET desktop development (Microsoft.VisualStudio.Workload.ManagedDesktop,version=15.8.27906.1)
        ASP.NET and web development (Microsoft.VisualStudio.Workload.NetWeb,version=15.8.27906.1)
        Data storage and processing (Microsoft.VisualStudio.Workload.Data,version=15.6.27309.0)
    Impacted components
        ASP.NET and web development tools (Microsoft.VisualStudio.Component.Web,version=15.8.27825.0)
        ASP.NET and web development tools prerequisites (Microsoft.VisualStudio.ComponentGroup.Web,version=15.9.28219.51)
        Azure Cloud Services core tools (Microsoft.VisualStudio.Component.Azure.Waverton,version=15.9.28107.0)
        Azure Data Lake and Stream Analytics Tools (Microsoft.Component.Azure.DataLake.Tools,version=15.9.28107.0)
        Cloud tools for web development (Microsoft.VisualStudio.ComponentGroup.Web.CloudTools,version=15.8.27729.1)
        IIS Express  (Microsoft.VisualStudio.Component.IISExpress,version=15.0.26208.0)
        Microsoft Azure WebJobs Tools (Component.Microsoft.VisualStudio.Web.AzureFunctions,version=15.7.27617.1)
        Microsoft Azure WebJobs Tools (Microsoft.VisualStudio.ComponentGroup.AzureFunctions,version=15.7.27617.1)
        Windows Communication Foundation (Microsoft.VisualStudio.Component.Wcf.Tooling,version=15.8.27924.0)

All replies (4)

Wednesday, January 16, 2019 8:52 AM

Hi Dev1089,

Welcome to the MSDN forum.

I checked your error message.

  • “Return code: 1601
     Return code details: The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed.”

According the description, I find some workaround to troubleshooting and you can skip over one of them if you have tried it.

  1. Install all pending hotfixes in Windows update, disable all anti-virus software and clean-up %temp% folder and run exe as admin.
  2. Run SFC /scannow to check if system or files have corrupted, it can help you to find out and fix it, refer to: https://support.microsoft.com/en-ae/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system .
  3. Run fix it tool to automatically repair issues including corrupted registry keys that block you from installing or removing programs
  4. If your OS is Windows 7, open registry and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CURRENT CONTROL SET\SERVICES\MSIserver\WOW64. Right click on WOW64, then select Modify**, Set Value Data to 0**. Close everything, reboot, then re-run the VS installer.
  5. See this thread and there are 3 method worthy trying: https://answers.microsoft.com/en-us/windows/forum/windows_vista-performance/the-windows-installer-service-could-not-be/8acfaa74-274b-492e-b65d-0e4a6b8ff470?auth=1
  6. upgrade your OS, reboot your machine and running the install again.

If it still persists, I need your help to the VS installation log. Please use http://aka.ms/vscollect to gather the installation logs. After using it, you will find vslogs.zip under %temp% folder. Please upload the file to https://onedrive.live.com/ and share the link here.

Looking forwards your reply.

Br

May

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]

Friday, January 25, 2019 9:09 AM

Hi Dev1089,

Is there any update could be shared here?

Have you tried my suggestion and how’s going on? I hope hear you feedback because I wonder know if my reply is helpful J

If possible, please give me a back.

May

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]

Monday, February 4, 2019 5:34 PM

Hi May,

Thanks for the response.

I am able to fix it by changing the installer setting to 1

Registry Key
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

Regards,

Anwar

Anwar Shaik

Tuesday, February 5, 2019 2:08 AM

Hi Anwar_S,

Thank you for your sharing and we are gald you solevd this issue.

Rely on this error code:1601. using the experience of your workaround for reference, i hope you could mark your workaround as answer. For that, it would be help other members have a try when they enountered similar issue. And if it useful, they will take a vote for your workaround, it must be help more and more members, i believe.

Wishing a heppy new year.

May 

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]