220-1102 Software Troubleshooting Practice Question
A user reports that a 64-bit application fails to launch on Windows 10 Pro with the error: 'The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.' The technician has already reinstalled the application and verified that all required Visual C++ Redistributable packages are installed. Which step should the technician take NEXT to identify the specific cause of the error?
⚠ Common exam trap
The trap here is that candidates may jump to checking the Application event log (Option D) because the error message mentions it, but the question specifically asks for the next step to identify the specific cause, and sxstrace.exe is the dedicated tool for SxS errors, providing far more detail than the event log.
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
✓
Use sxstrace.exe to trace the application startup and analyze the output log
The error message explicitly directs the user to use sxstrace.exe for detailed diagnostics. Since the technician has already reinstalled the application and verified Visual C++ Redistributables, the next logical step is to run sxstrace.exe to capture the side-by-side (SxS) assembly activation failure. This tool generates a detailed log showing which specific assembly version or dependency is missing or mismatched, enabling precise remediation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use sxstrace.exe to trace the application startup and analyze the output log
Why this is correct
The sxstrace.exe utility is the purpose-built tool for diagnosing Windows Side-by-Side (SxS) activation failures. When a 64-bit application fails to launch, sxstrace captures the activation context by enabling tracing, then generating a detailed log in .log/.txt format that pinpoints which assembly, manifest, or dependency could not be resolved. Unlike generic error logs, this output shows the exact error code (such as 0x800736B1) and the missing assembly identity, allowing a precise fix like installing the correct Visual C++ Redistributable. This makes it the definitive first step for this error.
- ✗
Reinstall Windows 10 Pro from scratch
Why it's wrong here
Reinstalling Windows 10 Pro from scratch is an extreme measure that wipes user data, applications, and system settings, requiring hours of reconfiguration and potential data loss. It may only help if the WinSxS component store itself is severely corrupted, but even then a repair upgrade or DISM /RestoreHealth is less disruptive. Also, if the underlying cause is a missing assembly dependency that belongs to a third-party runtime (e.g., a specific VC++ Redistributable), a fresh OS installation will not include that dependency, so the application will still fail. Thus, it is a last-resort action, not a targeted troubleshooting step for an SxS error.
- ✗
Edit the registry to manually add missing registry keys for the application
Why it's wrong here
Editing the registry to manually add 'missing' keys is a dangerous, unguided action for SxS errors because the side-by-side store is managed by the Windows Component-Based Servicing (CBS) infrastructure, not by individual registry values. Activation errors arise from an invalid activation context, a corrupt manifest, or a missing assembly in the WinSxS folder; none of these are fixed by creating registry entries. Blindly adding keys can destabilize unrelated system components or force the application to load a different, incompatible assembly version. Without knowing which component is at fault—something only a diagnostic like sxstrace can reveal—registry edits are both ineffective and systemically risky.
- ✗
Check the Application event log for error entries
Why it's wrong here
The Application event log (via Event Viewer) records a side-by-side error, but the entry from the 'SideBySide' source or Application Error source often contains only a generic message and a nonspecific HRESULT. It does not enumerate the chain of dependent assemblies or identify whether the missing component is a runtime DLL, a manifest mismatch, or a failed Windows update repair. This lack of granularity means the event log serves only as a confirmation that an SxS failure occurred, not as a tool for determining which assembly to repair. Therefore, it should be used to locate the error, while sxstrace is required to obtain the specific resolution path.
Go deeper
Related to this question
Learn chapter
VPN Client Configuration
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.
Key term
Event
An event is any identifiable occurrence or action in a computer system, network, or application that can be logged, monitored, or analyzed for security or operational purposes.
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.