220-1102 Software Troubleshooting Practice Question
A technician is trying to run a legacy 16-bit accounting application on a 64-bit version of Windows 10 Pro. The application fails to start with a 'This app can't run on your PC' error. The application is critical and there is no 64-bit version available. Which of the following is the BEST solution to allow this application to run?
⚠ Common exam trap
A common mix-up: candidates assume compatibility modes or the Program Compatibility Troubleshooter can fix any legacy application issue, but they fail to recognize that 64-bit Windows fundamentally cannot execute 16-bit code without a full 32-bit OS environment.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Install the application in a virtual machine running a 32-bit version of Windows.
The 16-bit accounting application cannot run directly on a 64-bit version of Windows 10 Pro because 64-bit Windows does not include the Windows on Windows (WOW) layer for 16-bit applications (NTVDM is removed). Installing the application in a virtual machine running a 32-bit version of Windows provides a complete 32-bit environment that includes the NTVDM subsystem, allowing the 16-bit application to execute properly without compatibility issues.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Run the application in Windows 7 compatibility mode.
Why it's wrong here
Windows 7 compatibility mode is a user-mode shim that substitutes OS version information and redirects specific APIs to mimic Windows 7's behavior; it has no effect on the CPU's execution mode or the binary format of the application. 64-bit Windows can only run PE32+ (64-bit) and PE32 (32-bit) executables, whereas a 16-bit NE-format program requires a 16-bit execution environment that the kernel simply does not provide to user-mode shims. As a result, compatibility mode neither loads nor executes the legacy accounting app.
- ✗
Enable NTVDM (NT Virtual DOS Machine) in Windows Features.
Why it's wrong here
NTVDM was a 32-bit Windows component that simulated an Intel 8086 environment to run MS-DOS and 16-bit Windows applications, but it was never ported to 64-bit editions because it relies on physical memory addressing and segment/offset tricks that conflict with the x86-64 long mode. In 64-bit Windows, the 'Windows Features' dialog does not list NTVDM, and even attempting to force-enable it via DISM fails because no NTVDM binaries are included in the installation media. Enabling NTVDM is therefore not a valid fix on a 64-bit OS.
- ✓
Install the application in a virtual machine running a 32-bit version of Windows.
Why this is correct
Installing the accounting application in a virtual machine running 32-bit Windows is the correct solution because the guest OS contains its own 32-bit kernel and NTVDM/WOW subsystem, which can execute 16-bit code natively. The hypervisor presents a standardized CPU to the guest, so the guest operates in 32-bit mode and allows the legacy application to run as if on a native 32-bit PC. This approach is theoretically sound and practically supported, as modern hypervisors can efficiently virtualize 32-bit environments without affecting the host OS.
- ✗
Use the Program Compatibility Troubleshooter to detect and apply fixes.
Why it's wrong here
The Program Compatibility Troubleshooter is an interactive wizard that collects diagnostic data and applies fixes such as forcing windowed mode, setting DPI compatibility, or running with administrator privileges for valid Windows executables. However, it operates entirely in the 64-bit user-mode compatibility framework and cannot interpret or launch a 16-bit executable because the Windows loader rejects NE-format binaries on 64-bit systems before any compatibility shim is invoked. Thus, the troubleshooter may help with 32-bit app quirks but provides no mechanism for 16-bit support.
Go deeper
Related to this question
Learn chapter
Troubleshoot: Application Crashes and Hangs
Key term
Windows 10
Windows 10 is a personal computer operating system developed by Microsoft that combines the familiarity of Windows 7 with the modern features of Windows 8, designed to run on a wide range of devices from desktops to tablets.
Key term
Windows
Windows is a family of operating systems developed by Microsoft that manages computer hardware and software, providing a graphical user interface for users to interact with their devices.
About these practice questions
One of 925 original 220-1102 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 220-1102 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 220-1102 exam.