Xperf - Error 193 and The Trace File does not exist error

[modulexcite]

Whenever I start tracing, I see a couple of errors being logged with Xperf and I'm not able to save the trace buffers either which reports an error "The Trace File does not exist error". Below is the log from UIforETW.

UIforETW Version: 1.41

OS: Windows 7 SP1 Professional

---

wevtutil.exe um "C:\Program Files\UIforETW\bin\etwproviders.man" wevtutil.exe im "C:\Program Files\UIforETW\bin\etwproviders.man" /mf:"C:\Users\TOM~1.GRE\AppData\Local\Temp\ETWProviders.dll" /rf:"C:\Users\TOM~1.GRE\AppData\Local\Temp\ETWProviders.dll"

Starting tracing to in-memory circular buffers... xperf.exe -start "NT Kernel Logger" -on Latency+POWER+DISPATCHER+DISK_IO_INIT+FILE_IO+FILE_IO_INIT+VIRT_ALLOC+MEMINFO -stackwalk PROFILE+CSWITCH+READYTHREAD -buffersize 1024 -minbuffers 600 -maxbuffers 600 -buffering -start UIforETWSession -on Microsoft-Windows-Win32k:0xfdffffffefffffff+Multi-MAIN+Multi-FrameRate+Multi-Input+Multi-Worker+Microsoft-Windows-Kernel-Memory:0xE0 -buffersize 1024 -minbuffers 100 -maxbuffers 100 -buffering _Error 193 starting C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\xperf.exe, xperf.exe -start "NT Kernel Logger" -on Latency+POWER+DISPATCHER+DISK_IO_INIT+FILE_IO+FILE_IO_INIT+VIRTALLOC+MEMINFO -stackwalk PROFILE+CSWITCH+READYTHREAD -buffersize 1024 -minbuffers 600 -maxbuffers 600 -buffering -start UIforETWSession -on Microsoft-Windows-Win32k:0xfdffffffefffffff+Multi-MAIN+Multi-FrameRate+Multi-Input+Multi-Worker+Microsoft-Windows-Kernel-Memory:0xE0 -buffersize 1024 -minbuffers 100 -maxbuffers 100 -buffering _Error 193 starting C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\xperf.exe, xperf.exe -start "NT Kernel Logger" -on Latency+POWER+DISPATCHER+DISK_IO_INIT+FILE_IO+FILE_IO_INIT+VIRTALLOC+MEMINFO -stackwalk PROFILE+CSWITCH+READYTHREAD -buffersize 1024 -minbuffers 600 -maxbuffers 600 -buffering -start UIforETWSession -on Microsoft-Windows-Win32k:0xfdffffffefffffff+Multi-MAIN+Multi-FrameRate+Multi-Input+Multi-Worker+Microsoft-Windows-Kernel-Memory:0xE0 -buffersize 1024 -minbuffers 100 -maxbuffers 100 -buffering Tracing is started. xperf.exe -capturestate UIforETWSession Microsoft-Windows-Win32k:0xfdffffffefffffff+Multi-MAIN+Multi-FrameRate+Multi-Input+Multi-Worker+Microsoft-Windows-Kernel-Memory:0xE0

Saving trace to disk... xperf.exe -flush "NT Kernel Logger" -f "C:\Users\tom~1.GRE\AppData\Local\Temp\kernel.etl" -flush UIforETWSession -f "C:\Users\TOM~1.GRE\AppData\Local\Temp\user.etl" Trace save took 0.0 s Merging trace... xperf.exe -merge "C:\Users\TOM~1.GRE\AppData\Local\Temp\kernel.etl" "C:\Users\TOM~1.GRE\AppData\Local\Temp\user.etl" "E:\etwtraces\2016-08-22_12-25-55_tom.green.etl" Trace merge took 0.0 s Stripping Chrome symbols - this may take a while... python.exe -u "C:\Program Files\UIforETW\bin\StripChromeSymbols.py" "E:\etwtraces\2016-08-22_12-25-55_tom.green.etl" Stripping Chrome symbols took 0.0 s Preprocessing trace to identify Chrome processes... python.exe -u "C:\Program Files\UIforETW\bin\IdentifyChromeProcesses.py" "E:\etwtraces\2016-08-22_12-25-55_tom.green.etl" Finished recording trace.

Stopping tracing... xperf.exe -stop UIforETWSession -stop "NT Kernel Logger" Tracing stopped.

[randomascii]

I'll try to reproduce this tonight on a Windows 7 machine, but there may be something specific to your machine that is causing the problem.

Error 193 appears to be "%1 is not a valid Win32 application." so maybe try running xperf from the command line to see if it works. You should also try running some of the UIforETW batch files, such as etwsamplefast.bat, and metatrace.bat, to see if they behave correctly.

On Mon, Aug 22, 2016 at 9:40 AM, modulexcite notifications@github.com wrote:

Whenever I start tracing, I see a couple of errors being logged with Xperf and I'm not able to save the trace buffers either which reports an error "The Trace File does not exist error". Below is the log from UIforETW.

UIforETW Version: 1.41

OS:

Windows 7 SP1 Professional

wevtutil.exe um "C:\Program Files\UIforETW\bin\etwproviders.man" wevtutil.exe im "C:\Program Files\UIforETW\bin\etwproviders.man" /mf:"C:\Users\TOM~1.GRE\AppData\Local\Temp\ETWProviders.dll" /rf:"C:\Users\TOM~1.GRE\AppData\Local\Temp\ETWProviders.dll"

Starting tracing to in-memory circular buffers... xperf.exe -start "NT Kernel Logger" -on Latency+POWER+DISPATCHER+DISK_ IO_INIT+FILE_IO+FILE_IO_INIT+VIRT_ALLOC+MEMINFO -stackwalk PROFILE+CSWITCH+READYTHREAD -buffersize 1024 -minbuffers 600 -maxbuffers 600 -buffering -start UIforETWSession -on Microsoft-Windows-Win32k: 0xfdffffffefffffff+Multi-MAIN+Multi-FrameRate+Multi-Input+ Multi-Worker+Microsoft-Windows-Kernel-Memory:0xE0 -buffersize 1024 -minbuffers 100 -maxbuffers 100 -buffering

_Error 193 starting C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\xperf.exe, xperf.exe -start "NT Kernel Logger" -on Latency+POWER+DISPATCHER+DISK_IO_INIT+FILE_IO+FILE_IO_INIT+VIRT_ALLOC+MEMINFO -stackwalk PROFILE+CSWITCH+READYTHREAD -buffersize 1024 -minbuffers 600 -maxbuffers 600 -buffering -start UIforETWSession -on Microsoft-Windows-Win32k:0xfdffffffefffffff+Multi-MAIN+Multi-FrameRate+Multi-Input+Multi-Worker+Microsoft-Windows-Kernel-Memory:0xE0 -buffersize 1024 -minbuffers 100 -maxbuffers 100 -buffering Error 193 starting C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\xperf.exe, xperf.exe -start "NT Kernel Logger" -on Latency+POWER+DISPATCHER+DISK_IO_INIT+FILE_IO+FILE_IO_INIT+VIRTALLOC+MEMINFO -stackwalk PROFILE+CSWITCH+READYTHREAD -buffersize 1024 -minbuffers 600 -maxbuffers 600 -buffering -start UIforETWSession -on Microsoft-Windows-Win32k:0xfdffffffefffffff+Multi-MAIN+Multi-FrameRate+Multi-Input+Multi-Worker+Microsoft-Windows-Kernel-Memory:0xE0 -buffersize 1024 -minbuffers 100 -maxbuffers 100 -buffering Tracing is started. xperf.exe -capturestate UIforETWSession Microsoft-Windows-Win32k: 0xfdffffffefffffff+Multi-MAIN+Multi-FrameRate+Multi-Input+ Multi-Worker+Microsoft-Windows-Kernel-Memory:0xE0

Saving trace to disk... xperf.exe -flush "NT Kernel Logger" -f "C:\Users\tom~1.GRE\AppData\Local\Temp\kernel.etl" -flush UIforETWSession -f "C:\Users\TOM~1.GRE\AppData\Local\Temp\user.etl" Trace save took 0.0 s Merging trace... xperf.exe -merge "C:\Users\TOM~1.GRE\AppData\Local\Temp\kernel.etl" "C:\Users\TOM~1.GRE\AppData\Local\Temp\user.etl" "E:\etwtraces\2016-08-22_12-25-55_tom.green.etl" Trace merge took 0.0 s Stripping Chrome symbols - this may take a while... python.exe -u "C:\Program Files\UIforETW\bin\StripChromeSymbols.py" "E:\etwtraces\2016-08-22_12-25-55_tom.green.etl" Stripping Chrome symbols took 0.0 s Preprocessing trace to identify Chrome processes... python.exe -u "C:\Program Files\UIforETW\bin\IdentifyChromeProcesses.py" "E:\etwtraces\2016-08-22_12-25-55_tom.green.etl" Finished recording trace.

Stopping tracing... xperf.exe -stop UIforETWSession -stop "NT Kernel Logger" Tracing stopped.

— 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/85, or mute the thread https://github.com/notifications/unsubscribe-auth/AKTLqTinw1foo2GwTSFmOTZReoiTyJGnks5qidEHgaJpZM4JqEMg .

Bruce Dawson

[modulexcite]

Sorry, it seems to be an issue with XPerf, Performance Recorder and WPA. They are not working on my machine, the reported error when I try to launch them is "it's not a valid win32 application". This might have been caused by the latest Visual Studio Update 3 on my machine. I'm not sure how to fix it besides re-installing the Windows kits. Any help would be greatly appreciated, thanks.

[randomascii]

That error sometimes indicates a 64-bit executable on a 32-bit machine. The automatic installation of the latest UIforETW is only supposed to happen on 64-bit Windows because I only package the 64-bit version, but if the 64-bit version somehow accidentally got installed then that would explain your problems.

I don't think you can reinstall the Windows kits, or uninstall them, but you can install the correct version on another machine and then xcopy them over.

On Mon, Aug 22, 2016 at 12:57 PM, modulexcite notifications@github.com wrote:

Sorry, it seems to be an issue with XPerf, Performance Recorder and WPA. They are not working on my machine, the reported error when I try to launch them is "it's not a valid win32 application". This might have been caused by the latest Visual Studio Update 3 on my machine. I'm not sure how to fix it besides re-installing the Windows kits. Any help would be greatly appreciated, thanks.

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

Bruce Dawson

[modulexcite]

I apologize for reporting it as an error/issue here, I should have tried your recommendations first before doing that. Thanks.

[modulexcite]

I'm using a Windows 7 64-bit OS. And regarding reinstalling the SDK, can't I just run repair from Programs and Features which does provide me with options for Repair/Change/Reinstall? Thanks.

[randomascii]

No worries.

On Mon, Aug 22, 2016 at 1:03 PM, modulexcite notifications@github.com wrote:

I apologize for reporting it as an error/issue here, I should have tried your recommendations first before doing that. Thanks.

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

Bruce Dawson

[randomascii]

I don't know. I've observed that the WPT MSIs cannot be uninstalled, but I'm no expert on that. A repair may well work. Failing that, xcopy from a good install.

On Mon, Aug 22, 2016 at 1:08 PM, modulexcite notifications@github.com wrote:

I'm using a Windows 7 64-bit OS. And regarding reinstalling the SDK, can't I just run repair from Programs and Features which does provide me with options for Repair/Change/Reinstall? Thanks.

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

Bruce Dawson

[modulexcite]

Ok thanks will give it a try and post my results here. 

[mwinterb]

"not a valid Win32 application" is also the error if the subsystem version specified in the PE header is greater than what's supported by the OS.

C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit> dumpbin /headers xperf.exe | findstr subsystem 6.02 subsystem version 3 subsystem (Windows CUI)

6.02 lines up with Windows 8. The end result for @modulexcite is the same, though.

[randomascii]

That's curious and disappointing. I've had other reports of the new WPT not working on Windows 7, although I thought I had checked that. I guess not.

So, an xcopy install to get the older version is probably necessary. And if VS 2015 Update 3 is installing an incompatible version on Windows 7 then that is a VS bug.

I'll probably add some version checks tonight to avoid causing this problem myself.

On Mon, Aug 22, 2016 at 4:55 PM, mwinterb notifications@github.com wrote:

"not a valid Win32 application" is also the error if the subsystem version specified in the PE header is greater than what's supported by the OS.

C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit> dumpbin /headers xperf.exe | findstr subsystem 6.02 subsystem version 3 subsystem (Windows CUI)

6.02 lines up with Windows 8. The end result for @modulexcite https://github.com/modulexcite is the same, though.

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

Bruce Dawson

[randomascii]

I got confirmation that WPT does not work on Windows 7. The next release will have the installer tagged to prevent installing on incompatible operating systems.

If WPTx64 was installed by UIforETW instead of installed as part of the Windows SDK then there should be a separate uninstall entry for it.

However UIforETW wlil try to reinstall it the next time you run it. I'll fix that tonight.

On Mon, Aug 22, 2016 at 5:01 PM, Bruce Dawson brucedawson@google.com wrote:

That's curious and disappointing. I've had other reports of the new WPT not working on Windows 7, although I thought I had checked that. I guess not.

So, an xcopy install to get the older version is probably necessary. And if VS 2015 Update 3 is installing an incompatible version on Windows 7 then that is a VS bug.

I'll probably add some version checks tonight to avoid causing this problem myself.

On Mon, Aug 22, 2016 at 4:55 PM, mwinterb notifications@github.com wrote:

"not a valid Win32 application" is also the error if the subsystem version specified in the PE header is greater than what's supported by the OS.

C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit> dumpbin /headers xperf.exe | findstr subsystem 6.02 subsystem version 3 subsystem (Windows CUI)

6.02 lines up with Windows 8. The end result for @modulexcite https://github.com/modulexcite is the same, though.

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

Bruce Dawson

Bruce Dawson

[randomascii]

I can't test until I get home but I think this (once packaged with two MSIs) will do the trick, including warning users who have installed the wrong version.

https://codereview.appspot.com/304470043

On Mon, Aug 22, 2016 at 6:01 PM, Bruce Dawson brucedawson@google.com wrote:

I got confirmation that WPT does not work on Windows 7. The next release will have the installer tagged to prevent installing on incompatible operating systems.

If WPTx64 was installed by UIforETW instead of installed as part of the Windows SDK then there should be a separate uninstall entry for it.

However UIforETW wlil try to reinstall it the next time you run it. I'll fix that tonight.

On Mon, Aug 22, 2016 at 5:01 PM, Bruce Dawson brucedawson@google.com wrote:

That's curious and disappointing. I've had other reports of the new WPT not working on Windows 7, although I thought I had checked that. I guess not.

So, an xcopy install to get the older version is probably necessary. And if VS 2015 Update 3 is installing an incompatible version on Windows 7 then that is a VS bug.

I'll probably add some version checks tonight to avoid causing this problem myself.

On Mon, Aug 22, 2016 at 4:55 PM, mwinterb notifications@github.com wrote:

"not a valid Win32 application" is also the error if the subsystem version specified in the PE header is greater than what's supported by the OS.

C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit> dumpbin /headers xperf.exe | findstr subsystem 6.02 subsystem version 3 subsystem (Windows CUI)

6.02 lines up with Windows 8. The end result for @modulexcite https://github.com/modulexcite is the same, though.

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

Bruce Dawson

Bruce Dawson

Bruce Dawson

[modulexcite]

@mwinterb is right, I did get similar results from the header files. However, on my machine I can confirm that the latest Windows Kit was installed as part of Visual Studio Update 3 and not by UIforETW. I'll try to get that uninstalled although my fear is that it might corrupt the Visual Studio installation.

@randomascii if you dont mind me asking where did you get the confirmation from that WPT does not work on Windows 7 as I didn't find anybody else reporting the issue upon google search?

[randomascii]

I have excellent contacts at Microsoft and they confirmed the issue.

I filed a bug for VS 2015 installing an incompatible version of WPT. Please comment/star as appropriate:

https://connect.microsoft.com/VisualStudio/feedback/details/3076739

On Mon, Aug 22, 2016 at 6:51 PM, modulexcite notifications@github.com wrote:

@mwinterb https://github.com/mwinterb is right, I did get similar results from the header files. However, on my machine I can confirm that the latest Windows Kit was installed as part of Visual Studio Update 3 and not by UIforETW. I'll try to get that uninstalled although my fear is that it might corrupt the Visual Studio installation.

@randomascii https://github.com/randomascii if you dont mind me asking where did you get the confirmation from that WPT does not work on Windows 7 as I didn't find anybody else reporting the issue upon google search?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/UIforETW/issues/85#issuecomment-241604230, or mute the thread https://github.com/notifications/unsubscribe-auth/AKTLqSL8i31VK0t9UYl9xRT7yOcmmd1Lks5qilI6gaJpZM4JqEMg .

Bruce Dawson

[modulexcite]

great, thanks for reporting the issue. Any ideas on how to get this resolved without corrupting VS or if the VS team is planning on releasing a fix for this?

[randomascii]

I'd do an xcopy repair for now - copy the 10586 version over top. It seems unlikely that that could cause any problems for VS. It's probably safer than mucking around with uninstalls.

But that's just an educated guess.

On Mon, Aug 22, 2016 at 7:08 PM, modulexcite notifications@github.com wrote:

great, thanks for reporting the issue. Any ideas on how to get this resolved without corrupting VS or if the VS team is planning on releasing a fix for this?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/UIforETW/issues/85#issuecomment-241606625, or mute the thread https://github.com/notifications/unsubscribe-auth/AKTLqXZN7gxgSa_CAx7G7ycz1dTYsSkCks5qilYggaJpZM4JqEMg .

Bruce Dawson

[modulexcite]

Sorry to keep bothering you with this! Can I just run the installer under oldwpt10 folder to install the older version of windows 10 kit now?

[randomascii]

I just uploaded a new release of UIforETW - v1.42. Can you give it a try?

If you run it on Windows 7 it should tell you that your version of WPT is too new. It will then tell you that you need to uninstall WPT. If you uninstall WPT and then run UIforETW again it should install the old version.

I doubt you can install the old version without first uninstalling the new one.

If you can't uninstall the new one then you probably have to xcopy the old one over top of it, I would guess.

On Tue, Aug 23, 2016 at 9:38 AM, modulexcite notifications@github.com wrote:

Sorry to keep bothering you with this! Can I just run the installer under oldwpt10 folder to install the older version of windows 10 kit now?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/UIforETW/issues/85#issuecomment-241794922, or mute the thread https://github.com/notifications/unsubscribe-auth/AKTLqabKWoRcijF4BEdZesqMjCkdnilUks5qiyIdgaJpZM4JqEMg .

Bruce Dawson

[modulexcite]

Yes it does display a warning, I was talking about the installer located under the "oldwpt10" folder from the new release.

You're right, I can't run the old windows 10 sdk setup downloaded from microsoft website without uninstalling the new version installed by Visual Studio. I was just wondering if I could just run the installer under that "oldwpt10" folder from the new release without doing so.

Anyway, I'll go ahead and uninstall the new WPT version installed by VS.

[randomascii]

You can run the oldwpt10 installer, I just doubt that it will work.

Microsoft wants installer logs for the bug about VS 2015 installing the incompatible WPT on Windows 7. I have never seen the bug so I don't have installer logs - can you gather some? The bug is:

https://connect.microsoft.com/VisualStudio/feedback/details/3076739/vs-2015-installs-the-10-0-14393-wpt-on-windows-7-where-it-doesnt-work

On Tue, Aug 23, 2016 at 10:08 AM, modulexcite notifications@github.com wrote:

Yes it does display a warning, I was talking about the installer located under the "oldwpt10" folder from the new release.

You're right, I can't run the old windows 10 sdk setup downloaded from microsoft website without uninstalling the new version installed by Visual Studio. I was just wondering if I could just run the installer under that "oldwpt10" folder from the new release without doing so.

Anyway, I'll go ahead and uninstall the new WPT version installed by VS.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/UIforETW/issues/85#issuecomment-241803761, or mute the thread https://github.com/notifications/unsubscribe-auth/AKTLqUTZQCyLyOWiskImWOY2HGh9yDG3ks5qiyjxgaJpZM4JqEMg .

Bruce Dawson

[modulexcite]

Ok thanks. I'll try to get those logs Microsoft is asking.

[randomascii]

The other report of problems on Windows 7 has been updating me on twitter. I'm sharing their latest tweet in case it is of interest:

https://twitter.com/jcalsbeek/status/768212103454863360

On Tue, Aug 23, 2016 at 10:18 AM, modulexcite notifications@github.com wrote:

Ok thanks. I'll try to get those logs Microsoft is asking.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/UIforETW/issues/85#issuecomment-241806859, or mute the thread https://github.com/notifications/unsubscribe-auth/AKTLqZjySlpL7rDzUgGlg2zhDLKE5aPgks5qiytcgaJpZM4JqEMg .

Bruce Dawson

[modulexcite]

Thanks for that info.

[modulexcite]

I did an xcopy of the WPT from a new machine instead as uninstalling didn't work for me. Unfortunately, I will not be able to post the logs requested by the VS team as my company's policy doesn't allow disclosing the kind of information that tool collects.

[MagicAndre1981]

the 1607/14393 WPT doesn't work on Win7 (only Win8 - Build 9200 onwards (8.1, 10))

[randomascii]

Microsoft seems to confirm that VS 2015 Update 3 is installing the 10.0.14393 version of WPT on Windows 7, which is bad. https://connect.microsoft.com/VisualStudio/feedback/details/3076739/vs-2015-installs-the-10-0-14393-wpt-on-windows-7-where-it-doesnt-work

UIforETW no longer does this, as of 28725f10cd, so I'm closing this issue as fixed.