Why Is My Firewall Blocking Everything -

Then I checked the audit log. Timestamps from 3:17 AM. Every two seconds, an entry: “Filtering platform policy change.” And then, at 3:18 AM: “Windows Filtering Platform base filtering engine stopped.” Restarted at 3:19 AM with a new configuration. The configuration had exactly one rule:

I went downstairs. Knocked. No answer. The door was unlocked.

I didn’t have a “she.” I lived alone. My last relationship ended two years ago. But the driver was real. It was running. It had full network stack interception. And it was updating itself every night at 3:17 AM from an IP address that geolocated to… my own apartment building. The apartment directly below mine. why is my firewall blocking everything

The third line: “SHE WILL COME BACK IF YOU DO.”

I dug into the Windows Filtering Platform callouts—deep kernel stuff. That’s when I found it: a tiny, unsigned driver named bxdiag.sys . No manufacturer. No version. Creation date: tomorrow. Not last week. Not today. Tomorrow. Then I checked the audit log

Inside, there was no furniture. No bed, no chair. Just a single desk with a monitor showing my desktop—live. The same alerts I saw on my screen, mirrored on hers. And next to the monitor, a photograph of me sleeping, taken from inside my bedroom closet. The date stamp was from three nights ago.

I ran a rootkit scan. Nothing. Malwarebytes: clean. System file checker: no integrity violations. So it wasn't a virus. It was something stranger. The configuration had exactly one rule: I went downstairs

I rebooted into safe mode, disabled the firewall, and the internet roared back to life. So the problem wasn’t the network. It was the firewall itself. But why? I hadn’t changed any rules. I hadn’t installed new security software. It was the same basic Windows Defender Firewall I’d ignored for three years.