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

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 632652
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Err not quite
by Bill Shooter of Bul on Wed 3rd Aug 2016 04:02 UTC in reply to "Err not quite"
Bill Shooter of Bul
Member since:
2006-07-14

Understood, but I thought windows prided itself as making each version compatible with all the crazy apps everyone already had.

I just upgraded to 10 before the free upgrade expired, and saw it hide/disable a few of the stupid OEM apps that were bundled in.

Reply Parent Score: 3

RE[2]: Err not quite
by Kochise on Wed 3rd Aug 2016 06:39 in reply to "RE: Err not quite"
Kochise Member since:
2006-03-03
RE[3]: Err not quite
by Bill Shooter of Bul on Thu 4th Aug 2016 14:05 in reply to "RE[2]: Err not quite"
Bill Shooter of Bul Member since:
2006-07-14

I think you misunderstood.

I did want to upgrade to win 10 from win 8.1.

I don't mind that it disabled crapware. Just surprised that Microsoft didn't go out of its way to support the OEM bloat/crapware.

Reply Parent Score: 2

RE[2]: Err not quite
by lucas_maximus on Wed 3rd Aug 2016 06:57 in reply to "RE: Err not quite"
lucas_maximus Member since:
2009-08-18

Newer Versions of SQL Server are backwards compatible with Database Scripts of earlier versions.

i.e. SQL Server 2005 database will work with MS SQL SERVER 2008 and above. So there is no reason to keep old versions of it around.

I think SQL SERVER and the Management studio really digs it way into the OS.

Reply Parent Score: 1