Monday, May 07, 2012 7:39 PM
I tried to install Autocad 2013 on windows 7 but get an error in the beginning : "Your computer is using an unsupported version of the Microsoft .NET Framework. The product you are installing requires Microsoft .NET Framework 4.0 or later.
Please update .NET Framework 4.0 and restart your computer before installing your Autodesk product. " although .NET Framework 4.0 is installed.I used a .Netfixcleaner and cleared Temp\ folder stopped antivirus but the message comes.
what should i do ? Please help
Monday, May 07, 2012 10:12 PM
So, do you have the full .NET Framework 4.0 installed?
If you do, you'll find at least two entries in your installed programs list that begin "Microsoft .NET Framework 4.0". One for Client Profile and one for Extended (if you have 64 bit Win 7, there may be a third).
If you have only the entry for Client Profile, that may be your problem.
First, verify what you have installed with this verifier:
Select .NET 4.0 from the list. After running the tool, post the first 15 lines and last 15 lines of tool output here.
Once we see what you have now, we can proceed from there.
If you DO NOT have .NET 4.0 installed, I suggest you install it independently using this procedure, then install AutoCAD.
Before trying to install .NET Framework 4.0, execute this command from an ELEVATED Command Prompt provided by the .NET Framework Team:
"This issue is likely caused by a bad ACL on assembly\tmp folder. After installing updates, the ACL propagates to installed assembly folders in both 4.0 & legacy GAC. If those updates were installed by WU or another user, the propagated ACL will prevent install of the same assembly by the current user.
A work around would be to reset the ACL on GAC dirs.
for /F %D in ('dir %WINDIR%\assembly %WINDIR%\Microsoft.NET\assembly /s /b /a:d') do takeown /F %D && icacls %D /reset /T"
After running that command, follow these steps:
Please follow these instructions exactly:
1. Download a fresh copy of the standalone installer for .NET Framework 4.0:
2. Also, clear your %temp% directory and disable your AV software.
The %temp% directory is a reference to the Temp folder associated with the current user. To clear it, do the following:
Sign on to your system with the Administrator user account you will use to run the installer. Click the Start Orb and type %temp% in the search box. The search results will show the Temp folder you want. Click on the Temp folder to open it in Windows Explorer, then delete the entire contents.
3. Run the standalone installer from step 1 As Administrator.
Note: Just using an administrator account is NOT enough. To activate full privileges, you must right-click the installer, then select Run as administrator.
If the install fails, provide complete install logs as follows:
Please collect your install logs with this:
After you run Collect.exe, you'll find vslogs.cab in your %temp% directory. Please upload vslogs.cab to a public site, like SkyDrive, and post the link here.
Tuesday, May 08, 2012 12:49 PM
I uninstalled the .NET 4.0 Extended and Client then followed the above procedure and ran the ACL resetting command and ran the .NET setup file again. Here are logs.
[05/08/12,15:58:47] Beginning of new SetupVerifier activity logging session
[05/08/12,15:58:47] Activity log file location: C:\Users\admin\AppData\Local\Temp\setupverifier_main_05-08-12_15.58.47.txt
[05/08/12,15:58:47] Error log file location: C:\Users\admin\AppData\Local\Temp\setupverifier_errors_05-08-12_15.58.47.txt
[05/08/12,15:58:47] Build created on December 29, 2011
[05/08/12,15:58:47] Detected operating system: Windows 7 (x86)
[05/08/12,15:58:47] Install state for .NET Framework 1.0: not installed.
[05/08/12,15:58:47] Install state for .NET Framework 1.1: not installed.
[05/08/12,15:58:47] Install state for .NET Framework 2.0: installed with service pack 2.
[05/08/12,15:58:47] Install state for .NET Framework 3.0: installed with service pack 2.
[05/08/12,15:58:47] Install state for .NET Framework 3.5: installed with service pack 1.
[05/08/12,15:58:47] Install state for .NET Framework 4 Client: installed with no service packs.
[05/08/12,15:58:47] Install state for .NET Framework 4 Full: installed with no service packs.
[05/08/12,15:58:47] Not adding product '.NET Framework 1.0' because it is not currently installed
[05/08/12,15:58:47] Not adding product '.NET Framework 1.1' because it is not currently installed
[05/08/12,15:58:47] Not adding product '.NET Framework 1.1 SP1' because it is not currently installed
[05/08/12,15:58:47] Not adding product '.NET Framework 2.0' because it is not currently installed
[05/08/12,15:58:47] Not adding product '.NET Framework 2.0 SP1' because it is not currently installed
[05/08/12,15:58:47] Not adding product '.NET Framework 3.0' because it is not currently installed
[05/08/12,15:58:48] Not adding product '.NET Framework 3.0 SP1' because it is not currently installed
[05/08/12,15:58:48] Not adding product '.NET Framework 3.5' because it is not currently installed
[05/08/12,15:58:52] Starting verification for product .NET Framework 4 Full
[05/08/12,15:59:15] Section [Registry - .NET Framework 4 Full (Common)] - stop parsing entries
[05/08/12,15:59:15] Section [Registry - .NET Framework 4 Full (32-bit)] - start parsing entries
[05/08/12,15:59:15] Section [Registry - .NET Framework 4 Full (32-bit)] - stop parsing entries
[05/08/12,15:59:15] Not running action 'Registry - .NET Framework 4 Full (64-bit)' for product '.NET Framework 4 Full' because the OS condition does not match
[05/08/12,15:59:15] Not running action 'Registry - .NET Framework 4 Full (Wow6432Node)' for product '.NET Framework 4 Full' because the OS condition does not match
[05/08/12,15:59:15] Processing custom action 'Custom Action - .NET Framework 4.0 test application'
[05/08/12,15:59:15] ExecutablePath = 'Netfx40TestApplication.exe'
[05/08/12,15:59:15] FriendlyName = '.NET Framework 4 test application'
[05/08/12,15:59:15] TimeoutSeconds = '300'
[05/08/12,15:59:15] WaitOnExit = 'true'
[05/08/12,15:59:15] Silent = 'true'
[05/08/12,15:59:15] Launching process 'Netfx40TestApplication.exe' now
[05/08/12,15:59:15] Process successfully launched. Waiting 300 seconds for it to complete.
[05/08/12,15:59:15] ****ERROR**** Process 'Netfx40TestApplication.exe' exited with return code -1073741515
[05/08/12,15:59:15] ****ERROR**** Verification failed for product .NET Framework 4 Full
[05/08/12,16:05:41] SetupVerifier exiting with return value 100
[05/08/12,16:06:46] Beginning of new SetupVerifier error logging session
[05/08/12,16:06:46] Activity log file location: C:\Users\admin\AppData\Local\Temp\setupverifier_main_05-08-12_16.06.46.txt
[05/08/12,16:06:46] Error log file location: C:\Users\admin\AppData\Local\Temp\setupverifier_errors_05-08-12_16.06.46.txt
[05/08/12,16:06:46] Build created on December 29, 2011
[05/08/12,16:06:46] Detected operating system: Windows 7 (x86)
[05/08/12,16:06:57] ****ERROR**** File C:\Windows\system32\mscoree.dll is not installed on the system
[05/08/12,16:06:57] ****ERROR**** File C:\Windows\system32\mscorier.dll is not installed on the system
[05/08/12,16:06:57] ***WARNING*** File C:\Windows\Microsoft.NET\Framework\sbscmp20_mscorlib.dll is not installed on the system
[05/08/12,16:06:57] ***WARNING*** File C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpftxt_v0400.dll is not installed on the system
[05/08/12,16:06:57] ***WARNING*** File C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\WPFFontCache_v0400.exe is not installed on the system
[05/08/12,16:06:58] ****ERROR**** Process 'Netfx40TestApplication.exe' exited with return code -1073741515
[05/08/12,16:06:58] ****ERROR**** Verification failed for product .NET Framework 4 Full
Tuesday, May 08, 2012 1:51 PM
I just finished reading a couple of dozen threads in this forum related to:
"****ERROR**** Process 'Netfx40TestApplication.exe' exited with return code -1073741515".
The synopsis won't make you happy :-(
If uninstalling, then reinstalling .NET Framework 4.0 using the steps I provided earlier does not resolve the issue of failing the verification test app, you're looking at reinstalling your OS. I hate having to type those words, but htere it is.
Wednesday, May 09, 2012 5:59 AMModerator
Welcome to the MSDN forum.
After reading your logs, I got almost the same result like pvdg42.
But I found that you have another error 0x80070424, so please try the solutions from this page
Maybe you can fix by that solutions. If these cannot work. I'm afraid you may have to reinstall your OS.
Barry Wang [MSFT]
MSDN Community Support | Feedback to us
Wednesday, May 09, 2012 8:27 AMI am forgeting to say thank you pvdg42 and BarryWang for wonderful support. Many thanks.
Unfortunately, it didn't make a difference. Could you a bit explain why should I reinstall OS because of formidable problem. What exactly the error is ?
Wednesday, May 09, 2012 8:47 AMModerator
After checking your installing logs, your error is like this
"Exe (D:\1c9522724b5c9579002613dec3\Windows6.1-KB958488-v6001-x86.msu) failed with 0x80240017 - (null).
[5/8/2012, 15:55:14]PerformOperation on exe returned exit code 2149842967 (translates to HRESULT = 0x80240017)"
"SchedSecureObjectsRollback: Failed to store ACL rollback information with error 0x80070424 - continuing"
First error is mostly because CRC failed and the second indicates that the service does not exist as an installed.
If you tried another standalone package then I'm afraid the error is not corrupt installation pakcage(That means not CRC error ).
Then I asked you to fix the service but it failed again.
To be honest, we haven't found the solution for your error until now. So I think maybe your system is corrupt and the best solution now maybe OS reinstall or OS repair. You can refer to this page to check your system files with the command:sfc /scannow http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Barry Wang [MSFT]
MSDN Community Support | Feedback to us
Monday, July 23, 2012 11:55 AM
I have the exact same problem and I congratulate you on your honesty Barry Wang.
This is one of the rare cases where people from a support team of some software company don't say "its not our mistake, its your corrupt system..." but actually admit that they don't have a solution...oh well, for me that's good enough, its certainly much better than excusing one's mistakes and blaming it on users corrupt system...like all of us never heard of antivirus or system maintenance...
The only thing I can do now is reinstall windows(I have a feeling that it won't work even after that), which I DID 3 days ago and set all my software up, so I'll totally hate to do it now.
People don't get our pain...its not about reinstalling the darn windows, I am not THAT LAZY, its about trust and being secure about framework 4...I don't want an error like this to happen to me in the middle of some project while meeting the tightest deadline ever...Many of us are already all stressed up and pressured enough, we don't need any more of software unreliability and unpredictability.
I wish someone could seriously come up with the solution about this, there are sooo many posts around the net related to this issue since 2 years ago and NO ONE has ever came up with anything besides reinstalling windows!?
Sunday, September 09, 2012 8:00 PM
Clearly, Microsoft self compatibility isn't working.
After paying so much money on these products you get all this? Really?
Thursday, October 18, 2012 6:33 AM
I had the almost exact same problem, read over the different posts and came upon a simple and quick solution, although it's truly not of my design.
I'm deeply sorry that I didn't know of your situation at the time, nor that this same problem had been going on for so long.
I sincerely hope you may find the time to try it and see if it works.
I would suggest for you to copy the entire installation to a local folder on your hard drive first. Please make a copy of the file named "Setup.ini" as in "Setup - Copy.ini" and open the original with Notepad or your text editor of choice. Search and delete all instances of "DOTNET20" and "DOTNET4" by going to "Edit" and "Replace..."; you may also use the shortcut Ctrl-H, and save the file after you've cleaned it up. There's one particular line with "DOTNET4LANG" which needs to go too.
Now you may try and install your product; it shall give you numerous errors at first (I think I got around 5 or 7), complaining of the location of the installer or something, but just close and disregard all of them; the installation shall continue and complete successfully.
Some users have mentioned that the software gives errors when closing the app, but you shall find it stable and fully functional. Or at least as stable as it was originally designed.
I don't feel it necessary to explain why is it that it works, given the obvious nature of the problem and its solution.
Hope you and anyone else find it useful and as always, I'm grateful for the opportunity to help.
Friday, November 30, 2012 5:17 AM
See the new(?) update http://support.microsoft.com/kb/2762895