.net framework error

[GokAy]

The main MS site that would come up for the error had 3 reasons for this failure:
- SYSTEM account not having the permission
- trying to install to an encrypted folder
- 3rd, I can't remember at the moment

 

[NoelDP]

I have to admit that I wasn't eve aware that a .NET v4.6 was in the works - let alone released (just goes to show how much I know!)
Almost all Windows/Microsoft Updates will choose the partition with the most available free space at the repository for the TEMPORARY files it creates during the install - but NOT the location for the final installed files.

The installed file location will be determined by the installer and the default locations specified by the Administrator on the client system.

In almost all cases of serious problems with .NET other than those with the preinstalled versions (3.5 in the case of Win7) the best solution is to uninstall and clean up using Aaron Stebner's tool here - .NET Framework Cleanup Tool User's Guide - Aaron Stebner's WebLog - Site Home - MSDN Blogs - and then reinstall the latest version from a fresh download.

 

[UsernameIssues]

~~~
In almost all cases of serious problems with .NET other than those with the preinstalled versions (3.5 in the case of Win7) the best solution is to uninstall and clean up using Aaron Stebner's tool here - .NET Framework Cleanup Tool User's Guide - Aaron Stebner's WebLog - Site Home - MSDN Blogs - and then reinstall the latest version from a fresh download.

I think that the OP tried that and another tool. See post #11.

But maybe we should work thru what the OP did and saw whiel using Stebner's tool.

 

[tkrojam]

Netframe works should be on the "C" partition.

How much free space do you have in the "C" partition.

According to the log files, it is going onto "C".
That has no bearing on where it decompresses to.

tkrojam,
Can you provide a link to the exact file that you are using to perform this install? Your link in post #13 is to a web based installer. Is that what you used? Or maybe an offline/standalone installer? I would like to install this into a virtual machine so that I can compare a good log file with yours. I see things in your log files that don't seem to mean what I initially thought they meant:

MSI (s) (3C!F4) [14:16:30:289]: Note: 1: 2259 2:  3:  4:  
08/05/15 14:16:30 DDSet_Status: Reserving disk space by 16460256 in %windir%
08/05/15 14:16:30 DDSet_Warning: MsiViewExecute failed
08/05/15 14:16:30 DDSet_Warning: [COLOR=Red]Could not reserve disk space[/COLOR] for mscorlib_dll_x86
08/05/15 14:16:30 DDSet_Status: component: system_enterpriseservices_dll_x86
08/05/15 14:16:30 DDSet_Status: Size: 239848

Plenty of people have threads quoting those same lines - yet they have enough free space (like you do). But the real puzzler is, there are lines like that even when the .net install completes "without error". Also, the installer can reserve space for subsequent files - then another round of failures to reserve space. I guess we can ignore those lines.

These lines I wonder about:

MSI (s) (3C!CC) [14:16:32:959]: Source type from package 'netfx_Full_x64.msi': 0
MSI (s) (3C!CC) [14:16:32:959]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{94A631D5-B30A-3DD8-B65C-1117C09DA73E}
MSI (s) (3C!CC) [14:16:32:959]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (3C!CC) [14:16:32:969]: Note: 1: 2262 2: SourceHash 3: -2147287038 
MSI (s) (3C!CC) [14:16:32:969]: SECREPAIR: New Hash Database creation complete.
MSI (s) (3C!CC) [14:16:32:969]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (3C!CC) [14:16:32:979]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (3C!CC) [14:16:32:979]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (3C!CC) [14:16:32:979]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (3C!CC) [14:16:32:979]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (3C!CC) [14:16:32:979]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (3C!CC) [14:16:32:979]: SECREPAIR: Crypt Provider not initialized. Error:997
MSI (s) (3C!CC) [14:16:32:979]: SECUREREPAIR: Failed to CreateContentHash of the file: 1030\SetupResources.dll: for computing its hash. Error: 997
MSI (s) (3C!CC) [14:16:32:979]: SECREPAIR: Failed to create hash for the install source files
MSI (s) (3C!CC) [14:16:32:979]: SECUREREPAIR: SecureRepair Failed. Error code: 3e5FC3E44B8
Action start 14:16:32: CA_NgenUpdateHighestVersion_I_RB_amd64.3643236F_FC70_11D3_A536_0090278A1BB8.
MSI (s) (3C!CC) [14:16:32:979]: 
Error 997.Overlapped I/O operation is in progress.

Download Microsoft .NET Framework 4.6 (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2008 SP2 Windows Server 2008 R2 SP1, Windows Server 2012 and Windows Server 2012 R2 from Official Microsoft Downloa

 

[tkrojam]

The main MS site that would come up for the error had 3 reasons for this failure:
- SYSTEM account not having the permission
- trying to install to an encrypted folder
- 3rd, I can't remember at the moment

Thanks for reply.
- SYSTEM account not having the permission <<< This is the only admin account
- trying to install to an encrypted folder <<< I confirmed Temp folder was not encrypted

 

[UsernameIssues]

SECREPAIR: Crypt Provider not initialized.

This seems to point to a problem with your profile.

Create a temporary local admin user account and try the install via that account.

 

[tkrojam]

SECREPAIR: Crypt Provider not initialized.

This seems to point to a problem with your profile.

Create a temporary local admin user account and try the install via that account.

For your approach, I tried but no help, please find the attached .zip for LOG files

 

[UsernameIssues]

Thanks for testing with a new account.

Can you install any app via an MSI file?

 

[tkrojam]

Thanks for testing with a new account.

Can you install any app via an MSI file?

Yes. Moreover, I can successfully install 4.6 on my X220 laptop (running W2K8 Server R2), please find the attached .zip for LOG files if any helpful ideas, Thanks!

 

[UsernameIssues]

I have successfully installed 4.6 several times while thinking about this thread of yours.

You are probably better off with a repair install of the OS. See post #8
.

 

[Layback Bear]

After going through this thread again I agree with UsernameIssues.
A repair install should fix your problem.
Before you start with the Repair Install make sure you have your COA key handy.

 

[tkrojam]

Thanks all for help. However, I am not going to repair the whole OS as I am afraid it will bring out further system issues after I do this.

 

[NoelDP]

A Repair install is more likely to FIX system issues than to create them - unless you have a highly modified install.

 

[Layback Bear]

tkrojam can you tell us what kind of issues you think a Repair Install will cause you.

 

[pustekuchencake]

Hey guys,

I have the same issue I think. I posted it already at sysnative.com:

This issue has a case-history --> Windows updates KB3001652 & KB2901983 installation problem (Error 643)

Now, the story goes on: I wanted to upgrade to .Net Framework 4.6. However the installation stopped soon - again - with error code 643

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
Failed Visual Studio 2015 installation - Stack Overflow
http://www.sevenforums.com/software/377091-net-framework-error.html
What does C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 use for ? why is it causing vcredist 2010 and 2008 not to install - windows 10 - Windows 10
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

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

 

[tkrojam]

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!

This worked like a charm and allowed me to complete my installs. Hopefully someone else will find it useful.

THANK YOU