Possible .NET Framework 3.5 installation failure caused by broken MSXML registration
The .NET Framework 3.5 can fail to install on a system where MSXML is not properly registered. There is a custom action that runs during .NET Framework 3.5 setup that tries to use some APIs in MSXML to modify some information in the web_mediumtrust.config file that is a part of the .NET Framework 2.0. In the cases that we've seen of this issue so far, one of the MSXML CLSID values was somehow unregistered on the system, and that causes this custom action to fail.
How to diagnose this issue from the .NET Framework 3.5 setup log file
This issue will cause the following information to be written to the verbose MSI log file for the .NET Framework 3.5 component (named %temp%\dd_net_framework35_MSI*.txt):
MSI (s) (58:94) [11:11:11:829]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI35C6.tmp, Entrypoint: ExecXmlConfig
MSI (s) (58:F0) [11:11:11:829]: Generating random cookie.
MSI (s) (58:F0) [11:11:11:829]: Created Custom Action Server with PID 4936 (0x1348).
MSI (s) (58:74) [11:11:11:860]: Running as a service.
MSI (s) (58:00) [11:11:11:860]: Hello, I'm your 32bit Elevated custom action server.
ExecXmlConfig: Error 0x80040154: failed to load XML file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_mediumtrust.config
MSI (s) (58!50) [11:11:11:954]: Product: Microsoft .NET Framework 3.5 -- Error 25541.Failed to open XML file C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_mediumtrust.config, system error: -2147221164
How to work around this issue
You can use one of the following options to work around this issue if you encounter it during .NET Framework 3.5 setup. Note that these workarounds are only useful for this exact error and HRESULT value. They will not help fix all possible .NET Framework 3.5 setup failures.
- Re-register msxml3.dll by running regsvr32 msxml3.dll
- Re-install MSXML3 by downloading and installing the package from https://www.microsoft.com/downloads/details.aspx?familyid=28494391-052b-42ff-9674-f752bdca9582
More details about the root cause of this issue
In the example log file above, the HRESULT value is 0x80040154, which means that a class is not registered. On systems where we have seen this error, the root MSXML CLSID is listed in the registry at the following location:
[HKEY_CLASSES_ROOT\Msxml2.DOMDocument\CLSID]
@="{F6D90F11-9C73-11D3-B32E-00C04F990BB4}"
However, the following sub-key for this CLSID was not present on this system:
[HKEY_CLASSES_ROOT\CLSID\{F6D90F11-9C73-11D3-B32E-00C04F990BB4}]
The suggested workarounds listed above will re-register this CLSID, which has fixed this issue in the cases we have seen of this error so far.
Comments
Anonymous
November 01, 2007
PingBack from http://msdnrss.thecoderblogs.com/2007/11/02/possible-net-framework-35-installation-failure-caused-by-broken-msxml-registration/Anonymous
November 01, 2007
.NET Framework 3.5 e MSXMLAnonymous
January 11, 2008
Thanks a lot! Been looking for the problem for a while. Unregistering and registering msxml3.dll fixed it. Regards, JoseAnonymous
January 17, 2008
Great!!!!! It works!!!! Thanks!!!!Anonymous
October 13, 2008
こんにちは！ フォーラム オペレーターの服部 清次です 皆さん、連休モードはもう抜けましたか？ 僕は今日からさっそく、 3 連休でスリープ モードに入っていた頭の中の OS を復帰させて、翻訳に励んでいます。Anonymous
March 06, 2010
Hi I am installinf vs2008 on windows 7 RTM and havinf the error 25541. I have tried the work arrounds but it remins the same error. Can you give any suggestion.Anonymous
March 06, 2010
Hi Jossy81 - I'm not sure if your error has the same root cause as this .NET Framework error. Can you please use the tool described at http://blogs.msdn.com/astebner/archive/2007/11/21/6458047.aspx to gather your VS 2008 setup log files, post the logs to a file server (such as http://skydrive.live.com) and then reply here with a link I can use to download the log files so I can take a look and see if I can figure anything out about the cause of this error?Anonymous
May 12, 2010
Hello Aaron, I am having the same problem as astebner. I have completed all the steps highlighted above, and still no success. I have loaded my logs to: http://cid-f412b5a647c8e0de.skydrive.live.com/browse.aspx/.Public?uc=1 Any assistance you could provide would be appreciated. Thanks! MichaelAnonymous
May 25, 2010
Hi Maas1701 – This is the exact error that I see in your logs: ExecXmlConfig: Error 0x8007006e: failed to load XML file: C:WINDOWSMicrosoft.NETFrameworkv2.0.50727CONFIGweb_mediumtrust.config The error code is different than the one described above in this blog post, so I’m not surprised that the workaround listed here didn’t work in this case. This error code 0x8007006e means “The system cannot open the device or file specified.” Can you check and see if this file exists on your system, and if so, if there are any settings on it that would prevent it from being opened (for example – is it marked as compressed or encrypted or something like that?)Anonymous
July 21, 2010
The comment has been removedAnonymous
July 21, 2010
Hi Paul - Error 1603 just means that setup failed, and there are many possible causes for that. This blog post describes only one of the possible causes. In order to diagnose this further, we'll need to look at your log files and see what the exact root cause of the failure is. Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to gather all of your log files, then post the file named %temp%vslogs.cab that this tool creates to a file server (such as http://skydrive.live.com), then reply back here with a link I can use to download your logs and take a further look?Anonymous
September 02, 2010
The comment has been removedAnonymous
September 02, 2010
Hi Rawaa - Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to gather all of your .NET Framework setup log files, then post the file named %temp%vslogs.cab that this tool creates on a file server (such as http://skydrive.live.com), then reply here and provide a link that I can use to download your log files and take a look?Anonymous
October 13, 2010
Reregistering the DLL fixed this issue for me. I was spending hours trying to fix it. Looking at the logs helped find the exact error message that was preventing it from installing. Thanks.Anonymous
January 14, 2011
I followed your directions above and have posted the vslogs.cab to the following link: cid-596dad0f029a45f8.skydrive.live.com/redir.aspx!596 Thanks in advance to any assistance you may be able to offer to me;-) Chris (I removed dot net framework 2.0 & attempted to reinstall before reading the directions to run the tool above)Anonymous
January 15, 2011
Hi Chris - The log files you posted show a different error than the one in this blog post. The .NET Framework 2.0 SP2 is failing, and here is the exact error: 01/15/11 01:01:02 DDSet_Error: Failed to install assembly 'C:WINDOWSMicrosoft.NETFrameworkv2.0.50727AspNetMMCExt.dll' because of system error: 0x80131107 For this 0x80131107 error, I typically recommend using the cleanup tool and the steps described at blogs.msdn.com/.../8108332.aspx to manually remove all versions of the .NET Framework that are installed on your computer, then attempt to re-install the .NET Framework 3.5 SP1 (which will install the .NET Framework 2.0 SP2 and 3.0 SP2 automatically behind the scenes).Anonymous
January 15, 2011
Hi astebner, Worked like a charm & for a relative newbie like myself I am so grateful for your help! 3.5 SP1 installed and I am checking for any needed updpates. Thanks again, ChrisAnonymous
May 08, 2011
The comment has been removedAnonymous
May 09, 2011
Hi Douglas - Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to gather all of your .NET Framework setup log files, post the file named %temp%vslogs.cab that this tool will create to a file server (such as http://skydrive.live.com), then reply here and provide a link that I can use to download your log files and take a look?Anonymous
May 09, 2011
Executei o arquivo, mas não acho o histórico de . Pode me fazer o favor de ensinar-me?Anonymous
May 09, 2011
Hi Douglas - I'm not sure I understand your question. Did you run the log collection tool? If so, you should be able to go to your %temp% directory and look for a file named vslogs.cab. That will contain all of your .NET Framework setup log files. Once you find that, please upload it to a file server and post a link so I can download it and look at your log files in more detail.Anonymous
May 09, 2011
Desculpe-me não prestei muito atenção, acabei de ler como chegava a esse arquivo. Espero que com isso consiga solucionar o erro. Aqui está o link do arquivo www.4shared.com/.../vslogs.htmlAnonymous
May 10, 2011
Hi Douglas - According to your log files, this is the error that is causing .NET Framework setup to fail on your computer: MSI (s) (48:F8) [11:49:36:171]: Produto: Microsoft .NET Framework 2.0 -- Error 1402.Não foi possível abrir a chave: UNKNOWNInstallerProductsD6461317C3DC4F04799BDCE9E42626FESourceListMedia. Erro do sistema 5. Verifique se você tem acesso suficiente a essa chave ou entre em contato com a equipe de suporte. For this type of access denied error, I'd suggest trying to use the suggestions listed at blogs.msdn.com/.../solving-setup-errors-by-using-the-subinacl-tool-to-repair-file-and-registry-permissions.aspx to repair the file/folder/registry permissions on your computer and see if that helps unblock the .NET Framework installation process.Anonymous
May 10, 2011
Fighting, managed to install only the 3.0, but the one to do gain, fought anyway. I will try to do this so I spoke.Anonymous
January 07, 2012
The comment has been removedAnonymous
January 07, 2012
Hi Dave W - This is the exact error message from your log files that is causing the installation of the .NET Framework 2.0 SP2 to fail on your computer: Error 1312.Cannot create the directory 'C:WINDOWSInstaller$PatchCache$'. A file with this name already exists. Please rename or remove the file and click retry, or click Cancel to exit. Setup is trying to create a directory named C:WINDOWSInstaller$PatchCache$, but it looks like there is already a file named $PatchCache$ in the C:WINDOWSInstaller directory, and setup cannot create a directory with the same name as a file that is already there. Can you please look for a file with that name and rename it, then try to install again and see if that helps solve this problem?Anonymous
January 09, 2012
Fantastic. That did the trick. All of the .NET versions, their SPs, and updates have now installed. Thank you. I was hoping this would also solve my XP SP3 installation failure (it didn't). Any clue in those log files on why XP SP3 is failing?Anonymous
January 10, 2012
Hi Dave W - I'm glad that you were able to solve this .NET Framework installation issue by using this workaround. The .cab file that you posted only contains log files for the .NET Framework and Visual Studio installers, so there isn't any information there about why Windows XP SP3 installation is failing. There is some information in the knowledge base article at support.microsoft.com/.../949388 that might help you narrow down the XP SP3 installation issue.Anonymous
January 15, 2012
Hi, Aaron. You're doing an amazing service here; thank you. I've spent literally the whole day trying to install .NET 3.5 so that I can play a game that uses it. I've gone through a good chunk of your (excellent) back catalogue trying fixes, but none of them have worked so far. It seems to keep choking on .NET 2.0, which I've tried to install and reinstall numerous times today. I've also disabled/enabled IIS, messed around with permissions, turned UAC off and on, and so on. I couldn't do the fix in this specific post because your link to MSXML 3 just takes me to the Microsoft landing page. I did a search on MSXML 3 and found numerous files; I was too scared to choose between 3.0, 3.1, and various SPs so I didn't download any of them. I took the liberty of uploading a log collection to this site, if you would be so kind as to look at it: skydrive.live.com/redir.aspx The logs might not be complete since one of the steps I took was cleaning out the registry with CCleaner, but it does have my most recent .NET 3.5 attempt in it so I hope it will help you. Thanks in advance.Anonymous
January 15, 2012
Hi Hapax - I'm sorry for the hassles that this issue is causing for you. I'm a little confused by what I'm seeing in your log files. You have a log for the .NET Framework 2.0 SP1, and it is failing with the following error: Setup has determined that this version of .NET Framework is part of your operating system and cannot be installed or uninstalled with this setup. Use Windows Update for all future updates to .NET Framework. Setup will now exit. The .NET Framework 2.0 SP1 is included with the .NET Framework 3.5 RTM. What I'd suggest that you do is try to install the .NET Framework 3.5 SP1 instead. You can get it at www.microsoft.com/.../details.aspx. It will install the .NET Framework 2.0 SP2 and 3.0 SP2 for you behind the scenes. Hopefully this helps resolve these issues. If the .NET Framework 3.5 SP1 fails to install as well, can you please re-run the log collection tool and upload a new set of log files so I can take another look?Anonymous
January 16, 2012
Thanks for getting back to me so quickly (on a weekend, too). Alas, the installation procedure failed again. :( I put the new logs in the same directory (the old ones have been renamed .old): skydrive.live.com/redir.aspx I have a terrible fear that you'll see exactly the same error messages again, but hope springs eternal!Anonymous
January 17, 2012
The comment has been removedAnonymous
January 17, 2012
It worked! It worked it worked it worked! I entered that registry key by hand and the error messages stopped! The game is running and all is well! YOU ARE MY HERO. Thank you so much!Anonymous
January 17, 2012
Hi Hapax - I'm really glad to hear that this worked! I just wish I could explain how that registry value went missing from your computer in the first place.Anonymous
March 28, 2012
I got the same problem while install Microsoft .NET Framework 3.5, is there anybody can help me thanks!Anonymous
March 28, 2012
Hi Kevin - I assume you already tried the workarounds in this blog post and they didn't help - correct? If so, can you please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your setup log files, post the file named %temp%vslogs.cab that this tool will create to a file server (such as http://skydrive.live.com), and then reply back here and provide a link that I can use to download your log files and take a closer look?Anonymous
May 14, 2012
Hi I have also the same problem on a 2008 Server. Can no Install .NET Framework 3.5. I read this Thread but its still not possible to Install the Version 3.5. Here ist the vslogs.cab... maybe is anybody here who can help me or tell me what is my problem... skydrive.live.com Thanks.Anonymous
May 14, 2012
Can anyone please address Rawaa's issue ?Anonymous
May 15, 2012
Hi Himanshu - I never heard back from Rawaa, and I need to look at the log files in order to be able to figure out what is causing setup to fail. If you are running into a similar issue, can you please use the steps that I posted above to collect and post your log files so I can take a closer look?Anonymous
May 15, 2012
Hi Bluzuk - Here is the error that is causing setup to fail on your computer: DDSet_Error: CFileHelper::CheckIsWriteable GetFileAttributes failed for file C:WindowsMicrosoft.NETFramework64v2.0.50727configmachine.config. GetLastError returned 0x2 DDSet_Error: CFileHelper::CheckIsWriteable C:WindowsMicrosoft.NETFramework64v2.0.50727configmachine.config File not found Here are the steps that I'd suggest that you try in this scenario:
- Make a copy of the file C:WindowsMicrosoft.NETFramework64v2.0.50727configmachine.config.default
- Rename the copy from step 1 to machine.config
- Reboot your computer
- Try again to install the .NET Framework 3.5 SP1
Anonymous
May 15, 2012
Hi Aaron - Thank you for the Feedback! I Will try this next Monday and give a Feedback.Anonymous
May 20, 2012
Hi Aaron - I tried your Tips and after reboot reinstalled .NET Framework but I became the same Error. Maybe you have another idea?Anonymous
May 20, 2012
Hi Bluzuk - Can you please collect a new set of log files and post them on your SkyDrive page so I can take a look and see if setup is failing for the same reason as it was last time?Anonymous
May 21, 2012
Hi Aaron - of course. here are the new log files: Hi Aaron skydrive.live.com Thank you!Anonymous
May 22, 2012
Hi Bluzuk - I see the same error as before in your most recent log files: DDSet_Error: CFileHelper::CheckIsWriteable C:WindowsMicrosoft.NETFramework64v2.0.50727configmachine.config File not found Can you please double-check that you have the file named C:WindowsMicrosoft.NETFramework64v2.0.50727configmachine.config on your computer? The steps I sent you previously should have re-created that file, but maybe it got deleted again or maybe you accidentally modified the other copy of machine.config that is located at C:WindowsMicrosoft.NETFramework instead of the one at C:WindowsMicrosoft.NETFramework64?Anonymous
June 20, 2012
Hi Aaron - Thank you again for your Message. Yesterday i had time to fix the Problem. Now is everything working. ThanksAnonymous
July 17, 2012
The comment has been removedAnonymous
July 17, 2012
The comment has been removedAnonymous
July 17, 2012
Wrong link, Here is the correct link with logs: skydrive.live.com/redirAnonymous
July 18, 2012
The comment has been removedAnonymous
July 18, 2012
Hi Svetlin - The error you described sounds similar to the one I wrote about at blogs.msdn.com/.../8342307.aspx. The first thing I'd suggest is to try to install the .NET Framework 3.5 SP1 instead of 3.5 if you haven't yet. The .NET Framework 3.5 SP1 includes some setup bug fixes that can help avoid the type of error that you're seeing in some cases. If that doesn't help, then I'd suggest following the troubleshooting steps listed in the blog post at blogs.msdn.com/.../8342307.aspx. If that doesn't help either, then please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your setup log files, upload the file named %temp%vslogs.cab that this tool will create to a file server (such as http://skydrive.live.com), and then reply back here and provide a link that I can use to download your log files and take a closer look.Anonymous
July 28, 2012
Hi Aaron could you please help me ? Here are the error logs : skydrive.live.comAnonymous
July 31, 2012
Hi Rayane1812 - This is the exact error that I see that is causing the .NET Framework 3.5 SP1 to fail on your computer: Error 1935.Une erreur s’est produite pendant l’installation de l’assembly « System.ServiceModel.Web,version="3.5.0.0",publicKeyToken="31bf3856ad364e35",processorArchitecture="MSIL",fileVersion="3.5.594.1152",culture="neutral" ». Pour plus d’informations, référez-vous à Aide et support. HRESULT : 0x8002802F. interface de l’assembly : , fonction : CreateAssemblyCache, composant : {8AAC775A-59B0-4591-A44C-4FCF2BA3184D} Error code 0x8002802F usually means that there is something wrong with the file mscoree.dll or with some of the .NET Framework 2.0 registry keys on your computer. Here are the steps that I'd suggest that you try to see if they will resolve this issue:
- Try to manually check for the registry keys listed in the .NET Framework 2.0 section of the blog post at blogs.msdn.com/.../3260076.aspx and add them if they are missing
- Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx
- Try to run the System Update Readiness Tool from support.microsoft.com/.../947821 Hopefully one of these suggestions will help in this scenario.
Anonymous
August 07, 2012
Hi Aaron, Thanks it worked for 1.1 and 2.0 but I still can't get to install 3.5, I suspect that 3.0 is broken (I tried all steps above). Also I can't use "Activate/Desactivate Windows Features" on .net framework 3.0, because after an hour trying to activate it, it says that it couldn't activate it but still asks me to reboot computer Here are the updated logs : skydrive.live.comAnonymous
August 21, 2012
Hi all, I had a problem with my msxml3.dll file. Registering it would not work at all so I followed the steps on one of Aaron's other posts at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. It turns out the my dll file was corrupt and Aaron's solution fixed the problem. After that I was able to register the dll file. Hope this works for you if you have the same problem! Thanks again Aaron!Anonymous
August 21, 2012
Hi Rayane1812 - Here are the steps I usually suggest for problems related to installing from the Windows Features control panel:
- Install the latest Windows service pack if you haven't yet.
- Try to run the System Update Readiness Tool from support.microsoft.com/.../947821.
- Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.
- Anonymous
November 06, 2012
The comment has been removed - Anonymous
November 06, 2012
Hi a2pac30 - From your logs, it looks like you've got Windows 7 on your computer. Windows 7 includes the .NET Framework 2.0, 3.0 and 3.5 as a part of the OS, and you cannot install it using the redistributable installer. Instead, you need to go to the Windows Features control panel and enable it there. If you tried to use the Windows Features control panel and are seeing errors, then I usually suggest the following options:
- Install the latest Windows service pack if you haven't yet.
- Try to run the System Update Readiness Tool from support.microsoft.com/.../947821.
- Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.
Anonymous
November 07, 2012
many thanks i will try your recomendations i will let you know my resultsAnonymous
November 08, 2012
hello again; many, many thanks Aaron stebner for you recomendations i did the 3 esteps recomendations the sp1 i had it already installed i installed de www.microsoft.com/.../confirmation.aspx as you told me and i finally run sfc /scannow and got this Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:> i will install now sql and visual thanksAnonymous
February 27, 2013
OMG, IT REALLY WORKED, THANK YOU TOO MUCH <3 I love such helpful guys ;)Anonymous
August 23, 2013
Hello Aaron. I try to install visual studio 2010 and ... Please help me. skydrive.live.com/redirAnonymous
September 02, 2013
Hi Ciupacau - I took a look at your log files, and I don't see any errors in the Visual Studio setup logs. What is the exact error that you are seeing when you try to install VS 2010 on your computer?Anonymous
September 11, 2013
Error 25541. Failed to open XML file C:WindowsMicrosoft.NETFrameworkv2.0.50727CONFIGmachine.config, system error: -2147024786 I copied the file from directory called machine.config.default to create machine.config and managed to install Visual Studio 2010. Thanks.Anonymous
September 11, 2013
Hi Ciupacau - The error code -2147024786 means that trying to open the file failed. It probably got corrupted on your computer somehow, and copying machine.config.default and trying again is the same thing I would've suggested to resolve this type of error. I'm glad to hear that this worked for you.Anonymous
September 03, 2014
hii Aaron....I hava same problem as Ciupacau ,but i can't understand the solution u given above..pls explain what i have to do with machine.config.default in details....Anonymous
September 04, 2014
Hi akanksha g - Here are more specific steps for replacing machine.config:
- Go to the folder C:windowsMicrosoft.NETFrameworkv2.0.50727CONFIG
- Rename the file machine.config to machine.config.old
- Make a copy of the file machine.config.default and rename the copy to be machine.config
- If your OS is 64-bit, go to the folder C:windowsMicrosoft.NETFramework64v2.0.50727CONFIG and repeat the above steps
- Reboot your computer Hopefully this helps.
Anonymous
May 05, 2015
Hi Aaron, I get "Setup Error" when I try to install .NET Framework 3.5SP1 on Windows Server 2008 SP2 Standard. I have uploaded the vslogs.cab file to: onedrive.live.com/redir Please can you advise on what I need to do to get .NET Framework 3.5SP1 installed? Many thanks.Anonymous
May 06, 2015
Hi AMC - I downloaded your vslogs.cab, but when I tried to open it, I was told that it couldn't be opened, so I'm guessing it got corrupted during the upload process or something like that. Can you please try to re-create and re-upload it and I'll try again?Anonymous
May 06, 2015
Hi Aaron, thanks for your response. I have re-run the collection tool and the newly created vslogs.cab file has been uploaded to: onedrive.live.com/redirAnonymous
May 07, 2015
Hi AMC - I was able to open the new vslogs.cab. The errors that I see in the log show that .NET Framework setup is unable to find one of the packages that it needs to install behind the scenes. It looks like you're using the web download version of .NET Framework setup. I'd recommend trying to download and run the offline installer instead. For the .NET Framework 3.5 SP1, the offline installer is at www.microsoft.com/.../details.aspx.Anonymous
May 07, 2015
Hi Aaron, I have been using the offline installer which is 231MB in size. I may have used the web download version at some point as a test, which is where those log entries may have come from? I've primarily been using the full offline installer and that is what's returning the setup error. Please advise further. Thank you.Anonymous
May 07, 2015
Hi AMC - Correct, the errors I saw were from web installers that were run on your PC on April 30, 2015. The newer logs that were in your vslogs.cab didn't show any errors. At this point, I'd recommend trying to use the tools and steps listed at blogs.msdn.com/.../8108332.aspx to fully uninstall the .NET Framework 3.5 SP1, then try again to install it with the offline installer.Anonymous
May 07, 2015
The comment has been removedAnonymous
May 07, 2015
Hi AMC - It looks like the .NET Framework 3.5 installer thinks that you already have it installed, and so it is skipping trying to install it as a result. This is the registry keys that it uses to detect whether or not to install it: [HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv3.5] Version = 3.5.30729.01 [HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftNET Framework SetupNDPv3.5] Version = 3.5.30729.01 I'd suggest using regedit to look for those keys, and if they exist, rename them and then try to run .NET Framework 3.5 SP1 setup again.Anonymous
May 08, 2015
Hi Aaron, that's fixed it! The second key still remained, and renaming this allows .NET Framework 3.5 SP1 to install again. It's strange that the cleanup tool neglected to remove this. Anyway, I can't thank you enough. You're doing an absolutely blinding job here, so keep up the fantastic work! Many, many thanks :)Anonymous
May 08, 2015
Hi AMC - I'm glad to hear that removing the registry key allowed you to install the .NET Framework 3.5 SP1. The .NET Framework cleanup tool does remove that key, so I'm not sure why it was still present after running the cleanup tool. Maybe the cleanup tool failed to remove the key because of an access denied error or something like that? The cleanup tool creates a log file in %temp% that lists each action that it takes, so if it hit any errors, they should be listed there.Anonymous
May 09, 2015
Hi Aaron, I will try to check the log file at the next opportunity. Thanks again for all your help.