So, contrary to previous marketing, Windows 10 will not be the last release… there’s at least one more. And yes, all the mis-features like requiring an Internet connection and the insistence on cloud services, they’re turning it up to 11. I give you…
… Come now, Microsoft… are you telling me your operating system just makes up its own error codes? How can the error code be “unknown”? The computer is doing what you told it to do!
Moreover, why can’t you fix your broken links? Clearly the error I’m getting is not any of the ones you’ve listed, so why even offer them as suggestions?
Well, it seems the updates to Microsoft’s latest aren’t going as its maker planned. A few people have asked me about my personal opinion of this OS, and I’ll admit, I have no direct experience with it. I also haven’t had much contact with Windows 8 either.
That said, I do keep up with the news, and a few things do concern me.
The good news
It’s not all bad of course. Windows 8 saw a big shrink in the footprint of a typical Windows install, and Windows 10 continues to be fairly lightweight. The UI disaster from Windows 8 has been somewhat pared back to provide a more traditional desktop with a start menu that combines features from the start screen.
There are some limitations with the new start menu, but from what I understand, it behaves mostly like the one from Windows 7. The tiled section still has some rough edges though, something that is likely to be addressed in future updates of Windows 10.
If this is all that had changed though, I’d be happily accepting it. Sadly, this is not the case.
Windows has, since day one, been on a long-term support release model. That is, they bring out a release, then they support it for X years. Windows XP was released in 2002 and was supported until last year for example. Windows Vista is still on extended support, and Windows 7 will enter extended support soon.
Now, in the Linux world, we’ve had both long-term support releases and rolling release distributions for years. Most of the current Linux users know about it, and the distribution makers have had many years to get it right. Ubuntu have been doing this since 2004, Debian since 1998 and Red Hat since 1994. Rolling releases can be a bumpy ride if not managed correctly, which is why the long-term support releases exist. The community has recognised the need, and meets it accordingly.
Ubuntu are even predictable with their releases. They release on a schedule. Anything not ready for release is pushed back to the next release. They do a release every 6 months, in April and October and every 2 years, the April release is a long-term support release. That is; 8.04, 10.04, 12.04, 14.04 are all LTS releases. The LTS releases get supported for about 3 years, the regular releases about 18 months.
Debian releases are basically LTS, unless you run Debian Testing or Debian Unstable. Then you’re running rolling-release.
Some distributions like Gentoo are always rolling-release. I’ve been running Gentoo for more than 10 years now, and I find the rolling releases rarely give me problems. We’ve had our hiccups, but these days, things are smooth. Updating an older Gentoo box to the latest release used to be a fight, but these days, is comparatively painless.
It took most of that 10 years to get to that point, and this is where I worry about Microsoft forcing the vast majority of Windows users onto a rolling-release model, as they will be doing this for the first time. As I understand it, there will be four branches:
- Windows Insiders programme is like Debian Unstable. The very latest features are pushed out to them first. They are effectively running a beta version of Windows, and can expect many updates, many breakages, lots of things changing. For some users, this will be fine, others it’ll be a headache. There’s no option to skip updates, but you probably will have the option of resigning from the Windows Insiders programme.
- Home users basically get something like Debian Testing. After updates have been thrashed out by the insiders, it gets force-fed to the general public. The Home version of Windows 10 will not have an option to defer an update.
- Professional users get something more like the standard releases of Debian. They’ll have the option of deferring an update for up to 30 days, so things can change less frequently. It’s still rolling-release, but they can at least plan their updates to take place once a month, hopefully without disrupting too much.
- Enterprise users get something like the old-stable release of Debian. Security updates, and they have the option to defer updates for a year.
Enterprise isn’t available unless you’re a large company buying lots of licenses. If people must buy a Windows 10 machine, my recommendation would be to go for the professional version, then you have some right of veto, as not all the updates a purely security-related, some will be changing the UI and adding/removing features.
I can see this being a major headache though for anyone who has to support hardware or software on Windows 10 however, since it’s essentially the build number that becomes important: different release builds will behave differently. Possibly different enough that things need much more testing and maintenance than what vendors are used to.
Some are very poor at supporting Linux right now due to the rolling-release model of things like the Linux kernel, so I can see Windows 10 being a nightmare for some.
One of the big issues to be raised with Windows 10 is the inclusion of telemetry to “improve the user experience” and other features that are seen as an invasion of privacy. Many things can be turned off, but it will take someone who’s familiar with the OS or good at researching the problem to turn them off.
Probably the biggest concern from my prospective as a network administrator is the WiFi Sense feature. This is a feature in Windows 10 (and Windows 8 Phone), turned on by default, that allows you to share WiFi passwords with other contacts.
If one of that person’s contacts then comes into range of your AP, their device contacts Microsoft’s servers which have the password on file, and can provide it to that person’s device (hopefully in a secured manner). The password is never shown to the user themselves, but I believe it’s only a matter of time before someone figures out how to retrieve that password from WiFi Sense. (A rogue AP would probably do the trick.)
We have discussed this at work where we have two WiFi networks: one WPA2 enterprise one for staff, and a WPA2 Personal one for guests. Since we cannot control whether the users have this feature turned on or not, or whether they might accidentally “share” the password with world + dog, we’re considering two options:
- Banning the use of Windows 10 devices (and Windows 8 Phone) from being used on our guest WiFi network.
- Implementing a cron job to regularly change the guest WiFi password. (The Cisco AP we have can be hit with SSH; automating this shouldn’t be difficult.)
There are some nasty points in the end user license agreement too that seem to give Microsoft free reign to make copies of any of the data on the system. They say personal information will be removed, but even with the best of intentions, it is likely that some personal information will get caught in the net cast by telemetry software.
Forced “upgrades” to Windows 10
This is the bit about Windows 10 that really bugs me. Okay, Microsoft is pushing a deal where they’ll provide it to you for free for a year. Free upgrades, yaay! But wait: how do you know if your hardware and software is compatible? Maybe you’re not ready to jump on the bandwagon just yet, or maybe you’ve heard news about the privacy issues or rolling release updates and decided to hold back.
Many users of Windows 7, 8 and 8.1 are now being force-fed the new release, whether we asked for it or not.
Now the problem with this is it completely ignores the fact that some do not run with an always-on Internet connection with a large quota. I know people who only have a 3G connection, with a very small (1GB) quota. Windows 10 weighs in at nearly 3GB, so for them, they’ll be paying for 2GB worth of overuse charges just for the OS, never mind what web browsing, emailing and other things they might have actually bought their Internet connection for.
Microsoft employees have been outed for showing such contempt before. It seems so many there are used to the idea of an Internet connection that is always there and has a big enough quota to be considered “unlimited” that they have forgotten that some parts of the world do not have such luxuries. The computer and the Internet are just tools: we do not buy an Internet connection just for the sake of having one.
There are a couple of tools that exist for managing this. I have not tested any of them, and cannot vouch for their safety or reliability.
- BlockWindows (github link) is a set of scripts that, when executed, uninstall and disable most of the Windows 10-related updates on Windows 7 and 8/8.1.
- GWX Control Panel is a (proprietary?) tool for controlling the GWX process. The download is here.
My recommendation is to keep good backups. Find a tool that will do a raw partition back-up of your Windows partition, and keep your personal files on a separate partition. Then, if Microsoft does come a-knocking, you can easily roll back. Hopefully after the “free upgrade” offer has expired (about this time next year), they will cease and desist from this practise.