DTF Bug with new Windows 10 Modern ARP #4857

Closed
wixbot opened this Issue Aug 13, 2015 · 16 comments

Projects

None yet

4 participants

@wixbot
Collaborator
wixbot commented Aug 13, 2015

Please see:
http://blog.iswix.com/2015/08/dtf-bug-with-new-windows-10-apps-and.html

Summary: Windows 10 has a new screen for invoking uninstalls. It invokes with a different process and current directory. Something about this is causing immediate DTF custom actions to fail to initialize rundll.exe.

Action start 11:22:33: REDACTED.
SFXCA: Failed to create new CA process via RUNDLL32. Error code: 575
CustomAction REDACTED returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Originally opened by chrpai

@wixbot
Collaborator
wixbot commented Aug 16, 2015

On Win10 x86, I get:

SFXCA: Extracting custom action to temporary directory: C:\Users\Tester\AppData\Local\Temp\MSIDF5B.tmp-
SFXCA: Binding to CLR version v4.0.30319
SFXCA: Failed to create app domain. Error code 0x80073B20
CustomAction CustomAction1 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Originally posted by barnson

@wixbot
Collaborator
wixbot commented Aug 17, 2015

My CA was compiled for .NET 2.0 and had a CA.Config with useLegacyV2RuntimeActivationPolicy=true and supportedRuntime elements for v4.0 and v2.0.50727. However the log file never got past invoking RunDLL32 so I don't think this matters. Of note all of my machines were 64bit that had been upgraded from Windows 8.1. I'll spin up some VM's tonight and do more scenario testing.

Originally posted by chrpai

@wixbot
Collaborator
wixbot commented Aug 17, 2015

Customer feedback indicates they can only repro on Win 10 x64 not x86. Both clean installs and upgrade installs repro.

Originally posted by chrpai

@wixbot
Collaborator
wixbot commented Aug 18, 2015

SFXCA: Extracting custom action to temporary directory: C:\Users\Tester\AppData\Local\Temp\MSIDF5B.tmp-\
SFXCA: Binding to CLR version v4.0.30319
SFXCA: Failed to create app domain. Error code 0x80073B20
CustomAction CustomAction1 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

@wixbot
Collaborator
wixbot commented Aug 18, 2015

Candidate for 3.10R2 if we get a fix soon enough.

Release changed from v3.10 to v3.11

@wixbot
Collaborator
wixbot commented Nov 1, 2015

Originally changed by rseanhall
AssignedTo set to shall

@wixbot
Collaborator
wixbot commented Nov 1, 2015

Wix3 pull request - wixtoolset/wix3#312

Will send wix4 pull request once wix3 is accepted.

Originally posted by rseanhall

@wixbot wixbot added bug sdk labels Dec 20, 2015
@rseanhall rseanhall was assigned by wixbot Dec 20, 2015
@wixbot wixbot added this to the v3.11 milestone Dec 20, 2015
@rseanhall rseanhall added a commit to rseanhall/wix4 that referenced this issue Feb 5, 2016
@rseanhall rseanhall Add history entry for 4857. bcede41
@rseanhall
Member

@chrpai Fix included in WiX weekly release 3.11.0.129, pull request pending for v4.

@robmen robmen added a commit to wixtoolset/wix4 that closed this issue Feb 12, 2016
@rseanhall @robmen rseanhall + robmen Add history entry for 4857. 42cc775
@kdmandawe

which version/release should I download that includes the fix for this?

@robmen
Member
robmen commented May 28, 2016

WiX v3.11 has the fix.

@kdmandawe

Thanks Rob. However, after I downloaded and installed v3.11.0.504 from http://wixtoolset.org/releases/ I still encounter the error on installing from "'Apps & Features". I also tried v4.0.3922.0, still no luck. Installing from the command line or control panel all works fine. Help is much appreciated.

@rseanhall
Member

Can you double check that your managed CA dll is being built with the newer MakeSfxCA.exe? If so, then please provide an MSI log with the error.

@kdmandawe

Hi Sean, here are the commands I ran:

Candle:

"C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe" -d"DevEnvDir=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\\" -d"SolutionDir=c:\users\admin\documents\visual studio 2015\Projects\SamplePDV1\\" -dSolutionExt=.sln -dSolutionFileName=SamplePDV1.sln -dSolutionName=SamplePDV1 -d"SolutionPath=c:\users\admin\documents\visual studio 2015\Projects\SamplePDV1\SamplePDV1.sln" -dConfiguration=Release -dOutDir=bin\Release\ -dPlatform=x86 -d"ProjectDir=c:\users\admin\documents\visual studio 2015\Projects\SamplePDV1\SamplePDV1\\" -dProjectExt=.wixproj -dProjectFileName=SamplePDV1.wixproj -dProjectName=SamplePDV1 -d"ProjectPath=c:\users\admin\documents\visual studio 2015\Projects\SamplePDV1\SamplePDV1\SamplePDV1.wixproj" -d"TargetDir=c:\users\admin\documents\visual studio 2015\Projects\SamplePDV1\SamplePDV1\bin\Release\\" -dTargetExt=.msi -dTargetFileName=SamplePDV1.msi -dTargetName=SamplePDV1 -d"TargetPath=c:\users\admin\documents\visual studio 2015\Projects\SamplePDV1\SamplePDV1\bin\Release\SamplePDV1.msi" -out obj\Release\ -arch x86 -ext "C:\Program Files (x86)\WiX Toolset v3.11\bin\\WixUtilExtension.dll" Product.wxs

Light:

"C:\Program Files (x86)\WiX Toolset v3.11\bin\Light.exe" -out "c:\users\admin\documents\visual studio 2015\Projects\SamplePDV1\SamplePDV1\bin\Release\SamplePDV1.msi" -pdbout "c:\users\admin\documents\visual studio 2015\Projects\SamplePDV1\SamplePDV1\bin\Release\SamplePDV1.wixpdb" -cultures:null -ext "C:\Program Files (x86)\WiX Toolset v3.11\bin\\WixUtilExtension.dll" -contentsfile obj\Release\SamplePDV1.wixproj.BindContentsFileListnull.txt -outputsfile obj\Release\SamplePDV1.wixproj.BindOutputsFileListnull.txt -builtoutputsfile obj\Release\SamplePDV1.wixproj.BindBuiltOutputsFileListnull.txt -wixprojectfile "c:\users\admin\documents\visual studio 2015\Projects\SamplePDV1\SamplePDV1\SamplePDV1.wixproj" obj\Release\Product.wixobj -sice:ICE38 -sice:ICE64

Am I missing something? Thanks.

@rseanhall
Member

This bug is about managed custom actions, does your MSI have any? Those commands are for building the MSI, not the managed custom actions.

@kdmandawe

My CA is calling a java application:

<CustomAction Id="LaunchUninstallPrompt" Directory="dir3D8C2B6BEC447DDCC50D1386BD4CD865" ExeCommand="[SystemFolder]cmd.exe /C start /wait pdv-uninstall-prompt.jar" Return="check" Impersonate='no'/>

This is running fine when ran using cli and control panel but not in ''Apps & Features". I'm thinking this is something similar to the issue resolved here.

@rseanhall
Member

The underlying issue is in Windows Installer, Microsoft will have to fix that. All WiX could do was workaround it in DTF.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment