How to Fix Sage 50 Error Code 1935?

Error 1935 is a known issue that occurs during Sage 50 installation. It arises when the installation of assembly components is unsuccessful. Pending Windows updates, antivirus issues, corrupted installation files, etc., are some of the reasons for this issue.

This installation error impacts daily business operations. It slows down payroll processing, reporting, and invoicing. In addition, it disrupts the recording of financial transactions and minimizes productivity. Prolonged downtime adversely impacts decision-making, client interactions, and business cash flow.

Here is the message that appears with this installation error:

“Error 1935: An error occurred during the installation of the assembly component.”

In this guide, complete information on Sage 50 error 1935 has been shared. Read on to learn about the causes and solutions to resolve this error swiftly and resume business productivity.

What are the Causes of Sage Error 1935?

Multiple factors trigger the Sage 50 error 1935. Among them, certain common reasons usually trigger this installation error.

Here is the list of the causes of Sage 50 Error 1935:

• Antivirus Problem- Security programs created to safeguard the system can often restrict Sage 50 installation. This accidental disruption can trigger Error 1935.
• Old Windows Operating System– With Windows XP, problems with the .NET structure can stop Sage 50 from installing systematically. This can trigger error 1935.
• .NET Framework Issues– On Windows XP, problems with the .NET Framework can stop Sage 50 from proper installation. This can lead to error 1935.
• Installation Files are corrupted– Corrupted or damaged installation files interrupt the setup procedure. This kind of corruption leads to error 1935.
• Active background applications– Programs actively running in the background can disrupt the Sage 50 installation. This often leads to error 1935.

Steps to Fix the Error Sage 50 1935

It is crucial to resolve this installation error in Sage 50 to resume business operations quickly. Here is the list of the quick and useful troubleshooting steps to resolve this issue:

1. Look for Windows Update

Often, the Sage error 1935 can be resolved using Windows updates. Ensuring the system is updated prevents compatibility problems with Sage 50.

Here are the steps to check for a Windows update:

1. Click the “Start” button available on the taskbar.
2. Open the Control Panel and head to the “Windows Updates” option.
3. Choose the “Change Settings” option present on the left side.
4. Open the drop-down menu in the “Important Updates” section.
5. Choose the “Never Check for Updates” option.
6. Click the “OK” button to save.
7. Head to the “Start” option and then click “Control Panel”.
8. Now, click the “Administrative Tools” option. 
9. Now, click the “Services” button.
10. Locate “Windows Update” in the list.
11. Click it twice and click the “Stop” button.
12. Now start with the Sage 50 installation.

2. Allow the Microsoft .NET Framework

Error 1935 often arises due to an old or deactivated .NET Framework. Allowing it resolves installation problems, mostly on older devices.

Here are the steps to enable the Microsoft .NET Framework:

1. Look for System errors- Check the operating system for issues prior to updating.
2. Update the .NET Framework- Update the .NET Framework to the most recent compatible version for Vista or later.
3. Install on XP again- Uninstall the .NET Framework 4.0. Now install again to resolve compatibility problems.

3. Install the Microsoft .NET Framework 4.6.1

Seamless Sage 50 installation 2024 is guaranteed by installing the current .NET Framework. Here are the steps to install the Microsoft .NET Framework 4.6.1:

1. Head to Microsoft.NET 4.6.1 to download.
2. Save manually or locate it in the Downloads folder.
3. Select a location and name it if requested. Now click the “Save” button.
4. Run the file and complete the on-screen guidelines.

4. Select all Background Applications

Background applications often disrupt proper Sage installations. Hence, shutting down such an application prevents issues like the 1935:

1. Look for third-party applications that have restricted the Sage 50 application.
2. Click the “Ctrl + Alt + Delete” keys together. This will open the Task Manager.
3. Deactivate Startup Programs:
   • Head to the “Startup” tab.
   • Right-click the conflicting programs.
   • Choose the “Disable” button.
4. Stop the Interfering Processes
   • Move to the “Details” tab.
   • Right-click on the interfering programs.
   • Choose the “End Task” option.

These solutions resolve Sage 50 installation issue 1935. Now, let’s learn about the steps for Windows 11 and 10.

How to Troubleshoot Sage Installation Error 1935 on Windows 10 and Windows 11?

Error 1935 arises often while installing Sage 50 on Windows 10 and 11. This issue restricts the setup and stops the correct installation.

Here are the solutions to resolve the error and finish the Sage 50 installation properly:

1. Repair the Microsoft Program Installation: Using the Install and Uninstall Troubleshooting from Microsoft often resolves the installation issues. It identifies the issues and fixes the problem automatically:
   • Head to the Microsoft Program Install Troubleshooter webpage.
   • Click the “Download Troubleshooter” option.
   • Open the downloaded file. It is generally named:
     • MicrosoftProgram_Install_and_Uninstall.diagcab
   • Start the troubleshooter. Now, click the “Next” button.
   • Now, choose the “Installing” option.
   • From the list, select the problematic program. 
   • Now, click the “Next” button.
2. Allow the Compatibility Mode for the MSI Installer File: Old MSI packages may not work for the latest Windows versions. Using them in compatibility mode helps to fix the installation error 1935.

Here are the steps to enable the compatibility mode for the MSI Installer File:

1. Open the “File Explorer”.
2. Head to the MSI file location.
3. Head to the “Compatibility” tab.
4. Now, check the option “Run this program in compatibility mode”.
5. Choose the Windows version the software was designed for (or Windows Vista).
6. In the same tab, tick the option “Run this program as administrator”.
7. Click the “Apply” button. Next, click the “OK” button.

See More: Sage 50 Connection Manager Error

3. Perform a Repair Command for Transaction Assistance: Fixing transaction support resolves standard installation problems. Here are the steps to execute a Repair command for transaction support.

1. Open the “Command Prompt” as Administrator.
2. Type fsutil resource setautoreset true C:
3. Now, click the “Enter” button.
4. Input “Exit”.
5. Now, click the “Enter” button.
6. Start Windows again.

4. Start or update Windows Installer and Windows Module Installer Services: Ensure that such services are running to avoid MSI installation issues. Here are the steps to start the Windows Installer services.

1. Open the “Services” option.
2. Now, tick the “Windows Installer” and “Windows Module Installer” options.
3. Next, right-click every service and choose the “Restart” button.
4. Now, choose the “Stop” option and then click the “Start” button to update the services.

5. Register the MSI Service again: Reregistering the Windows Installer fixes recurring installation issues. Here are the steps to register the MSI Service again.

1. As an Admin, open the “Command Prompt”.
2. Input “msiexec /unreg”.  
3. Now, click the “Enter” button.
4. Input “msiexec /regserver”.
5. Now, click the “Enter” button.
6. Reboot the system.

6. Fix or install Visual C++ Redistributable Packages: Missing or damaged Visual C++ packages trigger error 1935. Fix or install them to resolve the error using these steps.

To Fix Existing Packages:

1. Open the “Programs and Features” option.
2. Choose a Visual C++ package.
3. Now, click the “Change” option.
4. Click the “Repair” button.
5. Perform the same steps for all listed packages.

To install packages that are missing:

1. Head to the Microsoft Visual C++ Redistributable webpage.
2. Download the X64 versions for Visual Studio 2015-2022, 2013, and 2010.
3. Open the file downloaded and install it.
4. In case the software demands, install older packages.

Know More: Sage 50 Company File Not Valid Error

7. Remove Background App Interference via a Clean Boot: Preventing background applications from running stops issues from occurring during installation. Execute a clean boot to deactivate third-party startup apps and services.

8. Erase the APPMODEL Key from the Registry: Erasing the APPMODEL registry key fixes installation issues for specific Microsoft software. It is advisable to take a backup of the registry before proceeding.

Here are the steps to remove the APPMODEL key from the registry:

1. Click the “Windows + S” key. 
2. Now, input “Regedit” and open the “Registry Editor”.
3. Head to “HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\APPMODEL.”
4. Now, right-click “AppModel” and choose the “Delete” option.
5. Verify the deletion and close the editor.
6. Reboot the system and try the installation again.

Conclusion

Sage error 1935 can interrupt the installation of the software. Comprehending the causes and implementing the solutions can help to fix the issue. Implementing the solution steps mentioned in this guide guarantees future installations work seamlessly.

In case there is any query or doubt, feel free to call us. Talk to our Sage support team at +1-347-967-4079 at your convenience.

Frequently Asked Questions