violence, frustration, tech
I want to shoot whoever at microsoft decided to make it impossible to deal with a filename with a colon in it. I current have FOUR that I can't do anything about other than to boot into a Linux live CD because literally everything (yes, even the WSL) fails to do anything. Powershell, cmd, WSL, a tool specifically for removing special characters from file names. Everything I've tried has ended in errors.
Windows, this is why I'm leaving you, you stupid little bitch.
violence, frustration, tech
My best shot at fixing this was through a Linux VM in virtualbox, but Virtualbox has decided to be a stupid little bitch as well and won't let me open up any virtual machines.
...
I wonder if VMWare would work...
Or maybe QEMU?
Gods, something has to work without me having to reboot into a linux live cd for these four stupid filenames
Today, I was reminded that Windows filenames are case insensitive. I had a file named "pachli" and a folder named "Pachli" in the same directory, and Windows was throwing fits over it. Thankfully, it let me rename one, though, I tried to rename the folder and it renamed the file. But, that's one less thing to fix from a live CD, so 🤷
It's at this moment I'd like to give a huge shoutout to my past self. THANK YOU for actually bothering to copy your bitlocker recovery key to a flash drive. Without you, I'd have lost almost everything. I owe ya one, Kat