220-1102 Software Troubleshooting Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Right-click the executable, Properties, Compatibility tab, check 'Run this program in compatibility mode for Windows 8'

  Why this is correct

  This is the correct approach because the Program Compatibility Troubleshooter only diagnoses and suggests compatibility settings; to make the fix permanent for future launches you must apply the same mode manually. Opening the executable's Properties and selecting the Compatibility tab writes a compatibility flag (specifically, a Windows 8 emulated version) into the registry, which the OS then uses every time that program starts. The check box 'Run this program in compatibility mode for Windows 8' tells Windows to provide the Windows 8 API shims and operating-system version to the application, resolving the 'this application...' error without affecting other programs.

• ✗

  Reinstall the application

  Why it's wrong here

  Reinstalling the application will not resolve this error because the incompatibility is not caused by corrupted files or an incomplete install—it stems from the application's expectation of an older Windows API set or version. Reinstalling simply copies the same incompatible binary onto the disk again and does not write any compatibility settings to the registry, so the program will fail in exactly the same way on the next launch. While reinstallation might fix a completely different class of error (like missing DLLs), it does nothing to address the need for a compatibility shim.

• ✗

  Create a shortcut with the /compat flag

  Why it's wrong here

  This option is not valid because Windows does not recognize a '/compat' flag for executable shortcuts; command-line switches are passed to the program, not interpreted by Windows as a compatibility directive. Even if you created a shortcut and appended '/compat' to the Target, the application would receive that string as an argument (likely causing a different runtime error) and Windows would still launch it in its native environment. The only supported ways to set compatibility are the GUI on the Compatibility tab, the registry, or Group Policy—no undocumented command-line switch exists.

• ✗

  Enable Windows Features for Application Compatibility

  Why it's wrong here

  Enabling the 'Application Compatibility' feature in Windows Features does not apply a compatibility mode to any specific program; it merely installs supporting infrastructure such as the Application Compatibility Toolkit and the compatibility engine. After enabling the feature, you still have to manually configure the individual executable through its Properties dialog or via registry entries, so this option is a prerequisite at most, not the actual fix. The error would persist exactly as before because no shim or version override has been assigned to the failing application.

Go deeper

Related to this question