<human>: I've been writing a PowerShell script to find and delete redundant $RECYCLE.BIN files in our thousands of user personal folders.  

The script is going well. It works perfectly fine. It takes a matter of minutes and gives beautiful log and error output info.  

Then I notice that I'm not using the same standardised variable name for the folder I'm trying to clear out, so I edit one of my functions to bring it into line. Great, now the function should use the right variable name.  

I run the script and check my error logs. Instead of the 78 KB file I'm expecting (from previous runs it was that size), I get a 4.9 MB file. Shit.  

I check the file and see that it's got errors like "Unable to delete C:\WINDOWS. Folder not empty". Fuck.  

I check other folders on the server and notice they're also empty. Hardly any files to be found. It's like a digital ghost town.
I check my code again and see that I forgot to change the variable on the line that does the actual deleting:  

    ...
    Remove-Item $Folder\* -Recurse -Force -ErrorAction SilentlyContinue
    ...

The function accepted param([string] $Path), not $Folder.
Instead of PowerShell going "Hey, I see a bug here. Something's wrong, so I'll stop", it goes straight ahead and does a recursive delete from the root of the C: drive. Anything my script was able to delete, it did.  

I immediately owned up to the problem and got our servers and storage manager to see what he could do.  

There was no server image to restore from. The backup software on the server wasn't working because.. I'd deleted it. He first had to install the backup software before attempting to do a restore. The restore is still running. The server will be rebooted tomorrow, and if it's fine it'll be left as-is. If not it'll need to be re-done from scratch.  

No biggie, the server wasn't doing much apart from being required for governmental security compliance..

Could you distill the essence of the text into 1-3 sentences?
<bot>: All it took was a sphinctosecond to recursively delete everything I could on the C: drive of a local government security logging server.