How to Fix Error 1935 During Software Installation

If an Office installer stops with “Error 1935. An error occurred during the installation of assembly component,” the setup usually rolls back before the app is ready. The message can appear with Microsoft Office, older MSI packages, Visual C++ runtimes, or software that depends on .NET Framework.

This guide starts with the safest checks, then moves to Windows component repair and dependency troubleshooting. If you need to keep working while the Microsoft installer is being repaired, the final section shows a separate WPS Office option.

Why Error 1935 appears

Error 1935 is a Windows Installer assembly failure, not a single diagnosis. Common triggers include damaged or disabled .NET Framework components, a Windows Installer transaction left behind by an interrupted setup, security software blocking writes to protected folders, or damaged Windows system files.

How to Fix Error 1935 During Software Installation

Error 1935: Check the installer and restart Windows

Start with the error details instead of changing the registry. Note the assembly name, HRESULT, Windows version, and the application you were installing. These details can point to a missing runtime, pending update, damaged component store, or permissions problem.

1. Close the installer and any other setup programs.

2. Restart Windows to finish pending updates and release locked installer resources.

3. Download the installer again from the software publisher, save it locally, and right-click it to choose Run as administrator.

4. Temporarily disconnect unnecessary external drives and close security tools only if your organization allows it.

Do not download random DLL files or delete the contents of the Windows Installer folder. Those shortcuts can create a second problem while leaving the original dependency issue unresolved.

Reset a stuck Windows installation transaction

If the installer repeatedly fails after an interrupted setup and the error points to transaction or assembly metadata, open Command Prompt (Admin) and run:

fsutil resource setautoreset true C:\

Restart Windows after the command completes, then retry the installer. This command tells the default Transactional Resource Manager to clean transactional metadata on the next mount; it is a targeted troubleshooting step, not a general registry reset. If the command returns an error, stop and check the exact message before changing system settings.

Error 1935 assembly component dialog

Error 1935: Update Windows and repair required components

Older installers often depend on Windows servicing components, .NET Framework, or Visual C++ runtime files. Install updates from Windows Settings first, then repair the dependency named in the installer log or error message.

1. Open Settings > Windows Update, install available updates, and restart the PC.

2. For a .NET-related message, use Microsoft’s official .NET Framework installation guidance and choose the version supported by the application.

3. For a Visual C++ message, use Microsoft’s latest supported Visual C++ Redistributable downloads. Match x86 or x64 to the application requirements.

4. Run the installer again from a local folder with administrator permissions.

Repair or re-enable .NET Framework

If the installer or its log points to .NET Framework, check the Windows feature before reinstalling anything:

1. Press Win + R, enter appwiz.cpl, and press Enter.

2. Select Turn Windows features on or off.

3. On supported Windows versions, enable .NET Framework 3.5 (includes .NET 2.0 and 3.0), select OK, and restart if Windows asks.

4. If the feature is already enabled, use Microsoft’s supported repair or installation guidance rather than repeatedly toggling it. On newer Windows 11 releases, .NET Framework 3.5 may require the version-specific standalone installer instead of Windows Features.

Check your Windows version with winver first. Microsoft notes that the availability of .NET Framework 3.5 through Windows Features depends on the Windows 11 release, so do not assume the same checkbox exists on every PC.

Do not install every available runtime blindly. The assembly name and the application’s documentation should determine which dependency you repair.

Error 1935 repair checklist workflow

Error 1935: Repair Windows system files with DISM and SFC

If updates and dependency repair do not help, Windows component servicing may be inconsistent. Microsoft’s Windows Installer message identifies Error 1935 as an assembly installation failure; the exact HRESULT and assembly name still matter, so treat DISM and SFC as system-repair steps rather than a guaranteed one-click fix.

1. Open Windows Terminal (Admin) or Command Prompt (Admin).

2. Run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to finish.

3. Run sfc /scannow after DISM completes.

4. Restart Windows, then retry the installer from a fresh local copy.

Keep the command window open until each scan reaches 100%. If either command reports that it cannot complete, save the result and check Windows Update or Microsoft support before attempting more advanced repairs.

DISM SFC Windows component repair

The Best Free Office Alternative: WPS Office

If Error 1935 is blocking an Office installation and you need to edit documents immediately, WPS Office offers a separate productivity suite with Writer, Spreadsheet, Presentation, and PDF tools. It does not repair Microsoft’s installer, but it can give you a practical workspace while you continue troubleshooting.

• Open and edit common document, spreadsheet, presentation, and PDF files.

• Keep the workflow in one lightweight office suite instead of waiting for the failed setup to finish.

• Review file compatibility and fonts before sharing documents with users on other office software.

For Microsoft Office-specific add-ins, macros, or enterprise deployment rules, keep following your organization’s approved Microsoft installation process. Use WPS Office as a separate productivity option, not as a claim that the underlying Error 1935 has been repaired.

WPS Office productivity suite interface

FAQs

Can Error 1935 happen when installing Microsoft Office?

Yes. It can appear when Office or another MSI package cannot install an assembly component. The component named in the message and the HRESULT help narrow the cause.

Will restarting Windows fix Error 1935?

Sometimes. A restart can finish pending servicing work or release installer resources. If the error returns, continue with Windows Update, component repair, and system checks.

Should I reinstall .NET Framework to fix Error 1935?

Only when the installer or event log points to .NET. Repair or update the supported .NET Framework version first, and avoid removing framework components blindly.

What do DISM and SFC do for Error 1935?

DISM repairs the Windows component store, while SFC checks protected system files. Run them from an elevated Terminal, restart Windows, and try the installer again.

Can I use WPS Office if Microsoft Office will not install?

Yes. WPS Office can provide Writer, Spreadsheet, Presentation, and PDF tools without requiring the failed Microsoft Office installation to complete.