UTC vs local timestamp variances in tools
See original GitHub issueEvtxECmd version # I am running EvtxCmd version 1.0.0.0
Describe the bug
If I run EvtxCmd at 12:00 without specifying an output file name, the generated file has a name such as 20220615100000_EvtxECmd_Output.csv
. If I run it with others EZTools in a powershell loop, all others default output file names are like 20220615120101_LECmd_Output.csv
. @ro-olivier identified the same behavior on its end.
To Reproduce
The exact command executed is .\EvtxECmd.exe -d .\C\Windows\System32\winevt\Logs\ --csv .\output\EventLogs
with a fresh install of all EZTools.
Expected behavior
I expect the timestamp to be 20220615100000_EvtxECmd_Output.csv
Additional context My timezone is GMT + 2 / UTC+1
Possible explanation I suspect there are some time conversion between UTC and local timezone that somehow affected also the file name ?
Issue Analytics
- State:
- Created a year ago
- Comments:6 (5 by maintainers)
Top GitHub Comments
this is done
yea thats my bad. should have all been UTC from the get go. if you notice any others please let me know