Sometimes when installing software, I get an error during the installation of either the .Net framework or the Visual C Runtimes. This error, Error 1934. An error occurred during the instllation of assembly … will prevent the installation from being successfull, furthurmore after many hours of searching, many of the fixes listed around the web do not work.
To succsesfully allow the software installation to complete, a registry edit must be made. So go an open up Regedit and navigate to the following key: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control double-click on the RegistrySizeLimit and edit the DWORD value. In Hexadecimal enter FFFFFFFF or alternatively enter 4294967295 as the decimal value.
Once the registry change is done, restart the machine and then you can start the setup again that was causing you the issues earlier.
An optional set you can do once you have restarted the machine is to open up a command prompt window and type in the following command: SFC /SCANNOW this begins a windows file integrity checker ensuring that all windows system files are genuine and have not been edited or replaced, if you are running Windows XP you will need your installation CD to complete the scan.
Just about every encounter I’ve had with this error the RegistrySizeLimit has fixed the issue.
Thank you alot
Error 1935 appears while installing .NET framework, but i fixed it after taking help from this post. I fixed the error i faced.
by registering windows installer this error can also be fixed.
Not sure I understand what you mean. Windows Installer is built into the OS so there is no need to really register components (I have never come across anything recommending this).
I was installing SQL and this showed: an error occurred during installation of essembly ‘MicroSoft’ .server.diagnostics.STrace,Fileversion=”10.50.1600.1″,version=”10.0.0.00000″,culture=”neutral”,publickeytoken=”8984DCD8080CC91″,processorArchitecture=”MSIL”
Hi Celestin, see the following Microsoft KB Article which may help.
http://support.microsoft.com/kb/2688946
could not find the registry value specified in the solution
Hi jassani, you can just create the registry entry if it doesn’t exist.