Delta Blog

The idea of copying a Windows 10 install to a new hard drive seems like it should be easy on the outside -- you have the old hard drive, and you just copy it exactly to the new one, not hard, right? As it turns out, very wrong -- while I was able to migrate from a HDD To a SSD in the past, looking back, I was migrating from a 1TB drive to a 1TB drive; and this is not a problem to do with a utility like Gparted, which can be run off a USB. However, today, I was trying to upgrade from a 500GB SSD to a 1TB SSD; and GParted cannot  simply clone the 500GB drive to the 1TB drive -- even if I don't resize anything, Windows still shits the bed. Google was my next stop, and there's plenty of articles which seem to all concur on using some sort of commerical program to clone the drive. But I'm mistrustful of apps which seem to get presented as the "super easy third option" in a guide, moreso if they're called "EasyClone" or some shit like that. As it t...

So, in the name of vanity, I did something rather dumb. I changed my Windows 10 account's username. Not just changing the user's name -- that's cosmetic. I mean, I fully changed the actual username; the goal was to change my root folder path, but as it turned out, this did not work as expected, and all I did was break my Windows 10 login. I started by running the command netplwiz . This let me get my grubby little mitts on my own user account, for which I edited the properties and promptly changed, swapping the username (Which is ancient, from when I first built the computer and went by a different handle on the internet) to a more current one. I saved it, and thought nothing of it. Start Menu then did not work; I tried opening my account settings, and it locked up. I thought a reboot would fix the problem. It made it worse -- Windows 10 home edition tries to sign you in with the last username you used. Which was my old username. So no matter how hard I tried, my...