.

NET Framework verification tool change history The current build was created on October 15, 2010 For more information about the .NET Framework verification tool, see the followi ng blog post: http://blogs.msdn.com/astebner/pages/8999004.aspx ------------------Change history ------------------February 4, 2008 February 11, 2008 February 29, 2008 March 4, 2008 - Initial version of the tool created. - Added command line switches to specify the locations of the log files created by setupverifier.exe. - Added steps to verify all of the files installed by the .NET Framework 3.0 and 3.5. - Updated the tool to correctly handle some files for the .NET Framework 3.0 that are only installed on Windows Vista and higher and some files that are not installed on 64-bit OS's. - Fixed a .NET Framework 3.0 registry value that was incorrectly reporting failure on 64-bit Windows Vista. - Fixed some registry values and a file that were incorrectly reporting failure on Windows Vista. - Added log file entry to indicate what OS version the tool is being run on. - Fixed issue retrieving the Windows directory on systems with Terminal Services enabled. - Fixed false positive for a file installed by the .NET Framework 3.0 SP1 but not the original version of the .NET Framework 3.0. - Added logic to the setup verification tool to verify the .NET Framework 2.0 SP2, 3.0 SP2 and 3.5 SP1. - Added logging for .NET Framework version detection. Upda the tool to allow configuring the window title in cleanup .ini. September 5, 2008 - Fixed some false positives in .NET Framework 1.1 verification logic.

March 5, 2008 March 17, 2008 March 28, 2008 June 5, 2008 June 24, 2008

September 3, 2008 September 4, 2008 ted

September 15, 2008 - Fixed detection error for .NET Framework 1.0 files on 64-bit OS's. September 27, 2008 - Added logic to verify DWORD registry values are greater t han

or less than expected values instead of only equal to expected values. October 15, 2008 ework October 31, 2008 the 003. November 25, 2008 o not 64-bit versions of Windows. December 22, 2008 February 20, 2009 lled - Added version string that is added to the log file. - Added product filtering so the UI will only display insta versions of the .NET Framework by default. This can be overridden with the new /a switch if needed. Added an option to verify the .NET Framework 1.1 SP1. Fixed .NET Framework 1.1 detection issue on 64-bit Window s. Added better logging for registry values being verified. February 24, 2009 ork ck registry value was missing. March 10, 2009 use ounts. March 13, 2009 ausing March 23, 2009 e causing July 17, 2009 of the - Removed some .NET Framework 1.1 registry keys that were c false error reports. - Fixed some more .NET Framework 1.1 registry keys that wer false error reports. - Fixed false errors being reported on non-English versions .NET Framework 1.0. Fixed filtering problem that caused the .NET Framework 1. 0 to be removed from the list if any 1.0 service packs are instal led. - Removed checks for HKEY_CURRENT_USER registry values beca they cause false errors on systems with multiple user acc - Fixed a bug that would cause a version of the .NET Framew to be filtered out if it was installed but the service pa - Fixed a logic problem that caused the verification tool t check the correct location for 32-bit registry values on - Added a test application that verifies that the .NET Fram runtime can be started on a user's system. - Fixed a false positive for 3 files that were removed from .NET Framework 3.0 SP2 on Windows XP and Windows Server 2

Fixed false errors being reported for the .NET Framework 1.1 if the .NET Framework 1.0 is also installed on the system. Fixed false errors being reported for the .NET Framework 3.5 SP1 on Windows 7. Added detection and logging for .NET Framework 4 and Wind ows 7. October 19, 2009 ws ME. November 10, 2009 2 and December 9, 2009 d January 18, 2010 k 2.0 January 27, 2010 ET s. February 19, 2010 nglish versions of Windows 7. February 20, 2010 rk sions of Windows. March 15, 2010 March 29, 2010 d of le to the log file. May 11, 2010 Full. May 24, 2010 n July 2, 2010 - Add the ability to verify the .NET Framework 4 Client and - Fix some false errors for .NET Framework 4 verification o Windows XP. - Fix some false errors for .NET Framework 4 verification o - Force the process exit code to get propagated to the self extracting setup package. - Add the ability to treat missing files as warnings instea errors. Add file version information for each verified fi - Stop checking for English-only files for the .NET Framewo 3.5 SP1 because it causes false errors on non-English ver - Stop checking for English-only registry keys for the .NET Framework 3.5 SP1 because it causes false errors on non-E - Fixed false errors being reported on Windows 98 and Windo - Fixed false error being reported on Windows Server 2008 R Windows 7. - Fixed detection problems for performance counter files an registry keys on Windows 98 and ME. - Stop checking for some .config files during .NET Framewor verification that can result in false errors. - Stop checking for some additional .config files during .N Framework 2.0 verification that can result in false error

n Windows Vista and higher. August 16, 2010 n October 11, 2010 ys k 1.1 registry keys to be treated as warnings instead of errors to eliminate false positives during verification. October 15, 2010 change. - Fixed bug in registry parsing introduced by the previous - Fix some false errors for .NET Framework 4 verification o Windows Server 2003 x64. - Add the ability to treat missing or incorrect registry ke as warnings instead of errors. Mark several .NET Framewor