Lỗi cài itunes an error occurred during installation of assembly năm 2024

Error 1935 is an issue that arises for some users when they try to install Windows 11/10 software with MSI packages. That error typically occurs during the installation process and throws up a message that says, “an error occurred during the installation of an assembly.” Consequently, the affected software does not install.

A lot of users have reported this issue to affect the installation of Microsoft Office applications. However, it also occurs for non-Microsoft software products. This is how you can fix error 1935 on a Windows 11/10 PC.

1. Run the Microsoft Program Installation Troubleshooter

First, start your troubleshooting with the Microsoft Program Install and Uninstaller troubleshooter. That troubleshooter primarily addresses registry issues that cause errors when installing and uninstalling software. This troubleshooter isn’t available within Settings, but you can download and run it as follows:

1. Open this Microsoft Program Install troubleshooter webpage.
2. Click that page’s Download troubleshooter button.
3. Bring up your browser’s Downloads page (Ctrl + J opens that tab in Chrome, Edge, and Firefox).
   
4. Then click the MicrosoftProgram_Install_and_Uninstall.meta (1).diagcab file shown in your web browser’s Downloads tab.
5. Click the troubleshooter’s Next button and select Installing.
   
6. Select the program you can’t install listed in the troubleshooter if it’s listed in the troubleshooter. If not, click on Not Listed > Next.
   

2. Set the MSI Installer File to Run in Compatibility Mode

If you’re trying to install older software, running its MSI package in compatibility mode might fix error 1935. Compatibility mode is a setting you can select to address program compatibility issues with the Windows platform. You can set an MSI installer file to run in compatibility mode like this:

1. Right-click Start, select File Explorer, and open the directory containing the MSI installation file.
2. Then right-click the MSI installation file and select Properties.
3. Click on Compatibility to view that tab’s settings.
4. Select the checkbox labeled Run this program in compatibility mode.
   
5. Choose the OS that was the latest Windows platform when the software was released. If you’re not sure, select Windows Vista.
6. Select Run this program as administrator while you’re in the Compatibility tab.
7. Press the properties window’s Apply and OK buttons.

3. Run a Transaction Support Repair Command

One of the most widely confirmed error 1935 resolutions is to run a transaction support repair command. Doing so can fix corrupted transaction log data in Windows. These are the steps for running a transaction support repair command:

1. Run Command Prompt as an administrator to bring up an elevated CMD app.
2. Input this fsutil command:

       fsutil resource setautoreset true C:  
     
   

   
3. Press Enter to execute the fsutil command.
4. Input exit in the Command Prompt and press Enter.
5. Then select the Windows Restart option.

4. Start or Restart the Windows Installer and Windows Module Installer Services

Windows Installer is a service that needs to be running to install software with MSI packages. So, check if that service is running and start it, if necessary, along with Windows Module Installer. To apply this potential solution, follow the instructions in method one of our article about starting services in Windows.

If you find both of those services are already running, you can select to restart them instead. To do so, right-click on Windows Installer and Windows Module Installer in the Services window and select Restart. Or you can select Stop and Start on the context menu.

5. Reregister MSI Service

If restarting the Windows Installer (MSI) service isn’t enough, then you might need to reregister it instead. Reregistering the msiexec.exe file can resolve Windows Installer issues causing error 1395. You can reregister MSI service in these quick steps:

1. Bring up the Command Prompt with elevated administrative permissions.
2. To unregister the service, input this command and hit Enter:

       msiexec /unreg  
     
   

   
3. Then input the following command and press Return to execute:

       msiexec /regserver  
     
   

   
4. Restart your laptop or desktop after reregistering Windows Installer.

6. Repair or Install Visual C++ Redistributable Packages

Error 1935 can occur if there are corrupted or missing Visual C++ Redistributable packages on your PC. To remedy that, try repairing or installing missing Visual C++ packages as follows:

1. Open the Programs and Features applet to view installed software.
2. Then select a Visual C++ package there and click Change.
   
3. Press the Repair button.
   
4. Repeat the previous two steps for all Visual C++ packages listed in the Control Panel.

If it looks like you might be missing some Visual C++ Redistributable packages, you can download and install the ones you need. Open this Microsoft Visual C++ Redistributable webpage. Click the X64 download links there for the Visual Studio 2015-2022, 2013, and 2010 packs.

Then go to the folder your browser usually downloads files in to find the Visual C++ Redistributable package. Double-click the Visual C++ Redistributable file to bring up a window from which you can select to install the runtime libraries. Then click the I agree box and Install.

There are also older, unsupported Visual C++ Redistributable packs available there. If the software you’re trying to install predates 2010, you might need to download and install an older Visual C++ package.

7. Repair .NET Framework

Error 1935 can sometimes occur because a required .NET Framework version is either missing or needs repairing. You can repair .NET Framework on Windows with the .NET Framework Repair Tool.

To obtain that tool, click Download on this Microsoft .NET Framework Tool page. Then bring up the repair tool by double-clicking the NetFxRepairTool.exe file. Select the I have read and accept the license terms option and click Next within the repair tool to apply fixes.

If .NET Framework 4 is missing on your PC, open this Microsoft .NET Framework download page. Click on the Download option there, and then open whatever folder includes the .NET Framework package. Double-click the dotNetFx40_Full_setup.exe file to open the setup window and select to install from there.

8. Disable Background Apps by Setting a Clean Boot

Clean-booting Windows will ensure there isn’t a background app or process causing error 1935. The clean booting troubleshooting method disables all third-party startup apps and services. We have a guide to clean booting that explains how you can apply this potential solution with Task Manager and MSConfig. When you’ve set the clean boot, restart Windows and try installing the affected software.

9. Erase the APPMODEL Key in the Registry

This is an official Microsoft resolution for fixing error 1935 when it occurs for the installation of MS Office software (2010-2016). As it involves deleting a registry key, consider backing up the registry as a precautionary measure. Then delete the AppModel key exactly as follows:

1. To find the Registry Editor app, press the Windows logo + S keys in combination and input regedit within the activated search box.
2. Then select the Registry Editor result displayed within the search tool.
3. Next, go to this key within the registry:

       HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\APPMODEL  
     
   

   
4. Right-click on the AppModel key and select Delete.
   
5. Then select Yes to proceed with deleting the key.
   
6. Exit Registry Editor, restart Windows, and try installing your affected software again.

Install and Utilize the Windows Software You Need

Error 1935 is an old Windows issue that’s hindered software installation for many users. However, many users have also resolved error 1935 by applying the potential solutions in this guide. So, it’s more than likely one of those potential fixes will get error 1935 resolved on your Windows 11/10 PC. Then you can install all the software packages you need.