Problem installing Microsoft .net framework?

Question

Problem installing Microsoft .net framework?

Answer 1

Error 0x80131702 when installing .Net framework 2.0 Redist



The other day I encounter a problem when installing .Net framework 2.0 redist. It is a fresh install on a clean Windows XPSP2 machine.



During the install, setup pops up a dialog says LoadLibraryShim failed to locate fusion.dll, hr=0x80131702.



From CorError.h (in you .Net framework SDK include directory):



#define CLR_E_SHIM_INSTALLROOT EMAKEHR(0x1702) // Install root is not defined



The error means mscoree cannot find where the installroot is.



InstallRoot is a registry value of type REG_SZ in HKLM\Software\Microsoft\.NetFramework. It usually points to "%windir%\Microsoft.Net\Framework" in x86 and "%windir%\Microsoft.Net\Framework64" in x64/ia64 (replace %windir% with your real Windows directory.)



After I added the InstallRoot registry, the setup can be resumed and finished successfully.

Answer 2

I presume you have XP, where this is usually happening. This is an awful and known problem and the folks at M$ wont do much to remedy this now, as you can imagine. So, the fastest solution to it is - regrettably - somewhat drastic: reinstall Windows.



Short reason: .NET requires its installation to be in order of the numbers. If you skip one, you're screw... er, doomed. However, .NET is not built to be uninstalled (though there are tools for this).



Advice:



1.) try to remove all .NET updates/installations by way of Add/Remove programs. If that works, reinstall in correct order. This may sometimes due the trick - often it doesn't. It really depends on what exactly you are missing. This is also somewhat time consuming.



2.) If you continue to have the error, you have two options: continue to work with Windows, as most programs wont be affected and you can likely use them as if nothing happened. Adjust Automatic Updates to ignore .NET



or - sniff -



reinstall XP. Then, be sure to install .NET in the correct order. Automatic Updates may not prompt you to do that and so you'll have to *carefully* ensure that it happens *manually*. So, check each update, in/exclude the right things only.



Don't waste too much time trying to fix the error, though. I did and, to no avail. Just backup your data and do a clean install.



Best of luck!

Answer 3

I think it's trouble of your Microsoft.net.