7: kd> !wmitrace.logsave x.etl
WMI Trace Save: Debugger Extension. LoggerId = -1, Save File = 'LogData.etl'
Failed to Find Logger
7: kd> !wmitrace.search
wmitrace has no search export
I don't know much about Windbg either. So I've been doing some research but I haven't gotten anything...Not at all something I have worked with (full disclosure).
I wrote a code in C# for administrator access and adapted it for powershell, but nothing changed. Probably I needed to set additional permissions for the folder when selecting it from the folder, but even if I did that, the corrupted warning would not change. I adapted a different dump but it kept giving the corrupted warning. I don't think there is a corruption.First:
Do you have any way to test your code on an applicable file that you know you have admin access and that the file is not corrupted in some manner?
I also tried a command for the file location and the result failed again. For the !wmitrace.logsave command I did exactly what microsoft wrote. When I put different names instead of "X", the same error persisted. I can't understand it unfortunately.Noted that "x.etl" - the "x" seems unsual. Should it be a wildcard "*"?
What about the path to the required to the file? Is the full path included elsewhere in your code?
It probably can't preview because the file size is too big (Not too much)Could not view the memory dump. Re: "problem with the preview".
I saw it while doing research, but it contains definitions. I think.
You need to provide the name of the logging source or Id for which you're trying to export.WMI Trace Save: Debugger Extension. LoggerId = -1, Save File = 'LogData.etl' Failed to Find Logger
!wmitrace.logsave 2 C:\Users\<user name>\Desktop\Trace.etl