220-1102 Question 48
Single answerApplication and driver support/backward compatibilityA small accounting firm upgrades several PCs from Windows 10 to Windows 11. After the upgrade, a critical legacy invoicing application launches but immediately crashes when users try to print. The application vendor no longer supports the product, but the firm must keep using it temporarily. A technician confirms that Windows 11 has a working printer driver and printing works from other applications. What is the BEST next step to restore functionality with the least disruption?
- A
Configure the invoicing application's executable to run in Compatibility mode using settings for an earlier version of Windows
- B
Disable User Account Control (UAC) system-wide so the application can access the printer directly
- C
Replace the Windows 11 printer driver with a generic/text-only driver for all users
- D
Boot the PCs into Safe Mode whenever users need to print invoices
Show answer and explanation
Correct answer: A
Explanation
The best answer is to run the legacy invoicing application in Compatibility mode. In A+ Core 2 terms, backward compatibility troubleshooting should begin with the least disruptive, most targeted fix. Because the printer works from other programs, the problem is likely application compatibility rather than a hardware or driver failure. Microsoft best practices for older applications on newer Windows versions include using Compatibility mode, testing Run this program as an administrator only when appropriate, and considering virtualization or a supported replacement if compatibility settings do not work. Disabling security controls or replacing a working driver are poor first choices because they create broader impact without evidence that they address the root cause.
- A. Correct.
Correct. When a legacy application works partially but fails after an OS upgrade, using the program's Compatibility mode is an appropriate first troubleshooting step. This is especially true when the issue appears tied to the application's interaction with the newer OS rather than a system-wide printer failure. In Windows, compatibility settings can emulate behaviors from earlier supported versions and may resolve crashes caused by older application assumptions.
- B. Incorrect.
Incorrect. Disabling UAC system-wide is not a best practice and does not specifically address an application compatibility issue. UAC is a security feature, and turning it off broadly increases risk while potentially failing to resolve the print crash. A more appropriate approach would be to test the application with compatibility settings or, if required, run only that application with elevated privileges.
- C. Incorrect.
Incorrect. The scenario states that printing works from other applications, which strongly suggests the installed printer driver is functional. Replacing it with a generic/text-only driver would likely reduce printer functionality and affect all users without directly addressing the legacy application's crash behavior.
- D. Incorrect.
Incorrect. Safe Mode is intended for troubleshooting and uses minimal drivers and services. It is not a practical operational solution for routine business printing and may actually limit printer functionality rather than improve compatibility with a legacy application.