220-1102 Question 288
Single answerApplication to OS compatibilityA small accounting firm upgrades several desktops from Windows 10 to Windows 11. After the upgrade, a critical legacy invoicing application installs successfully but closes immediately when users launch it. The software vendor is no longer in business, and the application previously worked on Windows 10. You confirm the PCs meet Windows 11 hardware requirements and other modern applications run normally. Which action should the technician try FIRST to restore the application’s functionality while keeping the systems on Windows 11?
- A
Run the application using Program Compatibility settings for an earlier version of Windows
- B
Enable BitLocker on the system drive to improve application trust and startup behavior
- C
Reformat the computers and install a 32-bit edition of Windows 11
- D
Disable User Account Control permanently so the application can access protected system areas
- E
Upgrade the PCs to Windows 11 Pro so Hyper-V can emulate the older operating system automatically
Show answer and explanation
Correct answer: A
Explanation
For application-to-OS compatibility problems, the best first action is to try built-in compatibility tools before making major system changes. In Windows, this typically means using the application's Properties dialog under Compatibility or running the Program Compatibility Troubleshooter. These tools are designed specifically for older software that was written for previous Windows versions and may expect different APIs, privilege behavior, or display settings. This approach is low risk, fast to test, and consistent with CompTIA A+ Core 2 expectations for practical troubleshooting. Microsoft documents the use of compatibility mode and compatibility troubleshooting for legacy applications on modern Windows versions. If compatibility settings do not work, next steps might include checking for updated application versions, required runtimes such as .NET or Visual C++ redistributables, or isolating the application in a properly licensed virtual machine.
- A. Correct.
Correct. When a legacy application worked on an earlier Windows version but fails after an OS upgrade, the first low-impact troubleshooting step is to use Program Compatibility settings or the Program Compatibility Troubleshooter. This can run the app with compatibility settings such as an earlier Windows version mode, reduced color settings when applicable, or elevated privileges if required. This aligns with standard A+ troubleshooting and Microsoft best practices for older applications on newer Windows versions.
- B. Incorrect.
Incorrect. BitLocker is a disk encryption feature used to protect data at rest. It does not improve application compatibility or resolve issues where a legacy program closes immediately after launch. A candidate might choose this if they confuse security trust with application execution behavior.
- C. Incorrect.
Incorrect. Windows 11 does not have a 32-bit edition for PCs. In addition, reinstalling the operating system is not an appropriate first step when a targeted compatibility option is available. This distractor reflects a common misconception that older applications mainly fail because of 64-bit Windows, when many issues are actually resolved with compatibility settings or updated runtimes.
- D. Incorrect.
Incorrect. Permanently disabling User Account Control is not a recommended fix and creates unnecessary security risk. While some older applications may require administrative privileges, the proper first step is to use compatibility settings such as 'Run this program as an administrator' for that specific app rather than weakening security for the whole system.
- E. Incorrect.
Incorrect. Windows 11 Pro includes Hyper-V, but Hyper-V does not automatically emulate an older operating system for a legacy application. A virtual machine could be a later workaround if compatibility mode fails and licensing permits, but it is not the first step, and Hyper-V alone does not transparently fix application-to-OS compatibility issues.