220-1102 Question 595
Single answerApplication fails to installA technician is deploying a legacy inventory application to several Windows 11 Pro workstations. On one PC, the installer starts but immediately displays a message that the app is not supported on this version of Windows and then closes. The same installation media works on an older Windows 10 system. The user has local admin rights, enough disk space, and no antivirus alerts are present. Which action should the technician take FIRST to get the application installed on the Windows 11 PC?
- A
Run the installer in Compatibility Mode using settings for an earlier version of Windows
- B
Disable User Account Control and run the installer again
- C
Convert the workstation from NTFS to FAT32 so the installer can write older file types
- D
Boot into Safe Mode with Networking and launch the installer there
Show answer and explanation
Correct answer: A
Explanation
The key clue is the explicit message that the application is not supported on the current version of Windows, while the same media works on an older Windows 10 system. That strongly indicates an operating system compatibility issue rather than permissions, storage, malware prevention, or installer corruption. On A+ Core 2, a technician should recognize Compatibility Mode as an appropriate first troubleshooting step for legacy applications that fail to install or run on newer versions of Windows. Microsoft documents compatibility settings and the Program Compatibility Troubleshooter as supported methods for older applications. Disabling security controls such as UAC should not be the initial response unless there is clear evidence of elevation-related failure. Likewise, changing file systems or using Safe Mode does not directly resolve an OS version support check built into the installer.
- A. Correct.
Correct. When an older application installer reports that the operating system version is unsupported, the most appropriate first step is to use Compatibility Mode. Windows can apply settings that help older installers and applications run as if they were on an earlier supported version of Windows. This is a common and supported troubleshooting step for legacy software that fails due to OS version checks.
- B. Incorrect.
Incorrect. User Account Control prompts for elevation and helps protect the system from unauthorized changes. In this scenario, the user already has local admin rights, and there is no indication that the install is failing because of permissions or blocked elevation. Disabling UAC is not a best-practice first step and introduces unnecessary security risk.
- C. Incorrect.
Incorrect. Windows 11 requires NTFS for normal operation in typical enterprise and business deployments, and converting to FAT32 would not address an application compatibility message. FAT32 also has significant file size and security limitations. This distractor reflects a misunderstanding between file system issues and application OS compatibility issues.
- D. Incorrect.
Incorrect. Safe Mode is useful for isolating conflicts from startup items, drivers, or third-party services. However, the error specifically states that the application is not supported on this version of Windows, which points to a compatibility problem rather than an environmental conflict. In addition, many installers and Windows Installer services may not run normally in Safe Mode.