WinSDK bug notification: SDK Config Tool appears to work but fails

Where is UISpy.exe?

Microsoft Windows SDK Blog — Thu, 13 Nov 2008 05:25:33 GMT

The UI Spy tool did not ship in the Windows SDK for Windows Server 2008 and .NET Framework 3.5 , released

How to get the WinSDK Configuration Tool to work

Microsoft Windows SDK Blog — Mon, 06 Oct 2008 22:12:43 GMT

The Windows SDK Configuration Tool sets which version of Windows SDK headers, libraries and tools you

How to get the SDK Configuration Tool to work

ascend slowly, breathing normally — Mon, 22 Sep 2008 02:46:08 GMT

The Windows SDK Configuration Tool sets which version of Windows SDK headers, libraries and tools you

Workaround: VS2008 SP1 Breaks WinSDK Configuration Tool

ascend slowly, breathing normally — Mon, 25 Aug 2008 18:48:50 GMT

Issue : Installing Visual Studio 2008 SP1 breaks the Windows SDK Configuration tool in the Windows SDK

Bug Notification: VS2008 SP1 Breaks WinSDK Configuration Tool

Microsoft Windows SDK Blog — Sat, 23 Aug 2008 03:28:10 GMT

Issue : Installing Visual Studio 2008 SP1 breaks the Windows SDK Configuration tool in the Windows SDK

re: WinSDK bug notification: SDK Config Tool appears to work but fails

Brian Cost — Fri, 18 Jul 2008 18:21:01 GMT

Sajusathyan, I’m happy to help you if personally if you want to email me. You shouldn't have to reinstall, although that is one way to have VS point to the v6.1 directory. I apologize for the inconvenience this bug has caused you. Good luck!

--Karin

re: WinSDK bug notification: SDK Config Tool appears to work but fails

sajusathyan — Sun, 13 Jul 2008 15:33:44 GMT

Sorry about the typo.. I mean v6.0a.

I think I have installed the SDK after installing VS 2008.

I will try to reinstall again.

thanks

re: WinSDK bug notification: SDK Config Tool appears to work but fails

Brian Cost — Mon, 07 Jul 2008 18:25:29 GMT

Sajusathyan, I’m happy to help you troubleshoot your problem, but I’m not sure what it is. There is no SDK version v6.01a. The Windows SDK components installed with Visual Studio 2008 are v6.0a. The Standalone SDK for Server 2008 is version v6.1. Your VC++ directories will be set to point to whichever version of the SDK components were installed last, as I outlined in this blog post. When a Windows SDK (including the Windows SDK embedded in Visual Studio 2008) is installed, it writes the “currentInstallFolder" value in both of the following keys:

• HKEY_CURRENT_USER\Software\Microsoft\Microsoft SDKs\Windows\

• HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SDKs\Windows\

If you installed the standalone SDK for Server 2008 after Visual Studio 2008, the currentInstallFolder key will be set to v6.1. If you installed the standalone SDK for Server 2008 before Visual Studio 2008, the currentInstallFolder key will be set to v6.0a. If you’d like to change that setting so Visual Studio uses a different set of Windows SDK components, you can use either of the workarounds outlined in this blog post. If you need additional help, please email me separately (karinm at Microsoft.com).

--Karin

re: WinSDK bug notification: SDK Config Tool appears to work but fails

sajusathyan — Mon, 07 Jul 2008 16:00:32 GMT

Even though I reported this issue... you haven't provided a clue regarding "why visual studio 2008 macros still pointing to the old v6.01A" !!!

Visual Studio Links #45

Visual Studio Hacks — Wed, 02 Jul 2008 04:21:07 GMT

My latest in a series of the weekly, or more often, summary of interesting links I come across related to Visual Studio. The Windows SDK Blog has a WinSDK bug notification: SDK Config Tool appears to work but fails (GUI version of the tool). Greg Duncan