New
#21
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
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
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.
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.
Thanks for testing with a new account.
Can you install any app via an MSI file?