A system administrator deploys a corporate application to several Windows 11 workstations using an automated deployment service running under the Local System account context with a silent installation switch. Although the deployment service reports a successful exit code, users report that the application crashes on launch under standard user accounts. Further analysis shows the installer relies on the %APPDATA% environment variable to write default configuration templates during installation. Which of the following best explains why the application was configured incorrectly during deployment?
- Running the installer under the Local System account resolved %APPDATA% to the system profile path rather than individual user profile directories.Answer
- BSilent installation switches automatically suppress administrative privilege escalation, revoking access to user profile folders.
- CStandard Windows 11 client editions restrict background installer execution under the Local System service context.
- D64-bit operating systems prevent 32-bit installer processes from reading or resolving system environment variables.
Answer
Running the installer under the Local System account resolved %APPDATA% to the system profile path rather than individual user profile directories.
When automated deployment tools execute installers using the Local System account, system-level environment variables are used. The %APPDATA% variable expands to the system profile directory (C:\Windows\System32\config\systemprofile\AppData\Roaming) instead of the user profile path (C:\Users\<username>\AppData\Roaming). Consequently, configuration templates are placed in a folder standard users cannot access, leading to application launch failures.
Step-by-Step Solution
Key Concept
Impact of execution context (Local System vs. User Context) on environment variable resolution during application deployment