We're back again. I ain't fucking around this time. Go read the last part if you don't know what I'm talking about. Windows 10. We all know it. Some of you probably use it at home to read this. I don't, I'm one above you. Pioneered in some stuff. Ask Bill Gates, I don't know. Anyways, even though this will absolutely destroy my hard drive space, I'm here to corrupt it once again using our trustworthy* methods.

*methods in question are debatable on their efficiency.

The plan this time is even simpler. Boot up VMWare Workstation, install Windows 10, be le epic cool gamer and rain down hell upon it as we know it. Sounds simple, I'm sure this is not gonna absolutely ruin my time. I don't go back and edit this, so this is either subtle foreshadowing or my prediction. Same preperations as last time, infact, it's so similar I'm not even gonna replace the image below. Yeah, I'm reusing content. I'm lazy, boohoo. This time is a little more convoluted though, because it's bigger and also has a chance to just BSOD since NT is a crybaby unlike DOS which sucks it up. I think. Except when you try "c:\con\con" on 95RTM or whatever.

Don't lie. You're familiar with this. This is HxD. Hex Editor. How simple. I'm not gonna repeat my words, but this has a handy Fill Selection feature which vomits hex soup into the file. What does it do? Corrupts it. How badly? Not too badly unless you score lucky. I hate the OOBE. It takes eight "No"'s or "Skip"'s' to get to a usable desktop experience without Billy B. Gateathanlous spying on you, yet he does it anyway.

After battling with VMWare and Broadcom's inability to retain software support for more than 2 seconds, I finally have a working and not sluggish virtual machine due to the presence of VMWare Tools. I feel accomplished and yet now I'm sitting here ready to shoot it. Reminds me of that one Breaking Bad scene. I named my user "LPT2 Gamer" in honour of the previous 98 machine that no longer boots, because I had already tried this with LPT1 Gamer and failed.

Sigh, okay, let's backup the VMDK and start super slamming it like it's the 1996 movie, "Space Jam." You know what they say, it's time to slam now or something. The VMDK itself is 12GB. This is going to be super fun to edit and backup. Welp, it's done, so let's start doing the thing I love and enjoy. Random selection and shooting. Keep in mind, HxD automatically makes backups and has to save the whole file. This takes longer than you think because of the fat fuck being 12 whole gigabytes. But, we're done, so let's power it on and see what happens. And, to the surprise of like, two people, nothing. Yeah, thank fuck Microsoft Solitaire Collection is okay and unaffected. I think I'd start sobbing otherwise.

After a while of corrupting, I eventually had the kernel shaking in its NT boots and it failed to load. Okay, that's expected. Surely Safe Mode would fix this all, considering Windows couldn't. Pressing F8, and, holy shit. Take a look yourself. That is incredibly comedic.

I am DETERMINED to get SOMETHING to happen. I am on my last threads of patience here watching Automatic Repair do nothing and then be unable to boot. I have to know what Windows 10 acts like when it's fucked. Until something did happen. I lost the blur on the login screen. What a change. Infact, I actually lost all blur, including the taskbar. Until it actually decided it didn't like itself no more. It really started to break.

..but, we are BREAKING down Windows by it's THROAT. Really breaking it down for you, Mark. I feel accomplished, FINALLY. It's doing something! Settings REALLY causes it to freak out. Infact, most UWP apps do. Except for fucking Solitaire collection. Why, out of all UWP apps, that's the one that remains functional?!

I feel so happy. I've never been happier to see Windows shit itself. I feel 0x5 might be a good offset to start off. Let's continue on by backing up the current VMDK so I keep this absolute mess. I love this. I feel happy.

Going on, I corrupted some more and got logged in. Until Explorer didn't launch itself. Okay, open Task Manager, until.. what? I can't- what? I can't run Explorer on my own system? The fuck? This is the type of error you get trying to run i.e a 16-bit application on 64-bit, and I was getting it for explorer.

Until I tried to run explorer.exe from cmd. Holy shit, it actually thinks it's a 16-bit application. That is the most fucked I've ever seen explorer be. Okay, I'm a surgeon. I can fix this. Let me try copying a copy of explorer for Windows 10 onto the machine and copying it back. After careful surgery, we're back in business. You know what that means! Straight back to HxD we go!

I decided to make another backup at this point. I really wanted to break it as much as possible without losing all my progress; it was so broken at this point it'd be insulting to start over again. So I persisted! Eventually, I checked my Windows version. Just to check it wasn't having another identity crisis.

Hm. Very sadly, though, I deleted the working VMDK. Permanently. After restoring and replacing the working one with a non-working one thinking it was the working one. It's so over, say a sad goodbye to LPT2 Gamer. Though, I will say, I've been at this for about five hours at this point. This might be a sign. My final conclusions? Stick with DOS-based Windows, holy shit. That was actual pain and suffering all for a few laughs because Windows sucks