First, yes I know my desktop is messy. So is my desk. Sorry about that.
I have been using Windows 10 on my two main computers for several months now. In general it is a good solid operating system. It runs faster than Windows 7 ran on my 6 year old Dell desktop and it is miles ahead of the 8.1 I was using on my touchscreen laptop. That is not to say that there aren’t some issues with the operating system. It looks nice and loads fast. Programs run smoothly and the touchscreen drivers are a dream. It shuts down quickly (well, generally, unless it is installing an update – more on that in the next section). Generaly I like it very much and recommend it. That said, there are a few real irritations.
The most annoying of these is the “Cortana and the Start Menu have Stopped Working” error that has plagued Windows 10 users almost from the start. I have addressed this on the Windows 10 Problems page.
The second irritation for me is that I can’t control when Windows downloads and installs updates. Windows updates are probably necessary, but when you have a metered connection (a limit to the data you can download with paying more), it is important to have control over when some of these huge updates are downloaded. In theory, there is supposed to be a way to tell the computer that it is a metered connection and to delay downloads until notified, but it doesn’t work on my computers. This leads to the situation I ran into a couple of weeks ago when my 2 computers decided to download the Windows update file for the first major update to Windows 10. The update was nearly 2 gb, and I have a 10 gb a month limit. You can see the problem. For me it is huge, but for most people, is merely an inconvenience.
Another irritation is that sometimes drivers are updated using software that doesn’t work. That requires doing a roll-back on the computer, and most casual users have no idea how that works. I have seen Microsoft update drivers completely disable video cards, wireless cards, and sound cards (not with Windows 10, but with Windows 7). Come on, Microsoft, if it ain’t broke, don’t fix it.