The two experiences could not have been more different.
Before the update, the home system was running Windows 7-Pro-current, while the office laptop was running 8.1-Pro-current. Updating the home computer went very smoothly with the exception of some hardware issues that I was aware of ahead of time. But pretty much everything has worked out of the box in this environment, and the wife has not been exceptionally vocal with her complaints about the new interface. So that system, anyways, can be counted as a success.
The office laptop, on the other hand, hasn't been a nightmare but it is presenting a steady trickle of stupid little almost problems that might or might not be Windows 10's fault and might not and frankly I'm getting sick of it.
I even did this upgrade "correctly": I formatted the C: drive and installed the OS fresh. No "upgrade", this was more of a "complete fresh installation". All of my applications were then downloaded and freshly installed.
And since then, I have had problems like:
- The FortiNet VPN doesn't work. Oh unless you reboot, then it works again.
- VMware VI Client won't install. But if you download it three times, maybe the third try will be successful. If you reboot before trying the download. And this is the case for each of the three or four different versions of the VI Client I need to install.
- Chrome goes off into space. Yeah, it might be Chrome being Chrome, but Chrome is being Chrome far more frequently under Windows 10 than it did under Window 8.1.
- Windows key randomly stops working.
- Windows-key shortcuts randomly stop working. But no worries, a reboot will fix that, right?
- Dealing with situations where IP addresses are changing back and forth frequently (something I have to do fairly often because part of my job is networking and troubleshooting/verification thereof. If you flip back and forth between two networks, or static and dhcp, then occasionally the networking stack will just go off into space and you are screwed. Yes, the same thing happens under 7/8//8.1. But so far my experience is that W10 at least isn't any better, and might be worse.
What is it with all the rebooting. This isn't Windows 95, this kind of turning-it-off-and-on-again bullshit isn't acceptable any more. It is 2015 for fuck's sake.
I also have the impression that there are more Windows Updates happening that require reboots. I suspect this is due to the newness of the OS, and Microsoft is steadily, if stealthily, rolling out the updates required to fix some of the problems I am complaining about.
Plus the usual Outlook/Outlook confusion which seems even more ingrained in W10 than it was in previous versions.
Part of this is undoubtedly the fact that I use the home system for maybe a couple hours a week, much of that playing Kerbal Space Program, while I use the laptop all day every day and when a problem crops up it is invariably an impediment to something I'm trying to get done right now. I am sure that sense of urgency and stress only adds to the negative view that Windows 10 gets as a result.
I also have the impression that there are more Windows Updates happening that require reboots. I suspect this is due to the newness of the OS, and Microsoft is steadily, if stealthily, rolling out the updates required to fix some of the problems I am complaining about.
Plus the usual Outlook/Outlook confusion which seems even more ingrained in W10 than it was in previous versions.
Part of this is undoubtedly the fact that I use the home system for maybe a couple hours a week, much of that playing Kerbal Space Program, while I use the laptop all day every day and when a problem crops up it is invariably an impediment to something I'm trying to get done right now. I am sure that sense of urgency and stress only adds to the negative view that Windows 10 gets as a result.
It is also entirely possible that my problem isn't that Windows 10 isn't ready for my tools, it is that my tools are not ready for Windows 10. Either way, the immediate solution to the problem is the same: get rid of Windows 10.
I said in a tweet: