The fix MSI file installed on XP was not completed (prompting the installer to be interrupted and failed to install the app.) An issue that requires restarting the setup to retry).

, I made a small program with Visual Studio 2015. Based on. Net 4.0. Use the VS Install extension to package the new install project. Packaged as an. msi file. The installation file still appears in the case where. Net Framework4.0 is already installed, and the solution is baffled.

The data of stack overflow is consulted, and the method of tracing the source of failure--command line installation. msi program, you can see the log logs. That is, msiexec/i a.msi/l*v a.log will generate a log called "A.log". The following code was found in the log

= = = Record start: 2016-8-26 21:49:10 = = =
MSI (c) (84:68) [21:49:10:453]: note:1:2262 2:patchpackage 3:2147287038
MSI (c) (84:68) [21:49:10:453]: Machine policy value ' DisableRollback ' is 0
MSI (c) (84:68) [21:49:10:453]: User policy value ' DisableRollback ' is 0
MSI (c) (84:68) [21:49:10:453]: Property change:adding the Uilevel property. Its value is ' 5 '.
MSI (c) (84:68) [21:49:10:453]: Property change:adding the ACTION property. Its value is ' INSTALL '.
MSI (c) (84:68) [21:49:10:453]: Doing action:install
MSI (c) (84:68) [21:49:10:453]: note:1:2262 2:actiontext 3:2147287038
Operation 21:49:10:install.
The operation begins 21:49:10:install.
MSI (c) (84:68) [21:49:10:453]: UI Sequence table ' InstallUISequence ' is present and populated.
MSI (c) (84:68) [21:49:10:453]: Running uisequence
MSI (c) (84:68) [21:49:10:453]: Property change:adding the EXECUTEACTION property. Its value is ' INSTALL '.
MSI (c) (84:68) [21:49:10:453]: Doing action:dirca_checkfx
Operation 21:49:10:dirca_checkfx.
The operation begins 21:49:10:DIRCA_CHECKFX.
MSI (c) (84:4C) [21:49:10:453]: Invoking remote custom action. Dll:c:\docume~1\admini~1\locals~1\temp\msi164.tmp, ENTRYPOINT:CHECKFX
MSI (c) (84:48) [21:49:10:453]: cloaking enabled.
MSI (c) (84:48) [21:49:10:453]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (84:48) [21:49:10:453]: Connected to service for CA interface.
Operation ends 21:49:10:DIRCA_CHECKFX. Returns a value of 3.
MSI (c) (84:68) [21:49:10:546]: Doing action:fatalerrorform
Operation 21:49:10:fatalerrorform.
The operation begins 21:49:10:fatalerrorform.
MSI (c) (84:6c) [21:49:10:546]: note:1:2262 2:error 3:2147287038
Information 2898. Vsi_ms_sans_serif13.0_0_0, song body, 134
MSI (c) (84:6c) [21:49:10:546]: note:1:2262 2:error 3:2147287038
Information 2898. Vsi_ms_sans_serif16.0_1_0, song body, 134
MSI (c) (84:6c) [21:49:10:546]: note:1:2262 2:error 3:2147287038
Debug:error 2826:control Line2 On dialog fatalerrorform extends beyond the boundaries of the dialog to the right by 3 p Ixels
Setup encountered an error while installing this package. This may indicate an error in this package. The error code is 2826. The parameters are: Fatalerrorform, Line2, to the right
MSI (c) (84:6c) [21:49:10:546]: note:1:2262 2:error 3:2147287038
Debug:error 2826:control bannerbmp On dialog fatalerrorform extends beyond the boundaries of the dialog 3 pixels
Setup encountered an error while installing this package. This may indicate an error in this package. The error code is 2826. The parameters are: Fatalerrorform, bannerbmp, to the right
MSI (c) (84:6c) [21:49:10:546]: note:1:2262 2:error 3:2147287038
Information 2898. vsddefaultuifont.524f4245_5254_5341_4c45_534153783400, song body, 134
MSI (c) (84:6c) [21:49:10:546]: note:1:2262 2:error 3:2147287038
Debug:error 2826:control Line1 On dialog fatalerrorform extends beyond the boundaries of the dialog to the right by 3 p Ixels
Setup encountered an error while installing this package. This may indicate an error in this package. The error code is 2826. The parameters are: Fatalerrorform, Line1, to the right
Operation 21:49:10:fatalerrorform. Dialog created
MSI (c) (84:6c) [21:49:10:625]: note:1:2731 2:0
Operation ends 21:49:12:fatalerrorform. Returns a value of 1.
Operation ends 21:49:12:install. Returns a value of 3.

Netizen Aaron stebner

                                                   

Aaron Stebner

Microsoft

MSFT

264,416 points                 11                 6                 5                         Recent achievementsProposed Answerer IRatings Board President Forums replies III View profile

In the post, it is pointed out that "return value 3" is closely related to the rollback of program installation failure.

Open the verbose log in a text editor such as Notepad and search for the string "return value 3".  In nearly all cases, this takes me-to-the section in the verbose log that lists the action of failed that initially Caus Ed Setup to rollback.

From my a.log, I can see that DIRCA_CHECKFX should be the source of the problem. After you have repeatedly reviewed the target machine's installation environment (Group Policy,. NET), determine that there should be a problem with the installation package MSI file.

Access to information just found Csharpstyle brother's post "setup Project" Windows XP cannot be installed

Mentioned in the inside

Problem phenomena Windows Installer that are made with Setup Project for Visual Studio 2013 cannot run on Windows XP and get logs in the following ways:  msiexec/i <msipath& Gt;setup.msi/l*v C:\temp\msi.log by viewing the contents of the log, the following error was found:  dirca_checkfx Return Value 3 problem reason CHECKFX's role is to check the. NET Framework version , there are two places in Setup Project: 1. Prerequisite2.launch conditions above two places must unify. In addition, the more important issue is that the Windows Installer generated by Visual Studio 2013 is incompatible with Windows XP. Workaround 1. Close Visual Studio 20132.Copy file with replace Dpca.dll from C:\Program Files (x86) \microsoft Visual Studio 10.0\common7 \tools\deployment to C:\Program Files (x86) \microsoft Visual Studio 12.0\common7\ide\commonextensions\microsoft\vsi\ Bin3. Open Project4.rebuild

Helpless install VS2010 still too laborious, moreover may not be able to solve the problem of 2015, then find other possible ways. Finally, we found a convenient way to do this on GitHub:
In the discussion of installation problem Windows XP post, bh3605 mentions:

Find and download Orca. Use an IT to open up the MSI file and look for both Actions. "Dirca_checkfx" and "vsdca_vsdlaunchconditions". Delete them. You'll find them in tables InstallExecuteSequence and installuisequence. They ' re also in the CustomAction table, but I ' ve found deleting them in just the execution sequence tables sufficed. I don ' t know why it crashes on XP only, but I believe it's because XP doesn ' t has MSVBDPCA.dll.  You can find more information on the Actions I mentioned here:http://stackoverflow.com/a/8613979+1 for building something Related to pandora!

On the internet to check a lot of posts, said MSI installation package DIRCA_CHECKFX and vsdca_vsdlaunchconditions These two operations are prone to problems.

That is, download the Ocra tool and delete the two action "DIRCA_CHECKFX" and "vsdca_vsdlaunchconditions".
The first step is to download and open the Ocra.exe in the Ocra tool,

Second, open the generated (need to change) MSI file, find the CustomAction table, and find two action from the table

In the third part, right-click the two action, delete the row, and then save it. The installation will be installed successfully.

Note: After the revision, open the record tracking installation process, there is still an error problem. However, the program can be installed successfully and run properly. It would be wishful thinking to consider replacing the Dpca.dll file or the VSI group update (XP has been scrapped) for a complete solution. Replace Dpca.dll do not know whether there will be other effects.

Stack overflow post dirca_checkfx Return Value 3-vs Deployment Project There are other options, such as

Here's what I do to workaround this issue for a 32-bit deployment Project.1.build the Setup project in VS2010 once. This are not dogged by the issue but I didn ' t want to the keep building in a different VS version.2.open the RE  Sulting msi with Orca, select the Binary table and export the content of Msvbdpcadll to a file.3.now after you build it in VS2013 use Orca to import the exported data into Binary\msvbdpcadll to fix the package.  I have to do a similar thing with the 64-bit project and it's to import the correct installutil binary (being C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtilLib.dll).

User analysis, installation package problems because of the original

The preview of the. Vdproj Resurrection uses DLLs that don ' t support Windows XP or Server 2003. Microsoft posted an update that might has a fixed that bug.

Oh ~

I hope each unit will be eliminated early antique xp!!!

The fix MSI file installed on XP was not completed (prompting the installer to be interrupted and failed to install the app.) An issue that requires restarting the setup to retry).