Unistalled Windows sdk 10, it still complains of incompatible WPT

[elect86]

Hi,

I am using Win7 64, I unistall Windows 10 SDK from the system panel and restarted, hoping to get rid of WPT too, but unfortunately it doesn't look so..

How can I solve?

[randomascii]

First, run this:

"c:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\xperf.exe"

If it is 10.0.14393, or fails to run, then you still have the anniversary edition version and that is incompatible.

I don't know why uninstall would fail. It's all black magic. You do have the option of installing the previous version (10.0.10586) on another machine and then copying it to the directory listed above. That is a valid install mechanism.

On Mon, Oct 17, 2016 at 1:58 AM, Giuseppe Barbieri <notifications@github.com

wrote:

Hi,

I am using Win7 64, I unistall Windows 10 SDK from the system panel and restarted, hoping to get rid of WPT too, but unfortunately it doesn't look so..

[image: image] https://camo.githubusercontent.com/33d1a1a8ecebb76373298494ba5d96981dd0c82c/687474703a2f2f692e696d6775722e636f6d2f44506a794479332e706e67

How can I solve?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/google/UIforETW/issues/92, or mute the thread https://github.com/notifications/unsubscribe-auth/AKTLqWgzf-RDufL6cg_sBb0ucRRVD5O2ks5q0zisgaJpZM4KYYXg .

Bruce Dawson

[modulexcite]

I had to do an xcopy of the WPT from a new machine as uninstalling didn't work for me either. https://github.com/google/UIforETW/issues/85

[elect86]

I reinstalled it to give it another try and yep, it's the 10.0.14393.33..

is there a way to install the previous version 10.0.10586?

Moreover, I don't really get.. that's error seems referring to a 32/64 bit issue.. but I am on win7 x64, I had no chance to choose between 32 and 64, it directly installed the sdk under C:\Program Files (x86)..?!?

@modulexcite which OS is your new machine running? Which version of the SDK did you install? You just xcopied C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit?

[elect86]

My collegue managed to get it running, he has a 8.1 x64

Note: he had a lot of problems with log.cmd as far as he used powershell (Cannot create a file when that file already exists. (0xb7)... once he switched back to normal cmd no more errors..

Anyway, I xcopied his folder, but when I try to open Merged.etl it complains

Quick search, those dll don't exist neither or mine or my collegue's pc... mystery

[randomascii]

To install 10.0.10586 you need to uninstall 10.0.14393. I can't really offer advice on how to do that. It's a Microsoft bug that 10.0.14393 was even allowed to install in the first place.

The "C:\Program Files (x86)" thing is a red herring. That's just where it installs the toolkit on 64-bit Windows, even though it's a 64-bit toolchain. I think the installer is 32-bit or something stupid like that.

perf_nt.dll should be there whenever WPT is installed:

dir "c:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\perf_nt.dll" Volume in drive C has no label. Volume Serial Number is 18D4-8BE5

Directory of c:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit

07/28/2016 11:44 AM 1,441,472 perf_nt.dll 1 File(s) 1,441,472 bytes 0 Dir(s) 323,839,528,960 bytes free

Also, you should copy over the "c:\Program Files (x86)\Windows Kits\10\Debuggers" directory as well, 'cause WPT grabs symsrv.dll from there.

On Tue, Oct 18, 2016 at 1:48 AM, Giuseppe Barbieri <notifications@github.com

wrote:

My collegue managed to get it running, he has a 8.1 x64

Note: he had a lot of problems with log.cmd as far as he used powershell (Cannot create a file when that file already exists. (0xb7)... once he switched back to normal cmd no more errors..

Anyway, I xcopied his folder, but it complains

[image: image] https://camo.githubusercontent.com/81c106eb54ee7a58404ca73ea6bfafd5472291ac/687474703a2f2f692e696d6775722e636f6d2f383358326d444e2e706e67

Quick search, those dll don't exist neither or mine or my collegue's pc... mystery

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/google/UIforETW/issues/92#issuecomment-254445648, or mute the thread https://github.com/notifications/unsubscribe-auth/AKTLqdXIugeYm6zMmJYBpwmXKs_ELvIFks5q1IfIgaJpZM4KYYXg .

Bruce Dawson

[modulexcite]

@elect86 I'm using Windows 7 SP1 64-bit as well. The problem is with the Windows SDK v10.0.14393.33 which isn't compatible on Windows 7 & below and you won't be able to run any of the following tools XPerf, Performance Recorder and WPA after installing the SDK. It is only compatible with Windows 8.1 and above. I tried uninstalling the Windows SDK v10.0.14393.33 but that didn't seem to solve the problem so I spun up a VM and installed the old Windows SDK v10.0.10586.212 on it and copied the folder "Windows Performance Toolkit" under "C:\Program Files (x86)\Windows Kits\10" which seemed to have solved the problem on my machine.

Below are the issues reported earlier here and on Visual Studio Support Forum: https://github.com/google/UIforETW/issues/85 https://connect.microsoft.com/VisualStudio/feedback/details/3076739

[elect86]

Jeez, it looks like it is still '90 when it's about microsoft..

I unistalled the 10.0.14393, but everything looks like it's still there

and there is no way to install 10.0.10586

@modulexcite is it an option for you to upload Windows Performance Toolkit directory somewhere? It should be ~600MB

[modulexcite]

Like I mentioned earlier, uninstalling the SDK v10.0.14393.33 didn't work for me. You can find the older SDK versions at https://developer.microsoft.com/en-us/windows/downloads/sdk-archive.

Also, in the previous message I was only talking about the sub-directory "Windows Performance Toolkit" under "C:\Program Files (x86)\Windows Kits\10" which should be about ~72MB in size.

[chiamarc]

I can confirm that this same behavior exists for Windows Server 2008 Enterprise R2. I can't even get WPA 10 to start on this platform.

[randomascii]

If you can install the 10586 version of WPT on another machine then you can copy the install directory over to the Windows Server 2008 R2 machine. An xcopy "install" works fine and is probably the only solution if the previous version of WPT won't uninstall.

So, fire up a VM, install the 10586 version of WPT (the installer ships with UIforETW releases), copy it to your work machine, and then delete the VM.

[randomascii]

There is nothing I can do about this issue. If you can't uninstall the problematic version then install the 10586 version of WPT on another machine (every release of UIforETW comes with that installer) and xcopy the files over to the WPT install directory. You should first delete or rename the existing WPT directory to make sure you get a clean install. That will resolve the problem, but UIforETW can't do that for you - that would be too intrusive and would probably violate the WPT license agreement.