.NET Framework setup verification tool now supports .NET Framework 4.5 and Windows 8
I have posted an updated version of the .NET Framework setup verification tool that supports verifying the install state of the .NET Framework 4.5. It has also been updated to correctly recognize when it is running on Windows 8. This support is preliminary because the final versions of the .NET Framework 4.5 and Windows 8 have not yet shipped, and I’ll post an updated version in the future when the .NET Framework 4.5 and Windows 8 ship if any changes are made between now and then that cause the tool to report incorrect results.
There is more information about how to download and use the .NET Framework setup verification tool in the user’s guide at https://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx.
I have not yet posted updated versions of the .NET Framework cleanup tool or the sample .NET Framework detection code, but they are in progress and I’ll upload then and post an update on my blog when they are ready.
As always, if you run into any issues or have any feedback about the .NET Framework setup verification tool, please let me know by posting a comment on one of my blog posts or using the contact form.
Comments
Anonymous
July 04, 2012
Hi Aaron, I found this tool from asoft called .NET Version Detector: www.asoft.be/prod_netver.html It's actually very nice for visualizing the different versions and for users that don't know much about the different versions installed on their machines. And keep up the good work with the blog, always nice to read!Anonymous
July 10, 2012
The comment has been removedAnonymous
July 10, 2012
Hi Zimfree - I think you will need to try to manually replace the missing manifest file that is listed in the "Unavailable repair files" section of the report. There are some instructions in the tutorial at www.sevenforums.com/.../108805-system-update-readiness-tool-checksur-log-file-analyzis.html that will hopefully help you do that.Anonymous
July 10, 2012
Thanks, Aaron...I'll give it a shot and let you know how it went! Much appreciated!Anonymous
July 10, 2012
Hi Aaron, sorry if this is a duplicate msg. I posted again yesterday but can't find my comment. I was able to follow those instructions up to the point of where to find the manifest file that's missing on my Win 7 Pro disk. The instructions are very generic, but I'm looking in the Win 7 Pro/windows/system 32 folder and can't find another folder. I thought there might be a 'winsxs' folder, but no luck. Could you help me locate the file and tell me where I need to copy it/replace it on my system? Thanks!Anonymous
July 11, 2012
The comment has been removedAnonymous
July 11, 2012
My internet keeps kicking out so I don't know if you got my last post. When I try to rename the instance I'm told there's already an instance with that name. If I search the registry I can't see the duplicate.Anonymous
July 11, 2012
Also, like I said, I don't get any list when I open the 'Turn Windows Features on/off' through optionalfeatures.exe...is it enough just to run it?Anonymous
July 12, 2012
Hi Zimfree - Yes, it should be enough to just open the Windows Features control panel. I think it is not showing any entries because of the same error being reported by the System Update Readiness Tool. If you already have an instance with that name, then it might be sufficient to just delete that entry instead of trying to rename it. Before making that type of registry modification, I'd suggest making a backup just in case you find that you need to restore it later. You can find instructions for doing that at windows.microsoft.com/.../Back-up-the-registry.Anonymous
July 12, 2012
The comment has been removedAnonymous
July 12, 2012
Hi Zimfree - Awesome news, I'm glad to hear that things are working now. In the past, I've seen this type of issue prevent Windows Update from finding any applicable updates, so I'm not surprised to see a big backlog of updates that it found and needed to install for you afterwards. Definitely let me know if you run into any further issues in the future and I'll try to help if I can.Anonymous
August 07, 2012
The comment has been removedAnonymous
August 07, 2012
Hi Meenakshi - Windows 8 includes the .NET Framework 4.5 as a part of the OS, and it cannot be removed or installed separately from Windows. In pre-release versions of Windows 8, there is a pre-release version of the .NET Framework 4.5 as well. Visual Studio 2012 requires a matching build of the .NET Framework 4.5, and since Windows 8 includes a build of the .NET Framework 4.5 as a part of the OS, you have to install a version of VS 2012 on a build of Windows 8 that includes a matching version of the .NET Framework 4.5. For example:If you want to install the VS 2012 beta, you have to install on the Windows 8 consumer preview.
If you want to install the VS 2012 RC, you have to install on the Windows 8 release preview.
If you want to install the final version of VS 2012, you have to install on the final version of Windows 8. You cannot install versions of VS 2012 on versions of Windows 8 that don't match the above statements.
Anonymous
August 08, 2012
Oh great, thanks for your help. i have VS12 RC and my Os is Windows 8 consumer preview. i will try installing beta then.Anonymous
August 16, 2012
Hi Aaron! Does the .NET setup verification tool work on the "official" version of .NET 4.5 released to MSDN account holders yesterday? Thanks!Anonymous
August 16, 2012
Hi Don - Yes, the verification tool should work correctly on the final version of the .NET Framework 4.5. Please let me know if you run into any issues.Anonymous
August 28, 2012
Hi, I have problems with the .Net Framework on Windows 8 Final. VS 2012 Final doesn't list FW 4.5 in its list, and so I tried to reinstall it, but didn't work. After some search I found this Tool, but it doesn't start. (After the License Dialog there comes the progress and then nothing). Any idea what I can check?Anonymous
August 29, 2012
Hi Lohnegrim - The final version of Windows 8 includes the final version of the .NET Framework 4.5, and the final version of VS 2012 should recognize that and skip trying to install the .NET Framework 4.5 because it is already present on the computer. There is an issue with the verification tool that prevents it from running on the final version of Windows 8 currently. I'm still trying to work out the exact right way to fix that, but for now, you won't be able to use it on Windows 8.Anonymous
August 31, 2012
Hi Aaron! >> The final version of Windows 8 includes the final version of the .NET Framework 4.5 Yes I know >> and the final version of VS 2012 should recognize that and skip trying to install the .NET Framework 4.5 because it is already present on the computer. Yes it does, but if I start VS 2012 and click on New Project, then the FW Drop down list only shows 2.0 to 4.0, but not 4.5. Also if I select a Windows Store project type, then the Drop down list is Disabled and Empty. On a different System I can select from 2.0 to 4.5Anonymous
August 31, 2012
Seems like I missed everything except the .xml Files directly in the Folder 'Program Files (x86)Reference AssembliesMicrosoftFramework.NETCorev4.5' and '...Framework.NETFrameworkv4.5'Anonymous
September 01, 2012
The comment has been removedAnonymous
September 01, 2012
Hi Aaron! I already solved it, I missed some files in the '...Reference Assemblies...' folders. I copied them from another Win8, and then everything worked. Thanks anywayAnonymous
April 17, 2013
On a Windows 2000 SP4 machine I'm getting a "Error creating process...setupverifier2.exe Reason: c:WINNTsystem32advpack.dll" error and therefore cannot check if .NET 2 is actually installed. Any ideas? AndrewAnonymous
April 17, 2013
Hi Andrew Jones - I made a change to the verification tool in December 2011 that prevents it from running on versions of Windows older than Windows XP. I don't have an easy way to go back and undo all of the changes made since then, so you won't be able to use this tool to verify the .NET Framework 2.0 on Windows 2000. Are you running into errors when trying to use .NET Framework applications on your Windows 2000 computer currently? If so, can you let me know the exact error messages and I'll see if I can help you troubleshoot the issues?Anonymous
June 24, 2014
.NET 4.5.2?Anonymous
June 24, 2014
Hi Matt - Yes, I'm planning to update both the verification tool and the .NET Framework detection sample to support 4.5.2, but I haven't had time yet. I hope to get to that in the next few days. I'm sorry for the delay.