Partilhar via

Possible cause of error code 1719 or 1723 when installing a 64-bit MSI

  • Artigo

I have heard from a few people in the past who have run into setup failures with error code 1719 or 1723 while installing the 64-bit version of the .NET Framework on a 64-bit version of Windows.  I want to describe the underlying issue in a little more detail and provide a couple of possible workarounds in case you run into this type of issue in the future.

How to diagnose this issue

If you are encountering this issue, you will see one of the following errors in the verbose MSI log file for the failing installation:

MSI (s) (DC:FC) [12:34:56:023]: Invoking remote custom action. DLL: C:\Windows\Installer\MSICE44.tmp, Entrypoint: SchedSecureObjects
MSI (s) (DC:B8) [12:34:56:024]: Generating random cookie.
MSI (s) (DC:B8) [12:34:56:051]: Created Custom Action Server with PID 1884 (0x75C).
MSI (s) (DC:98) [12:34:56:092]: Running as a service.
MSI (s) (DC:98) [12:34:56:094]: Custom Action Server rejected - Wrong Context
MSI (s) (DC:B8) [12:34:56:097]: CA Server Process has terminated.
Action start 12:34:56: SchedSecureObjects_x64.
MSI (s) (DC:94) [12:34:56:098]: Note: 1: 1719
CustomAction SchedSecureObjects_x64 returned actual error code 1601 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (DC:94) [12:34:56:738]: Product: Microsoft .NET Framework 4 Client Profile -- Error 1719. 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.

MSI (s) (B4:74) [12:34:56:098]: Note: 1: 1723
CustomAction SchedSecureObjects_x64 returned actual error code 1157 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (B4:74) [12:34:56:738]: Product: Microsoft .NET Framework 4 Client Profile -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.  Action SchedSecureObjects_x64, entry: SchedSecureObjects, library: C:\Windows\Installer\MSIE8C8.tmp

The underlying problem in this scenario is that Windows Installer is incorrectly configured to run in 32-bit mode.  64-bit custom actions cannot run in 32-bit mode, and so any 64-bit MSI that includes a 64-bit custom action (including, but not limited to, all 64-bit versions of the .NET Framework starting with 2.0) will fail in this way the first time it tries to run a 64-bit custom action. 

How to work around this issue

If you are encountering this issue, you can remove the following registry value to prevent Windows Installer from trying to run 64-bit custom actions in 32-bit mode:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msiserver]
WOW64=1

If the above registry value does not exist on your computer, then there is another possible root cause and workaround described in this blog post from Robert Flaming.

Comments

  • Anonymous
    February 02, 2012
    registry is already set to 1 and still its not installing

  • Anonymous
    February 02, 2012
    i check the [this blog post from Robert Flaming] it will not give me any clue. we just did a repair install in windows 7 and still its not installing i tried to check the version of windows installer both in syswow64 and system32, it has version 5.0 im confuse on how will i install this update in a 64 bit computer.

  • Anonymous
    February 02, 2012
    i check the HKLMSoftwareMicrosoftWindowsCurrentVersionInstaller ! MsiExecCA32 the registry key is right same goes with the HKLMSoftwareMicrosoftWindowsCurrentVersionInstaller ! MsiExecCA64 can i have a much deeper troubleshooting step for this error thanks

  • Anonymous
    February 02, 2012
    Hi Ryoko - This blog post only describes one possible cause for this type of error.  Do you have a verbose MSI log file from the failing installation, and if so, can you please upload it to a file server (such as http://skydrive.live.com) and post a link back here so I can download it and take a closer look?

  • Anonymous
    February 08, 2012
    Ryoko "registry is already set to 1 and still its not installing" Read the post again: If you are encountering this issue, you can "!remove!" the following registry value to prevent Windows Installer from trying to run 64-bit custom actions in 32-bit mode:

  • Anonymous
    March 14, 2012
    Hi, I have just changes "wow64=1" to "wow64=0" and all my problems are gone. BR. [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesmsiserver] WOW64=0

  • Anonymous
    June 20, 2013
    hey it would be nice if you could help me regarding windows installer issue it says it's not installed right and i am running windows 8 and tips/solutions ?

  • Anonymous
    June 24, 2013
    Hi John - Could you please provide more detail about the error that you're seeing in this scenario?  What is the exact error message you see, and when do you see it (for example, do you see it when you boot your computer, when you try to launch a specific program, etc)?

  • Anonymous
    November 29, 2013
    hey i cheacked  but in my version of windows seven i didint find the folder called msiserver isthat a problem, everything is according except that folder, its just not there.  

  • Anonymous
    December 01, 2013
    Hi salman - The msiserver value is a registry sub-key name, not a folder name.  You need to open regedit.exe and look at HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesmsiserver to find it.

  • Anonymous
    October 07, 2014
    Hi Aaron We are encountering the 1723 error. I"ve got the log files. Unfortunately I've not been able to get access to the systems where this error is encountered. I've tried the above steps to reproduce the error in a different Win 8 64 bit machine but not able to reproduce it. Could you please help? Thanks kajal

  • Anonymous
    October 08, 2014
    Hi Kajal Biswas - The issue described in this blog post is only one possible cause of a 1723 error.  It isn't the only possible cause.  If you're not able to reproduce the failure by manually changing that registry key, then you're likely hitting a different problem than the one described here.  There is another possible root cause described at blogs.msdn.com/.../439834.aspx.  If that doesn't help either, then I'd suggest doing a web search for Windows Installer error 1723 and trying some of the other things suggested in the forum posts that will appear in the search results.

  • Anonymous
    October 08, 2014
    The comment has been removed

  • Anonymous
    October 08, 2014
    The comment has been removed

  • Anonymous
    October 21, 2014
    Hi I use windows 8.1 and when I want to install office 2013,it gives me this error error 1719.the windows installer service could not be accessed. what can I do??

  • Anonymous
    October 21, 2014
    Hi Morteza - I'd suggest trying the repair steps in support.microsoft.com/.../2642495 to see if they help resolve this error.  If that doesn't help, then I'd suggest posting a question on the Windows 8.1 forum at answers.microsoft.com/.../windows8_1 to see if someone there has any other ideas for you to try.

  • Anonymous
    October 26, 2014
    Just Install This ( Install x64 + x86 ) www.microsoft.com/.../details.aspx This 100% Fix My Problem

    • Anonymous
      March 01, 2019
      Thanks! It hepled me on Server 2016 - Visual C++ Redistributable for Visual Studio 2012 Update 4.