WPT: Updated version of “Windows Performance Toolkit” 8.1 update from the ADK or SDK.

WPT: Updated version of “Windows Performance Toolkit” 8.1 update from the ADK or SDK.

  • Comments 2
  • Likes

Hi all,

For those of you that are using the “Windows Performance Toolkit” actively in your troubleshooting, here is an update regarding the tool.

For those of you that missed, here are the two blog posts regarding installing and capturing data with the tool:

WPT: Installing the Windows Performance Toolkit v5.0 (WPRUI, WPR, Xperf)

WPT: WPR/Xperf: Capture high cpu, disk i/o, file, registry, networking, Private bytes, Virtual bytes, Paged Pool/Nonpaged pool and/or application slowness.

As of April 2014, our Product Group released the “Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1 Update”

http://www.microsoft.com/en-us/download/details.aspx?id=39982

Please go ahead and download the tool.

It contains new bits and added features.

The confusing part is that the WPRUI/WPR/WPA are the same version 6.3.9600.16384.

 

image 

WPT v5.0 (from ADK/SDK 8.0)

image

WPT v5.1.0 (from ADK/SDK 8.1)

image

WPT v5.1.1 (from ADK/SDK 8.1 Update 1)

17 files that are updated and 1 new file that was introduced.

 

clip_image001

Left = updated 8.1 Update 1 version Right = original 8.1 version.

On the upcoming posts, I’ll be covering more in-depth some of the items that we went over in TechEd 2014 Americas.

Windows Performance Deep Dive Troubleshooting

http://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/WIN-B413#fbid=

And for those folks at TechEd that asked about the Custom measurements, I’ll be posting them here in this blog.

I hope this helps and I hope that you enjoy,

Yong Rhee

Comments
  • When performing a boot trace with WPT v5.1.1 (from ADK/SDK 8.1 Update 1) on Win7x64, I'm receiving the error 0x8004e001 after logging back into Windows during its "gathering system information for on/off - boot trace" phase. Looking up the error message appears to be a dead end. Known issue?

  • In Windows 7 and Windows Server 2008 R2, there can only be 1 “NT Kernel Logger” “Event Trace Session” (ETS).

    Make sure that you are not running any other tools/apps that are using the “NT Kernel Logger” ETS.

    What other tools/apps use the "NT Kernel Logger" ETS?
    Sysinternal tools such as ProcExp/ProcMon/TCPView, etc...

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment