{section: TODO}
 see Ticket #779
 
+{section: Windows Gotchas}
+{subsection: SDK corruption of VC setup}
+Installation of the new Microsoft SDK (6.1 aka Server 2008) can leave an existing VC 9.0 installation with a corrupted setup bat file. After installing the SDK, check the contents of =C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat= {linebreak}If you see the lines:
+
+{code}
+@SET FrameworkDir=Framework32
+@SET FrameworkVersion=v2.0.50727
+{endcode}
+change them to:
+{code}
+@SET FrameworkDir=C:\Windows\Microsoft.NET\Framework
+@SET FrameworkVersion=v2.0.50727
+@SET Framework35Version=v3.5
+{endcode}
+
+Also, a portion of the PATH variable may have an incorrect entry which can lead to problems in the CMD interpreter. If in the same file you see a PATH entry like:
+{code}
+%FrameworkDir%\%Framework35Version%\Microsoft .NET Framework 3.5 (Pre-Release Version);
+{endcode}
+change it to point to the correct version like:
+{code}
+%FrameworkDir%\%Framework35Version%\Microsoft .NET Framework 3.5 SP1;
+{endcode}
+
+{subsection: Environment variable expansion}
+The new =SetEnv.cmd= shipped in the 6.1 SDK requires that both command extensions and environment variable expansion be turned on. Either use the "CMD Shell" shortcut installed with the Windows SDK or ensure that CMD is launch with the /V:ON and /E:ON parameters. For example:
+{code}
+CMD \V:ON \E:ON
+{endcode}
+
 {section: Links}
 
 {link: http://www.cmake.org/cmake/help/documentation.html CMake Official Documentation}