Courseiva
Software Troubleshooting →mediumMultiple Choice

220-1102 Software Troubleshooting Practice Question

A technician is attempting to install a legacy Windows 7 application on a Windows 10 Pro workstation. The installer fails with the error 'Error 1935. An error occurred during the installation of assembly component.' The technician has already run System File Checker (SFC) and Deployment Image Servicing and Management (DISM), both reporting no corruption. Which step should the technician take NEXT?

⚠ Common exam trap

A common mix-up: candidates confuse assembly component errors with missing Visual C++ redistributables, but the specific 'Error 1935' and 'assembly component' language directly points to .NET Framework issues, not C++ runtime libraries.

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

✓

Enable the .NET Framework 3.5 feature in Windows Features

Error 1935 during installation of a legacy Windows 7 application on Windows 10 typically indicates a missing or corrupted .NET Framework 3.5 component. The .NET Framework 3.5 includes .NET 2.0 and 3.0, which many older applications require. Since SFC and DISM reported no corruption, the next step is to enable the .NET Framework 3.5 feature via Windows Features, which installs the necessary assemblies without needing a separate download.

Answer analysis

Option-by-option breakdown

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

  • ✓

    Enable the .NET Framework 3.5 feature in Windows Features

    Why this is correct

    Windows 10 does not include .NET Framework 3.5 by default; enabling it via Windows Features installs the .NET 2.0/3.0/3.5 assemblies that legacy applications need. Error 1935 occurs when the Windows Installer cannot write a required assembly to the Global Assembly Cache (GAC) or WinSxS store, typically because those .NET framework assemblies are absent. While SFC/DISM repair system files, they do not enable optional features, so this step is the direct fix that provides the missing dependencies for the installer to complete successfully.

  • ✗

    Install the latest Visual C++ Redistributable for Visual Studio

    Why it's wrong here

    Error 1935 is specifically an assembly installation error, not a missing DLL runtime issue. Visual C++ Redistributables ship msvcp and vcruntime libraries but do not include Microsoft .NET Framework assemblies, which are the components that fail to install in this scenario. If the problem were an absent C++ runtime, the installer would typically fail with a different error like 'The program can't start because msvcr120.dll is missing' or a side-by-side configuration error, not error 1935. Therefore, this option does not address the root cause of the legacy application's .NET Framework dependency.

  • ✗

    Run the installer in Windows 7 compatibility mode

    Why it's wrong here

    Compatibility mode alters the environment that the application sees, such as reporting a different Windows version or adjusting DPI/virtualization settings, but it cannot install missing platform components. Since error 1935 occurs during the installation process while the Windows Installer is registering .NET assemblies, the failure is a missing prerequisite, not an application-version compatibility issue. The application may eventually run in compatibility mode after installation, but the installer itself will still fail without .NET Framework 3.5 enabled. Thus, this step provides no mechanism to resolve the framework dependency.

  • ✗

    Create a new user account with administrative privileges and run the installer

    Why it's wrong here

    A lack of administrative rights typically results in an 'Access Denied' or UAC error, not error 1935, which indicates a failure to add an assembly to the system's component store. Creating a new admin account merely grants permissions and does not add any missing .NET Framework or Win32 assembly files. The technician already ran SFC/DISM, which means system file corruption has been ruled out; this is an optional-feature problem. Therefore, switching accounts would have no effect on the assembly installation failure.

About these practice questions

Courseiva writes every 220-1102 question from scratch — 925 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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.