This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- installing as system account uses the wrong directory
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 26, 2017
02:20 PM
installing as system account uses the wrong directory
Many desktop management tools are starting to install via the system account. In my case my installer fails. The log yields this:
MSI (s) (80:44) [20:59:20:956]: Note: 1: 2203 2: C:\Windows\system32\config\systemprofile\AppData\Local\Downloaded Installations\{2A799340-820C-4C05-8DDE-26CA1B685CB8}\Awesome_App.msi 3: -2147287037
This error means that the file was not found.
It looks like the installer is not looking in the right place:
C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Downloaded Installations\{2A799340-820C-4C05-8DDE-26CA1B685CB8}\Awesome_App.msi
Is there a setting that controls where it should look for the extracted msi file? Usually, this location is for cached installers so that the repair function will work.
Thanks,
MSI (s) (80:44) [20:59:20:956]: Note: 1: 2203 2: C:\Windows\system32\config\systemprofile\AppData\Local\Downloaded Installations\{2A799340-820C-4C05-8DDE-26CA1B685CB8}\Awesome_App.msi 3: -2147287037
This error means that the file was not found.
It looks like the installer is not looking in the right place:
C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Downloaded Installations\{2A799340-820C-4C05-8DDE-26CA1B685CB8}\Awesome_App.msi
Is there a setting that controls where it should look for the extracted msi file? Usually, this location is for cached installers so that the repair function will work.
Thanks,
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 27, 2017
02:22 PM
Found a post in 2011. Apparently, this has never been fixed.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 27, 2017
04:25 PM
It appears that the issue is directly related to the "Cache MSI Locally" property. If it is on it fails use the correct directory. If it is off then the installation path changes to windows\temp and everything works.
Since my customer's use of is only using SCCM, then I don't need to cache and enable the repair option. Now I'm on the hunt for a property that will disable the "cache msi locally" from the command-line or set it via custom action when the user is system
Since my customer's use of is only using SCCM, then I don't need to cache and enable the repair option. Now I'm on the hunt for a property that will disable the "cache msi locally" from the command-line or set it via custom action when the user is system
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 03, 2017
05:52 PM
Installshield 2015 fixes this issue. maybe Installshield 2014, but I haven't tried that.
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)