WiX Toolset PermissionEx Problem - App Does Not Run After Installation












2















I have an application in Wpf/C# and I created an installer with the WiX Toolset. The installer works on all tested computers, it does not display any error messages. However, on some machines, the application does not run after installation, even with an administrator user. I believe it's some permission problem, but I'm not sure. How do I give permissions to the current user?



UPDATE:
So far the problem has only occurred on two machines with Windows 10 Home. I thought it might be the InstallerVersion that I set.



Below are the most relevant code snippets.



Any help is very welcome. Thank you.



<Product Id="{2A173950-... }"
Codepage="UTF-8"
Name="Xyz"
Language="1033"
Version="1.0"
Manufacturer="Xyz Software"
UpgradeCode="{8B843496-... }">

<Package InstallerVersion="301"
Compressed="yes"
InstallScope="perMachine"
Manufacturer="Xyz Software"
Description="Xyz Installer"
Keywords="Practice,Installer,MSI"
Comments="(c) 2018, Xyz Software" />

<Feature Id="ProductFeature" Title="Xyz Installer" Level="1">
<ComponentGroupRef Id="ApplicationComponents" />
<ComponentGroupRef Id="DataComponents" />
<ComponentGroupRef Id="SavedFilesEmptyFolder" />
<ComponentGroupRef Id="StartMenuComponents" />
<ComponentGroupRef Id="DesktopComponents" />
</Feature>




<Fragment>
<Directory Id="TARGETDIR" Name="SourceDir">
<!--Program Files Folder-->
<Directory Id="ProgramFilesFolder">
<Directory Id="CompanyFolder" Name="Xyz Software" >
<Directory Id="ApplicationFolder" Name="Xyz" >
<Directory Id="DataFolder" Name="Data" >
<Directory Id="SavedFilesFolder" Name="Saved Files" />
</Directory>
</Directory>
</Directory>
</Directory>
<!--Start Menu-->
<Directory Id="ProgramMenuFolder">
<Directory Id="StartMenuFolder" Name="Xyz" />
</Directory>
<!--Desktop-->
<Directory Id="DesktopFolder" Name="Desktop" />
</Directory>




<Fragment>
<ComponentGroup Id="ApplicationComponents" Directory="ApplicationFolder">
<Component Id="CmpXyzExe" Guid="{1EA7372D-... }">
<File Id="FilXyzExe" Source="Xyz.exe" KeyPath="yes" />
</Component>
<Component Id="CmpSetPermissionsApp" Guid="{36CDCE9A-... }" >
<CreateFolder>
<util:PermissionEx User="Administrators" GenericAll="yes" />
<util:PermissionEx User="Users" GenericAll="yes" />
</CreateFolder>
</Component>
</ComponentGroup>

<ComponentGroup Id="DataComponents" Directory="DataFolder">
<Component Id="CmpXyzDic" Guid="{A32B6F47-... }">
<File Id="FilXyzDic" Source="Xyz.dic" />
</Component>
</ComponentGroup>


<Fragment>
<ComponentGroup Id="StartMenuComponents" Directory="StartMenuFolder">
<Component Id="CmpStartMenuShortcuts" Guid="{818AD65E-... }">
<CreateFolder />
<Shortcut Id="SctApplication"
Name="Xyz"
Target="[ApplicationFolder]Xyz.exe" />
<Shortcut Id="SctUninstall"
Name="Uninstall Xyz"
Description="Uninstalls Xyz and all of its components"
Target="[System64Folder]msiexec.exe"
Arguments="/x [ProductCode]" />
<RemoveFolder Id="RmvStartMenuComponents"
On="uninstall" />
<RegistryValue Root="HKCU"
Key="SoftwareMicrosoftXyz"
Name="installed"
Type="integer"
Value="1"
KeyPath="yes" />
</Component>
</ComponentGroup>




<Fragment>
<ComponentGroup Id="DesktopComponents" Directory="DesktopFolder">
<Component Id="CmpDesktopShortcuts" Guid="{4FC34354-... }">
<Shortcut Id="SctApplicationDesktop"
Name="Xyz"
Target="[ApplicationFolder]Xyz.exe" />
<RemoveFolder Id="RmvDesktopComponents"
On="uninstall" />
<RegistryValue Root="HKCU"
Key="SoftwareMicrosoftXyz"
Name="installed"
Type="integer"
Value="1"
KeyPath="yes" />
</Component>
</ComponentGroup>











share|improve this question

























  • Are you expecting the application to start immediately after finishing the installation? Or do you mean that the user can't launch the installed application from start menu or .exe after the installation?

    – Hemaolle
    Nov 17 '18 at 19:56











  • I'm sorry for not being clear Hemaolle, I wanted to say that the user can not start the application after installation.

    – Jose Afonso
    Nov 17 '18 at 20:16











  • Going to look later, but maybe just verify the permissions as attempted explained here.

    – Stein Åsmul
    Nov 18 '18 at 16:37
















2















I have an application in Wpf/C# and I created an installer with the WiX Toolset. The installer works on all tested computers, it does not display any error messages. However, on some machines, the application does not run after installation, even with an administrator user. I believe it's some permission problem, but I'm not sure. How do I give permissions to the current user?



UPDATE:
So far the problem has only occurred on two machines with Windows 10 Home. I thought it might be the InstallerVersion that I set.



Below are the most relevant code snippets.



Any help is very welcome. Thank you.



<Product Id="{2A173950-... }"
Codepage="UTF-8"
Name="Xyz"
Language="1033"
Version="1.0"
Manufacturer="Xyz Software"
UpgradeCode="{8B843496-... }">

<Package InstallerVersion="301"
Compressed="yes"
InstallScope="perMachine"
Manufacturer="Xyz Software"
Description="Xyz Installer"
Keywords="Practice,Installer,MSI"
Comments="(c) 2018, Xyz Software" />

<Feature Id="ProductFeature" Title="Xyz Installer" Level="1">
<ComponentGroupRef Id="ApplicationComponents" />
<ComponentGroupRef Id="DataComponents" />
<ComponentGroupRef Id="SavedFilesEmptyFolder" />
<ComponentGroupRef Id="StartMenuComponents" />
<ComponentGroupRef Id="DesktopComponents" />
</Feature>




<Fragment>
<Directory Id="TARGETDIR" Name="SourceDir">
<!--Program Files Folder-->
<Directory Id="ProgramFilesFolder">
<Directory Id="CompanyFolder" Name="Xyz Software" >
<Directory Id="ApplicationFolder" Name="Xyz" >
<Directory Id="DataFolder" Name="Data" >
<Directory Id="SavedFilesFolder" Name="Saved Files" />
</Directory>
</Directory>
</Directory>
</Directory>
<!--Start Menu-->
<Directory Id="ProgramMenuFolder">
<Directory Id="StartMenuFolder" Name="Xyz" />
</Directory>
<!--Desktop-->
<Directory Id="DesktopFolder" Name="Desktop" />
</Directory>




<Fragment>
<ComponentGroup Id="ApplicationComponents" Directory="ApplicationFolder">
<Component Id="CmpXyzExe" Guid="{1EA7372D-... }">
<File Id="FilXyzExe" Source="Xyz.exe" KeyPath="yes" />
</Component>
<Component Id="CmpSetPermissionsApp" Guid="{36CDCE9A-... }" >
<CreateFolder>
<util:PermissionEx User="Administrators" GenericAll="yes" />
<util:PermissionEx User="Users" GenericAll="yes" />
</CreateFolder>
</Component>
</ComponentGroup>

<ComponentGroup Id="DataComponents" Directory="DataFolder">
<Component Id="CmpXyzDic" Guid="{A32B6F47-... }">
<File Id="FilXyzDic" Source="Xyz.dic" />
</Component>
</ComponentGroup>


<Fragment>
<ComponentGroup Id="StartMenuComponents" Directory="StartMenuFolder">
<Component Id="CmpStartMenuShortcuts" Guid="{818AD65E-... }">
<CreateFolder />
<Shortcut Id="SctApplication"
Name="Xyz"
Target="[ApplicationFolder]Xyz.exe" />
<Shortcut Id="SctUninstall"
Name="Uninstall Xyz"
Description="Uninstalls Xyz and all of its components"
Target="[System64Folder]msiexec.exe"
Arguments="/x [ProductCode]" />
<RemoveFolder Id="RmvStartMenuComponents"
On="uninstall" />
<RegistryValue Root="HKCU"
Key="SoftwareMicrosoftXyz"
Name="installed"
Type="integer"
Value="1"
KeyPath="yes" />
</Component>
</ComponentGroup>




<Fragment>
<ComponentGroup Id="DesktopComponents" Directory="DesktopFolder">
<Component Id="CmpDesktopShortcuts" Guid="{4FC34354-... }">
<Shortcut Id="SctApplicationDesktop"
Name="Xyz"
Target="[ApplicationFolder]Xyz.exe" />
<RemoveFolder Id="RmvDesktopComponents"
On="uninstall" />
<RegistryValue Root="HKCU"
Key="SoftwareMicrosoftXyz"
Name="installed"
Type="integer"
Value="1"
KeyPath="yes" />
</Component>
</ComponentGroup>











share|improve this question

























  • Are you expecting the application to start immediately after finishing the installation? Or do you mean that the user can't launch the installed application from start menu or .exe after the installation?

    – Hemaolle
    Nov 17 '18 at 19:56











  • I'm sorry for not being clear Hemaolle, I wanted to say that the user can not start the application after installation.

    – Jose Afonso
    Nov 17 '18 at 20:16











  • Going to look later, but maybe just verify the permissions as attempted explained here.

    – Stein Åsmul
    Nov 18 '18 at 16:37














2












2








2








I have an application in Wpf/C# and I created an installer with the WiX Toolset. The installer works on all tested computers, it does not display any error messages. However, on some machines, the application does not run after installation, even with an administrator user. I believe it's some permission problem, but I'm not sure. How do I give permissions to the current user?



UPDATE:
So far the problem has only occurred on two machines with Windows 10 Home. I thought it might be the InstallerVersion that I set.



Below are the most relevant code snippets.



Any help is very welcome. Thank you.



<Product Id="{2A173950-... }"
Codepage="UTF-8"
Name="Xyz"
Language="1033"
Version="1.0"
Manufacturer="Xyz Software"
UpgradeCode="{8B843496-... }">

<Package InstallerVersion="301"
Compressed="yes"
InstallScope="perMachine"
Manufacturer="Xyz Software"
Description="Xyz Installer"
Keywords="Practice,Installer,MSI"
Comments="(c) 2018, Xyz Software" />

<Feature Id="ProductFeature" Title="Xyz Installer" Level="1">
<ComponentGroupRef Id="ApplicationComponents" />
<ComponentGroupRef Id="DataComponents" />
<ComponentGroupRef Id="SavedFilesEmptyFolder" />
<ComponentGroupRef Id="StartMenuComponents" />
<ComponentGroupRef Id="DesktopComponents" />
</Feature>




<Fragment>
<Directory Id="TARGETDIR" Name="SourceDir">
<!--Program Files Folder-->
<Directory Id="ProgramFilesFolder">
<Directory Id="CompanyFolder" Name="Xyz Software" >
<Directory Id="ApplicationFolder" Name="Xyz" >
<Directory Id="DataFolder" Name="Data" >
<Directory Id="SavedFilesFolder" Name="Saved Files" />
</Directory>
</Directory>
</Directory>
</Directory>
<!--Start Menu-->
<Directory Id="ProgramMenuFolder">
<Directory Id="StartMenuFolder" Name="Xyz" />
</Directory>
<!--Desktop-->
<Directory Id="DesktopFolder" Name="Desktop" />
</Directory>




<Fragment>
<ComponentGroup Id="ApplicationComponents" Directory="ApplicationFolder">
<Component Id="CmpXyzExe" Guid="{1EA7372D-... }">
<File Id="FilXyzExe" Source="Xyz.exe" KeyPath="yes" />
</Component>
<Component Id="CmpSetPermissionsApp" Guid="{36CDCE9A-... }" >
<CreateFolder>
<util:PermissionEx User="Administrators" GenericAll="yes" />
<util:PermissionEx User="Users" GenericAll="yes" />
</CreateFolder>
</Component>
</ComponentGroup>

<ComponentGroup Id="DataComponents" Directory="DataFolder">
<Component Id="CmpXyzDic" Guid="{A32B6F47-... }">
<File Id="FilXyzDic" Source="Xyz.dic" />
</Component>
</ComponentGroup>


<Fragment>
<ComponentGroup Id="StartMenuComponents" Directory="StartMenuFolder">
<Component Id="CmpStartMenuShortcuts" Guid="{818AD65E-... }">
<CreateFolder />
<Shortcut Id="SctApplication"
Name="Xyz"
Target="[ApplicationFolder]Xyz.exe" />
<Shortcut Id="SctUninstall"
Name="Uninstall Xyz"
Description="Uninstalls Xyz and all of its components"
Target="[System64Folder]msiexec.exe"
Arguments="/x [ProductCode]" />
<RemoveFolder Id="RmvStartMenuComponents"
On="uninstall" />
<RegistryValue Root="HKCU"
Key="SoftwareMicrosoftXyz"
Name="installed"
Type="integer"
Value="1"
KeyPath="yes" />
</Component>
</ComponentGroup>




<Fragment>
<ComponentGroup Id="DesktopComponents" Directory="DesktopFolder">
<Component Id="CmpDesktopShortcuts" Guid="{4FC34354-... }">
<Shortcut Id="SctApplicationDesktop"
Name="Xyz"
Target="[ApplicationFolder]Xyz.exe" />
<RemoveFolder Id="RmvDesktopComponents"
On="uninstall" />
<RegistryValue Root="HKCU"
Key="SoftwareMicrosoftXyz"
Name="installed"
Type="integer"
Value="1"
KeyPath="yes" />
</Component>
</ComponentGroup>











share|improve this question
















I have an application in Wpf/C# and I created an installer with the WiX Toolset. The installer works on all tested computers, it does not display any error messages. However, on some machines, the application does not run after installation, even with an administrator user. I believe it's some permission problem, but I'm not sure. How do I give permissions to the current user?



UPDATE:
So far the problem has only occurred on two machines with Windows 10 Home. I thought it might be the InstallerVersion that I set.



Below are the most relevant code snippets.



Any help is very welcome. Thank you.



<Product Id="{2A173950-... }"
Codepage="UTF-8"
Name="Xyz"
Language="1033"
Version="1.0"
Manufacturer="Xyz Software"
UpgradeCode="{8B843496-... }">

<Package InstallerVersion="301"
Compressed="yes"
InstallScope="perMachine"
Manufacturer="Xyz Software"
Description="Xyz Installer"
Keywords="Practice,Installer,MSI"
Comments="(c) 2018, Xyz Software" />

<Feature Id="ProductFeature" Title="Xyz Installer" Level="1">
<ComponentGroupRef Id="ApplicationComponents" />
<ComponentGroupRef Id="DataComponents" />
<ComponentGroupRef Id="SavedFilesEmptyFolder" />
<ComponentGroupRef Id="StartMenuComponents" />
<ComponentGroupRef Id="DesktopComponents" />
</Feature>




<Fragment>
<Directory Id="TARGETDIR" Name="SourceDir">
<!--Program Files Folder-->
<Directory Id="ProgramFilesFolder">
<Directory Id="CompanyFolder" Name="Xyz Software" >
<Directory Id="ApplicationFolder" Name="Xyz" >
<Directory Id="DataFolder" Name="Data" >
<Directory Id="SavedFilesFolder" Name="Saved Files" />
</Directory>
</Directory>
</Directory>
</Directory>
<!--Start Menu-->
<Directory Id="ProgramMenuFolder">
<Directory Id="StartMenuFolder" Name="Xyz" />
</Directory>
<!--Desktop-->
<Directory Id="DesktopFolder" Name="Desktop" />
</Directory>




<Fragment>
<ComponentGroup Id="ApplicationComponents" Directory="ApplicationFolder">
<Component Id="CmpXyzExe" Guid="{1EA7372D-... }">
<File Id="FilXyzExe" Source="Xyz.exe" KeyPath="yes" />
</Component>
<Component Id="CmpSetPermissionsApp" Guid="{36CDCE9A-... }" >
<CreateFolder>
<util:PermissionEx User="Administrators" GenericAll="yes" />
<util:PermissionEx User="Users" GenericAll="yes" />
</CreateFolder>
</Component>
</ComponentGroup>

<ComponentGroup Id="DataComponents" Directory="DataFolder">
<Component Id="CmpXyzDic" Guid="{A32B6F47-... }">
<File Id="FilXyzDic" Source="Xyz.dic" />
</Component>
</ComponentGroup>


<Fragment>
<ComponentGroup Id="StartMenuComponents" Directory="StartMenuFolder">
<Component Id="CmpStartMenuShortcuts" Guid="{818AD65E-... }">
<CreateFolder />
<Shortcut Id="SctApplication"
Name="Xyz"
Target="[ApplicationFolder]Xyz.exe" />
<Shortcut Id="SctUninstall"
Name="Uninstall Xyz"
Description="Uninstalls Xyz and all of its components"
Target="[System64Folder]msiexec.exe"
Arguments="/x [ProductCode]" />
<RemoveFolder Id="RmvStartMenuComponents"
On="uninstall" />
<RegistryValue Root="HKCU"
Key="SoftwareMicrosoftXyz"
Name="installed"
Type="integer"
Value="1"
KeyPath="yes" />
</Component>
</ComponentGroup>




<Fragment>
<ComponentGroup Id="DesktopComponents" Directory="DesktopFolder">
<Component Id="CmpDesktopShortcuts" Guid="{4FC34354-... }">
<Shortcut Id="SctApplicationDesktop"
Name="Xyz"
Target="[ApplicationFolder]Xyz.exe" />
<RemoveFolder Id="RmvDesktopComponents"
On="uninstall" />
<RegistryValue Root="HKCU"
Key="SoftwareMicrosoftXyz"
Name="installed"
Type="integer"
Value="1"
KeyPath="yes" />
</Component>
</ComponentGroup>








c# wpf wix






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 17 '18 at 20:32







Jose Afonso

















asked Nov 17 '18 at 19:44









Jose Afonso Jose Afonso

134




134













  • Are you expecting the application to start immediately after finishing the installation? Or do you mean that the user can't launch the installed application from start menu or .exe after the installation?

    – Hemaolle
    Nov 17 '18 at 19:56











  • I'm sorry for not being clear Hemaolle, I wanted to say that the user can not start the application after installation.

    – Jose Afonso
    Nov 17 '18 at 20:16











  • Going to look later, but maybe just verify the permissions as attempted explained here.

    – Stein Åsmul
    Nov 18 '18 at 16:37



















  • Are you expecting the application to start immediately after finishing the installation? Or do you mean that the user can't launch the installed application from start menu or .exe after the installation?

    – Hemaolle
    Nov 17 '18 at 19:56











  • I'm sorry for not being clear Hemaolle, I wanted to say that the user can not start the application after installation.

    – Jose Afonso
    Nov 17 '18 at 20:16











  • Going to look later, but maybe just verify the permissions as attempted explained here.

    – Stein Åsmul
    Nov 18 '18 at 16:37

















Are you expecting the application to start immediately after finishing the installation? Or do you mean that the user can't launch the installed application from start menu or .exe after the installation?

– Hemaolle
Nov 17 '18 at 19:56





Are you expecting the application to start immediately after finishing the installation? Or do you mean that the user can't launch the installed application from start menu or .exe after the installation?

– Hemaolle
Nov 17 '18 at 19:56













I'm sorry for not being clear Hemaolle, I wanted to say that the user can not start the application after installation.

– Jose Afonso
Nov 17 '18 at 20:16





I'm sorry for not being clear Hemaolle, I wanted to say that the user can not start the application after installation.

– Jose Afonso
Nov 17 '18 at 20:16













Going to look later, but maybe just verify the permissions as attempted explained here.

– Stein Åsmul
Nov 18 '18 at 16:37





Going to look later, but maybe just verify the permissions as attempted explained here.

– Stein Åsmul
Nov 18 '18 at 16:37












1 Answer
1






active

oldest

votes


















0















Permissions: As commented above, maybe do a quick check to see if the permissions are applied correctly as described here: Checking
permissions.



Runtime Dependency / Requirement: If this happens on very few machines one would think the cause to be a runtime requirement that is
not met. Are you sure you have the visual studio C++ runtime installed
on the computers in question? Or some other runtime requirement?




Debugging Launch Issues: There are several older answers with suggestions on debugging. Now that I look at them they are so similar that I need to stop repeating myself in different flavors:





  • Application Launch Issues Check List (list of ideas)


  • Launch debug binaries and attach debugger - and dependency scanner tools (Which winform project files should be packed up into the installer)

  • How exactly does the WiX 'Service Install' work internally?

  • wix c# app doesn't launch after installing

  • Visual Studio installer fails on AspNetDiagnosticPack.msi

  • The setup process in windows fails access denied when trying to create "uc.micro" folder

  • Create a .config folder in the user folder

  • EXE file is not working


Procedure: In brief I would try to determine if there is a missing runtime. You can use procmon.exe or dependency walker to check for this. You can also use the debugging approach described above where you build debug binaries and connect to the binaries during launch. Provided the binary gets off the ground at all.






share|improve this answer


























  • Using Dependency Walker, I discovered a few missing libraries.

    – Jose Afonso
    Nov 26 '18 at 23:34











  • That would do it. Could be more of course. Nicely stated question by the way. I forgot to upvote it before. Let me do that now.

    – Stein Åsmul
    Nov 26 '18 at 23:51











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53354907%2fwix-toolset-permissionex-problem-app-does-not-run-after-installation%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0















Permissions: As commented above, maybe do a quick check to see if the permissions are applied correctly as described here: Checking
permissions.



Runtime Dependency / Requirement: If this happens on very few machines one would think the cause to be a runtime requirement that is
not met. Are you sure you have the visual studio C++ runtime installed
on the computers in question? Or some other runtime requirement?




Debugging Launch Issues: There are several older answers with suggestions on debugging. Now that I look at them they are so similar that I need to stop repeating myself in different flavors:





  • Application Launch Issues Check List (list of ideas)


  • Launch debug binaries and attach debugger - and dependency scanner tools (Which winform project files should be packed up into the installer)

  • How exactly does the WiX 'Service Install' work internally?

  • wix c# app doesn't launch after installing

  • Visual Studio installer fails on AspNetDiagnosticPack.msi

  • The setup process in windows fails access denied when trying to create "uc.micro" folder

  • Create a .config folder in the user folder

  • EXE file is not working


Procedure: In brief I would try to determine if there is a missing runtime. You can use procmon.exe or dependency walker to check for this. You can also use the debugging approach described above where you build debug binaries and connect to the binaries during launch. Provided the binary gets off the ground at all.






share|improve this answer


























  • Using Dependency Walker, I discovered a few missing libraries.

    – Jose Afonso
    Nov 26 '18 at 23:34











  • That would do it. Could be more of course. Nicely stated question by the way. I forgot to upvote it before. Let me do that now.

    – Stein Åsmul
    Nov 26 '18 at 23:51
















0















Permissions: As commented above, maybe do a quick check to see if the permissions are applied correctly as described here: Checking
permissions.



Runtime Dependency / Requirement: If this happens on very few machines one would think the cause to be a runtime requirement that is
not met. Are you sure you have the visual studio C++ runtime installed
on the computers in question? Or some other runtime requirement?




Debugging Launch Issues: There are several older answers with suggestions on debugging. Now that I look at them they are so similar that I need to stop repeating myself in different flavors:





  • Application Launch Issues Check List (list of ideas)


  • Launch debug binaries and attach debugger - and dependency scanner tools (Which winform project files should be packed up into the installer)

  • How exactly does the WiX 'Service Install' work internally?

  • wix c# app doesn't launch after installing

  • Visual Studio installer fails on AspNetDiagnosticPack.msi

  • The setup process in windows fails access denied when trying to create "uc.micro" folder

  • Create a .config folder in the user folder

  • EXE file is not working


Procedure: In brief I would try to determine if there is a missing runtime. You can use procmon.exe or dependency walker to check for this. You can also use the debugging approach described above where you build debug binaries and connect to the binaries during launch. Provided the binary gets off the ground at all.






share|improve this answer


























  • Using Dependency Walker, I discovered a few missing libraries.

    – Jose Afonso
    Nov 26 '18 at 23:34











  • That would do it. Could be more of course. Nicely stated question by the way. I forgot to upvote it before. Let me do that now.

    – Stein Åsmul
    Nov 26 '18 at 23:51














0












0








0








Permissions: As commented above, maybe do a quick check to see if the permissions are applied correctly as described here: Checking
permissions.



Runtime Dependency / Requirement: If this happens on very few machines one would think the cause to be a runtime requirement that is
not met. Are you sure you have the visual studio C++ runtime installed
on the computers in question? Or some other runtime requirement?




Debugging Launch Issues: There are several older answers with suggestions on debugging. Now that I look at them they are so similar that I need to stop repeating myself in different flavors:





  • Application Launch Issues Check List (list of ideas)


  • Launch debug binaries and attach debugger - and dependency scanner tools (Which winform project files should be packed up into the installer)

  • How exactly does the WiX 'Service Install' work internally?

  • wix c# app doesn't launch after installing

  • Visual Studio installer fails on AspNetDiagnosticPack.msi

  • The setup process in windows fails access denied when trying to create "uc.micro" folder

  • Create a .config folder in the user folder

  • EXE file is not working


Procedure: In brief I would try to determine if there is a missing runtime. You can use procmon.exe or dependency walker to check for this. You can also use the debugging approach described above where you build debug binaries and connect to the binaries during launch. Provided the binary gets off the ground at all.






share|improve this answer
















Permissions: As commented above, maybe do a quick check to see if the permissions are applied correctly as described here: Checking
permissions.



Runtime Dependency / Requirement: If this happens on very few machines one would think the cause to be a runtime requirement that is
not met. Are you sure you have the visual studio C++ runtime installed
on the computers in question? Or some other runtime requirement?




Debugging Launch Issues: There are several older answers with suggestions on debugging. Now that I look at them they are so similar that I need to stop repeating myself in different flavors:





  • Application Launch Issues Check List (list of ideas)


  • Launch debug binaries and attach debugger - and dependency scanner tools (Which winform project files should be packed up into the installer)

  • How exactly does the WiX 'Service Install' work internally?

  • wix c# app doesn't launch after installing

  • Visual Studio installer fails on AspNetDiagnosticPack.msi

  • The setup process in windows fails access denied when trying to create "uc.micro" folder

  • Create a .config folder in the user folder

  • EXE file is not working


Procedure: In brief I would try to determine if there is a missing runtime. You can use procmon.exe or dependency walker to check for this. You can also use the debugging approach described above where you build debug binaries and connect to the binaries during launch. Provided the binary gets off the ground at all.







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 21 '18 at 13:35

























answered Nov 18 '18 at 19:14









Stein ÅsmulStein Åsmul

21.5k1356117




21.5k1356117













  • Using Dependency Walker, I discovered a few missing libraries.

    – Jose Afonso
    Nov 26 '18 at 23:34











  • That would do it. Could be more of course. Nicely stated question by the way. I forgot to upvote it before. Let me do that now.

    – Stein Åsmul
    Nov 26 '18 at 23:51



















  • Using Dependency Walker, I discovered a few missing libraries.

    – Jose Afonso
    Nov 26 '18 at 23:34











  • That would do it. Could be more of course. Nicely stated question by the way. I forgot to upvote it before. Let me do that now.

    – Stein Åsmul
    Nov 26 '18 at 23:51

















Using Dependency Walker, I discovered a few missing libraries.

– Jose Afonso
Nov 26 '18 at 23:34





Using Dependency Walker, I discovered a few missing libraries.

– Jose Afonso
Nov 26 '18 at 23:34













That would do it. Could be more of course. Nicely stated question by the way. I forgot to upvote it before. Let me do that now.

– Stein Åsmul
Nov 26 '18 at 23:51





That would do it. Could be more of course. Nicely stated question by the way. I forgot to upvote it before. Let me do that now.

– Stein Åsmul
Nov 26 '18 at 23:51


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53354907%2fwix-toolset-permissionex-problem-app-does-not-run-after-installation%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







這個網誌中的熱門文章

Xamarin.form Move up view when keyboard appear

Post-Redirect-Get with Spring WebFlux and Thymeleaf

Anylogic : not able to use stopDelay()