-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KeyError: 138 #41
Comments
i can reproduce this issue using the provided .evtx file, though unfortunately, my local system doesn't exhibit this unexpected node type. i'll continue to search for public evtx files that demonstrate the issue. |
note:
this is possibly array (0x80) of QWORD (0x0A)
|
this has been tricky to track down. still working on it. |
In its opening momentum, Microsoft has not documented its file format ? |
Hi Willy
Thank you. |
thanks also to @limonidisicilia for providing a sample .evtx file. i'm able to reproduce this issue, but haven't yet figured out how the data is supposed to be parsed. the immediate "solution" is to register an exception handler, log the raw data, and skip the record. long term, I might be able to figure out the binary format (and/or will happily accept patches!). |
python-evtx seems to struggle with many WindowsX evtx files, to name a few: as a workaround I'm using Powershell: |
hi Willy,
I've this issue with
evtx_dump.py
onMicrosoft-Windows-Ntfs%4Operational.evtx
file (from Windows 10) :the evtx file
Microsoft-Windows-Ntfs%4Operational.evtx
seems to be ok because it is correctly exported from Windows : I send you the exported and the original evtx file...regards, lacsaP.
The text was updated successfully, but these errors were encountered: