Okay, so after some time, which was much less than I expected, windows offered me (okay, not offered, it started downloading the moment I did “check for updates”) the Creator’s fall update (or what’s the exact wording).

Now before I go on about how that went (though the title gives it away), I need to mention that I was waiting much longer for the spring update, which made sense. My PC is getting close to its 6th birthday (bought after Christmas 2011) with a help of friend as mix-and-match of components to give me stronger where I would need it and save where I would not (student’s budget…). It included said friend’s used HDD (for him, 1TB+ was necessary while for me the old 750GB was at least two times more than enough). Said HDD was the first to be replaced, over time followed by power source and graphic card, so now it’s a mix of components of varying age, up to 6 years.

For that very reason, I expected it’ll take months before the Fall update is offered to me, but it came quite fast. I let it do its thing and as my father was home, I just went to Uni as usual, hoping that when I come back home, it’ll be finished.

Well, it was. But even the very basic functions were failing massively. First, it somehow splintered the account settings, adding a Schrödinger’s copy of my default account that was not visible in settings, but was active, with all my settings now on default for this ‘new’ account. So, I started to put things back in normal, and in time, Start button (including through the Windows key) stopped reacting. Eventually, even folder browsing was starting to behave weirdly, and so I decided to use the restore to roll back the update.

NOPE!

The Schrödinger’s account thing completely blocked that. It asked me to remove the newly created account, sending me to settings – where it could not be seen.

Long story short, three hours later I decided that there’s only one solution: Format the whole C: drive and make clean W10 install, only getting to the spring update and then blocking the Fall (from now on to be called Fail) update. I am now sitting here, installing some essential programs and drivers while waiting for W10-1703 update to download (Not sure which big pack it was, but I know that FAIL is 1709 and I believe the working one before is 1706).

Oh, one thing: before I started the reinstall later today, I went to the hills, my favorite ultimate solution. It cleared my mind, which is nice.

With that, I end this post and go back to installing stuff.