Linked by Thom Holwerda on Tue 2nd Aug 2016 21:28 UTC

The Windows 10 Anniversary Update was released earlier this evening, and I dutifully installed it so that I could write about any oddities that might pop up. Well, a number of oddities have popped up, and they're bad - really bad. The Anniversary Update does some really shady stuff during installation that it doesn't inform you of at all until after the fact.

First, the Anniversary Update reinstalls Skype "for you", even if you had it uninstalled earlier, which in and of itself is a blatant disregard for users - I uninstalled it for a reason, and I'd like Microsoft to respect that. That in and of itself is bad enough, but here's the kicker: during installation, Microsoft also automatically logs you into Skype, so that possible Skype contacts can just start calling or messaging you - again, without ever asking for the user's consent.

Imagine my surprise when I open that useless Metro notification center thing - whose button now sits in the bottom right of the task bar, right of the clock, even, and is unremovable - and see that Skype is now installed, and that I'm logged in. This is a blatant disregard for users, and I'm sure tons of users will be unpleasantly surprised to see Microsoft forcing Skype down their throats.

There was an even bigger surprise, though: during installation of the Anniversary Update, Microsoft apparently flags Classic Shell - a popular Start menu replacement that gives Windows 10 a customisable Start menu that doesn't suck - as incompatible with the Anniversary Update, and just straight-up deletes hides it from your computer - again, without ever notifying you beforehand or asking you for your permission.

Update: actually, the application isn't removed entirely - it's still there in the Program Files folder, but it's entirely scrapped from search results and the Start menu. Effectively, for most users, that's identical to removing it. What an incredibly odd and user-hostile way of dealing with this. You can see how the wording in the screenshot below is confusing regarding the removing vs. hiding issue.

Classic Shell released an update to fix the compatibility issue detected, so I hope my settings are still there somewhere, because it'd suck having to redo all of them because Microsoft just randomly deleted a program from my computer hid a program, without informing me or asking me for my permission. It could've just disabled the program, prevented it from running - why delete hide it entirely? Are they that desperate to try and get me to use their terrible excuse for a Start menu?

So, just in case you're about to install this update - Microsoft will force Skype down your throat, and may randomly delete hide programs from your computer without asking for your permission.

Have fun.

Thread beginning with comment 632681
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Some things never change.
by RobG on Wed 3rd Aug 2016 10:40 UTC in reply to "RE[2]: Some things never change."
Member since:

I agree with the point that reinstalling Skype was bad behaviour. WRT Classic Shell though, maybe there was an incompatibility. As a Shell replacement, that could potentially leave your system in an unusable state, in which case this behaviour would be just what I would expect.

Reply Parent Score: 2

darknexus Member since:

WRT Classic Shell though, maybe there was an incompatibility. As a Shell replacement, that could potentially leave your system in an unusable state, in which case this behaviour would be just what I would expect.

Are you serious? You want, even expect, the system to make changes without even asking once?
Did I fall through a wormhole into a universe of sheep or something?

Reply Parent Score: 9

avgalen Member since:

Nope, you didn't fall through a wormhole but maybe you finally discovered that you are a ram living amongst sheep. And although the ram is certainly more powerful than any individual sheep, it is the flock that actually decides the direction they are all going.

(okay, that is as far as I am going to take that analogy)

Reply Parent Score: 3

avgalen Member since:

Apparently Classic Shell, despite the name, is NOT a shell replacement. It adds/modifies the default Shell (Explorer.exe) and otherwise it is just a program.

What I would expect is that the compatibility checker inside the Upgrade procedure would warn about this incompatible program before performing the actual update with an option to stop the upgrade. That is how it always used to work and how I think it should work!

As I mentioned earlier today, Microsoft is very confused about the difference between an update and an upgrade and I think this is one of the symptoms of that.

Reply Parent Score: 4

lucas_maximus Member since:

The program has been flagged as incompatible since Win8 on and off if you do a quick google and you will see Forum posts going back to 2013-2014.

Reply Parent Score: 2