<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/windows-event-log-cleared-think-outside-the-box-0ov0vuywe" -->

---
title: Windows Event Log Cleared? Think Outside the Box | daily.dev
description: Clearing a Windows Event Log does not erase the underlying EVTX file, Arctic Wolf researchers found. During a ransomware investigation, the attacker cleared...
canonical: https://daily.dev/posts/windows-event-log-cleared-think-outside-the-box-0ov0vuywe
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Windows Event Log Cleared? Think Outside the Box | daily.dev
og:description: Clearing a Windows Event Log does not erase the underlying EVTX file, Arctic Wolf researchers found. During a ransomware investigation, the attacker cleared...
og:url: https://daily.dev/posts/windows-event-log-cleared-think-outside-the-box-0ov0vuywe
og:image: https://api.daily.dev/og/posts/0ov0vUYWE.png
og:image:alt: Windows Event Log Cleared? Think Outside the Box
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Windows Event Log Cleared? Think Outside the Box

**[Arctic Wolf](https://daily.dev/sources/arcticwolf)** · 8 min read · 0 upvotes · 0 comments

## Summary

Clearing a Windows Event Log does not erase the underlying EVTX file, Arctic Wolf researchers found. During a ransomware investigation, the attacker cleared the System.EVTX log, but old records remained in slack space within the file, including a command line containing the --pass option and the encryptor's disguised name, svc-host.exe. An EVTX file is always at least 68 KB (a 4 KB header plus a 64 KB data block), and clearing it only truncates data after that first 64 KB cluster. In a second case, a cleared PowerShell EVTX file still held 44 records, only one of which was marked allocated. Most forensic tools don't flag or parse this slack space, so analysts built a proof-of-concept Python script to carve and rebuild the hidden records.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://arcticwolf.com/resources/blog/windows-event-log-cleared-think-outside-the-box>

## Questions this post answers

### Does clearing a Windows Event Log actually delete the event data?

No, clearing a Windows Event Log does not wipe the underlying EVTX file. Windows truncates everything after the first 64 KB cluster and resets the start and end record numbers, but the remaining data in that first 64 KB block stays on disk as recoverable slack space until new events overwrite it.

_Investigators piecing together an incident after log clearing can track forensic techniques like this on daily.dev._

### What is the minimum file size of a Windows EVTX log file and why?

An EVTX file is always at least 68 KB: a 4 KB file header plus at least one 64 KB block holding the event data structures. Even after a clear event resets the log, the file is reset to this 68 KB minimum rather than shrinking further, which is why old record data can remain hidden inside the first 64 KB chunk.

_Forensic analysts digging into EVTX internals can keep up with findings like this on daily.dev._

### Can most forensic tools detect records left behind after a Windows Event Log is cleared?

No, in testing no forensic tool flagged records left in EVTX slack space after a log clear, among tools including Windows Event Viewer, Zimmerman Tools' EvtxECmd, and Magnet AXIOM. One tool could parse events sequentially without relying on the file header, potentially surfacing these records, but it did not indicate whether a record survived a clearing event or predated it.

_Analysts evaluating forensic tooling gaps can follow coverage like this on daily.dev._

## Similar posts on daily.dev

- [My Event Viewer logs were useless until I fed them to Claude — now it catches failures Windows misses](https://daily.dev/posts/my-event-viewer-logs-were-useless-until-i-fed-them-to-claude-now-it-catches-failures-windows-misse-lf7gt7x2d) · XDA Developers · 0 upvotes · 0 comments
- [Fantastic clear-text passwords and where to collect them \(Part 2 - Windows\)](https://daily.dev/posts/fantastic-clear-text-passwords-and-where-to-collect-them-part-2---windows--k6qxogell) · dfir.ch · 0 upvotes · 0 comments
- [Up a Creek Without a Command Line: Mapping an Akira Ransomware Attack](https://daily.dev/posts/up-a-creek-without-a-command-line-mapping-an-akira-ransomware-attack-bhmp0lmjy) · Huntress Blog · 0 upvotes · 0 comments
- [VECT: Ransomware by design, Wiper by accident](https://daily.dev/posts/vect-ransomware-by-design-wiper-by-accident-q85bmpvlz) · Check Point Research · 0 upvotes · 0 comments

---

Tags: [#windows](https://daily.dev/tags/windows), [#ransomware](https://daily.dev/tags/ransomware)

[View this post on daily.dev](https://daily.dev/posts/windows-event-log-cleared-think-outside-the-box-0ov0vuywe)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Windows Event Log Cleared? Think Outside the Box","url":"https://daily.dev/posts/windows-event-log-cleared-think-outside-the-box-0ov0vuywe","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/windows-event-log-cleared-think-outside-the-box-0ov0vuywe"},"datePublished":"2026-11-20T01:25:04.580Z","dateModified":"2026-11-20T01:25:35.971Z","description":"Clearing a Windows Event Log does not erase the underlying EVTX file, Arctic Wolf researchers found. During a ransomware investigation, the attacker cleared...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/55be309c24c07a2d1cc6107fc455ada5?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/55be309c24c07a2d1cc6107fc455ada5?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Arctic Wolf","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Arctic Wolf","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/30920b37616d4d80ad2b810a4b9f6b2e","url":"https://daily.dev/sources/arcticwolf"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/windows-event-log-cleared-think-outside-the-box-0ov0vuywe","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"windows,ransomware","timeRequired":"PT8M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Arctic Wolf","item":"https://daily.dev/sources/arcticwolf"},{"@type":"ListItem","position":3,"name":"Windows Event Log Cleared? Think Outside the Box"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/windows-event-log-cleared-think-outside-the-box-0ov0vuywe#faq","mainEntity":[{"@type":"Question","name":"Does clearing a Windows Event Log actually delete the event data?","acceptedAnswer":{"@type":"Answer","text":"No, clearing a Windows Event Log does not wipe the underlying EVTX file. Windows truncates everything after the first 64 KB cluster and resets the start and end record numbers, but the remaining data in that first 64 KB block stays on disk as recoverable slack space until new events overwrite it. Investigators piecing together an incident after log clearing can track forensic techniques like this on daily.dev."}},{"@type":"Question","name":"What is the minimum file size of a Windows EVTX log file and why?","acceptedAnswer":{"@type":"Answer","text":"An EVTX file is always at least 68 KB: a 4 KB file header plus at least one 64 KB block holding the event data structures. Even after a clear event resets the log, the file is reset to this 68 KB minimum rather than shrinking further, which is why old record data can remain hidden inside the first 64 KB chunk. Forensic analysts digging into EVTX internals can keep up with findings like this on daily.dev."}},{"@type":"Question","name":"Can most forensic tools detect records left behind after a Windows Event Log is cleared?","acceptedAnswer":{"@type":"Answer","text":"No, in testing no forensic tool flagged records left in EVTX slack space after a log clear, among tools including Windows Event Viewer, Zimmerman Tools' EvtxECmd, and Magnet AXIOM. One tool could parse events sequentially without relying on the file header, potentially surfacing these records, but it did not indicate whether a record survived a clearing event or predated it. Analysts evaluating forensic tooling gaps can follow coverage like this on daily.dev."}}]}
```

