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.

Permalink for comment 632673
To read all comments associated with this story, please click here.
RE: Some things never change.
by avgalen on Wed 3rd Aug 2016 09:32 UTC in reply to "Some things never change."
Member since:

As far as I know Classic Shell only checks for updates when it starts, not in a seperate background process. So if Thom would have waited untill the anniversary update would have arrived by Windows Update, Classic Shell would have updated itself to be compatible with the Anniversary Update first and then there wouldn't have been an issue.

Also, Skype auto-logging in is exactly what most people would love. It is the exact same with the Mail app. As long as both are linked to the Microsoft Account that you use to log in to Windows it only makes sense for Windows to say "Hey, you have this software, I know how to login, I will setup everything for you automatically and get it ready to use".

I agree that it sucks that Skype (and many apps) get reinstalled by default though. (Technically I think it is a different Skype App actually) Except for that this article basically feels like hyperbole and ranting. Let's see exactly what happened to Thom: On the very day that the update came out he got it through an alternative way and installed it. That worked without any issue. After the upgrade he got 1 app that he doesn't like anymore, although he had an account previously, and can uninstall with 2 clicks. He also had only 1 3rd party program-incompatibility and that was in a Shell Replacement. He got updated of that but doesn't like the wording. There is already an update from that 3rd party.

So on day 1 someday finds an alternative way of installing Windows in search for oddities and he thinks the above 2 things are "bad - really bad".
Well, I guess we have now reached the level of OS-maturity where this is considered "bad - really bad" /s

Edited 2016-08-03 09:34 UTC

Reply Parent Score: -1