[SOLVED] The story goes on: .NET Framework 4.6 installation issue

[pustekuchen]

Hi everybody,

You want to know which story? --> https://www.sysnative.com/forums/wi...stallation-problem-error-643-a.html#post97795

Now, the story goes on: I wanted to upgrade to .Net Framework 4.6. However the installation stopped soon - again - with error code 643 :banghead: I tried to uninstall KB3008627, KB3000988 & KB2918614 (workaround which helped to install v4.5.2) but they weren't installed again by Windows update since I removed them some months ago. So I tried some FixIT solutions by M$ (.Net Repair ...), sfc -scannow (no errors) and other tips. Nothing helped and everything looked/looks like the first time: completely mysterious.

However I have found now two workarounds which help to get things working. It is definitely no solution which fixes the underlying problem but a shabby workaround.

ATTENTION: I don't know if these steps will cause other problems in future. Therefore you do this on your own risk!!! You need only one of those two methods to get it working. Don't ask me which one is less bad - I don't know.

First method:
1) rename folder "S-1-5-18" in C:\ProgramData\Microsoft\Crypto\RSA\ to "S-1-5-18_bak" or sth. like that
2) Run .net installer again. A new folder "S-1-5-18" should be created automatically during installation. More important: the installation should be successful now!
3) Interessting thing: if you don't install .net after the "S-1-5-18" folder was deleted, and you reboot your PC a new "S-1-5-18" folder gets created. If you open the folder you will be asked for permission. When you proceed and start the installation afterwards, it will fail as it did before! So accessing the folder (after having deleted it) will again prevent .NET installations! I don't know why and how this folder is interconnected with the issue... probably only M$ knows this. Perhaps.

Second method:
1) Whitelist the installer -> Link
2) Delete the registry hacks (if the issue occurs again in future with an M$ .msi package, you will have to add the registry keys again)

Here, I have a collection of some interesting links which are related to this "crypto-issue":

Error 997. Overlapped I/O operation is in progress: KB2918614 breaks Windows Installer Service - Microsoft Visual Studio/.Net Framework Setup & Deployment Tips & Tricks - Site Home - MSDN Blogs
installation - .NET 4 fails to install because SECUREREPAIR fails to CreateContentHash of file SetupResources.dll: for computing hash Error: 997 - Stack Overflow
https://social.msdn.microsoft.com/F...ies-to-40-45-and-all-updates?forum=netfxsetup
http://stackoverflow.com/questions/31840924/failed-visual-studio-2015-installation/31905202#31905202
http://www.sevenforums.com/software/377091-net-framework-error.html
http://www.tomshardware.co.uk/forum...o-rsa-causing-vcredist-2010-2008-install.html
https://www.sophos.com/de-de/support/knowledgebase/110803.aspx
https://social.technet.microsoft.co...atamicrosoftcryptorsas1518?forum=winservergen
http://www.networksteve.com/forum/t...rver_2014_Express_on_W/?TopicId=46476&Posts=7


It looks like this is a widely spread problem. And again: not only .NET Framework is affected but many other M$ applications respectively M$ .msi packages. For me it looks like update KB2918614 broke many Windows installations :shame2:

Both workarounds work for me. In each case when I uninstall .NET framework and remove the used workaround the subsequent installation will fail again. So I can easily reproduce the installation issue.
Can someone help me finding the root cause? I hate workarounds (which may lead to future errors). Here are the two log files I get when the installation error occurs: OneDrive

Please tell me if I can provide you more information. Thanks

 

[BrianDrab]

Hi and welcome back to Sysnative.

Thanks for the detailed information and research. Unfortuantely you are correct, we don't know why this happens. I've personally had success with the Whitelist so have used that. I've not used your Method#1 however and will keep that in mind so thank you again.

I wish I had more information for you.

 

[pustekuchen]

Interesting to hear that you are also affected. I think there must be a similarity between all affected Windows installations.

Does Microsoft help "normal" users like me? Can I open a case? Is it for free?

 

[BrianDrab]

Does Microsoft help "normal" users like me? Can I open a case? Is it for free?

Yes, you can try opening a case with Microsoft. It will be free for their 1st tier support to look into it. They will likely not know the solution and will offer you their 2nd tier paid support. You can always try though.