|Windows 10 upgrade woes||Tuesday 11th August 2015|
Don't let anybody tell you that Windows 10 is a free upgrade. To upgrade my PC it cost me three entire evenings and a slightly annoyed wife.|
In order to get the free upgrade, you have to upgrade from inside Windows (7, 8 or 8.1). Anybody who has worked with computers for even a small amount of time will tell you - never upgrade an existing installation, always do a clean install.
Previous Windows upgrades allowed this, providing you had an older version of Windows already on disk, or had a previous CD-key, you could do a clean install. Microsoft, in their infinite wisdom, have changed things and disallowed this. There is still an upgrade option in the DVD boot, but it just tells you to go back into Windows and do it from there.
True as ever, upgrading didn't go well. I ran the setup program, it downloaded the data and did the first reboot - and I was promptly presented with a blue-screen:
A required device isn't connected or can't be accessed.
Error code: 0xc00000bb
The only option is to continue back into Windows 8.1; to which I am then presented with an even more useless message:
0xC1900101 - 0x20017
Super! Thanks Microsoft. My suspicions went immediately to my installation drive being an Intel 750 PCIe SSD, and not your standard SATA affair. So then started my long quest with Microsoft. Using the "Answer Desk" online chat, this is a slow process as I suspect the operators are juggling more than one chat. Still, it avoids phone bills and lengthy sitting around with a phone to your ear.
It wasn't long before the helpdesk lass was on my computer trying things out. She wanted to go through the motions so that evening was spent trying different ways of installing it. I started with the DVD iso, but they wanted to try via Windows Update (it didn't work) and then went onto the Media Creation tool, which downloaded to USB - at this point, they realised that USB upgrade isn't supported, so started it again. Each time having to download 3GB of data. At one point I seemed to have picked up a slow server and the download would have taken 12 hours, luckily restarting it picked up speed - I am lucky enough to have reasonably good broadband.
After a few token things were changed around the helpdesk advisor was feeling confident that it would work so I tried again - naturally it failed, but her confidence was so high that she had terminated the support session so I couldn't get back in contact with her.
This meant starting again with another helpdesk contact, despite having a case number they wanted to go through the motions again - I managed to convince them to jump a few steps and was passed onto second-line, who told me that it wasn't an issue with the upgrade and my system was corrupt and it would work if I did a clean install of Windows 8.1.
Due to apathy, I waited a couple of days before trying this - but sure enough, it didn't work. And I started the conversations anew with another advisor, who also went through the motions before agreeing to get me back in contact with second line; although this time there was a 72 hour wait for a call-back from them.
My final conversation with second line started at 6pm and ended just before 10pm. As you can guess, it involved going through the motions of re-downloading and re-running. It was when I was told I'd probably have to get a local IT technician to have a look I lost my patience. I explained what I do for a living, and what I thought the problem was; it didn't take long for the engineer to agree that a clean install would probably be the best and he'd see what he could do about getting a CD key.
I did the install from scratch and it worked fine, an hour later I got a call back with a CD-key - it turned out that the engineer had to spend the best part of forty minutes convincing his manager that this was the right approach and provide evidence that in-place upgrade wasn't working.
Thumbs up to the second-line engineer for fighting my corner, but a big thumbs down that Microsoft made this so hard for him (and me, as a customer).
If you're reading this as somebody who has the same error, I'm sorry to say that there is no quick fix, you'll probably have to go through the motions with Microsoft to try and get a CD-key for Windows 10.
My next approach would have been to install Windows 8.1 onto a SATA drive, upgrade to 10 and then transfer the image over to the PCIe SSD and hope that activation wouldn't throw too much of a wobbly.
|Sony Vaio SVS13 & Windows 10||Monday 3rd August 2015|
I'm in the unfortunate position of owning a Sony Vaio laptop, an SVS13A1C5E to be specific (catchy name, I know). It's a cracking laptop and great value for money; at the time if you wanted a lightweight 13" laptop with a dedicated GPU it was Sony, Dell, HP or Apple, with Sony coming in the cheapest with some nice features to boot such as bluray. The unfortunate part being that Sony has canned the Vaio line and has stopped selling computers. Whilst they are committed to supporting existing customers, this doesn't include things like updating drivers and providing support for Windows 10.|
So Windows 10, my installation was a bit of a fluke, with numerous hard-reboots and rollbacks until it magically worked. Installing drivers for the Sony has always been a challenge for things like the ambient sensor and fingerprint scanner, the most troublesome feature being the touch-pad. Upon resume from sleep the mouse wouldn't work. Interestingly Windows Update had automatically installed Synaptics driver for the touchpad - removing this solved the problem, but also meant I was a little restricted (being a "clickpad" and not a "touchpad" there are no physical buttons).
Lucky for us, this hyped up Windows "It's so significant we've jumped a version" 10 is actually fairly similar to Windows 8.1, which was pretty much identical to Windows 8 which was essentially the same as Windows 7, which wasn't vastly removed from Vista. In terms of drivers and how things work underneath, at least.
For a successful installation of the Sony you need to just treat it like Windows 8.1. Install all the Windows 7 drivers where you can (which can be downloaded from the Sony support web-site), followed by the Windows 8 drivers, followed by the Windows 8.1 driver.
The only driver that I struggled with was the Sony Firmware Parser, for this to work I ran the installer and then opened the temporary directory the installer was running from and manually installed the driver into device manager (I just tried each unknown device until one matched up).
The mouse issue was cleared up by using the Windows 7 driver, which is a Synaptics ClickPad v22.214.171.124 from August 2012. It seems to work like a charm and you can edit the registry to add middle click to 3-finger tap.
I should now be able to get on with poking around Windows 10 and discovering just how little impact the UI changes actually have on my day-to-day usage.
One thing I have noticed is that with all this touch-enabled effort, accessibility for the keyboard seems to have reduced. It used to be entirely feasible to navigate around Windows, including interacting with context menus and the desktop with just the keyboard. Things are a lot more trickier if you have a dead mouse on Windows 10.