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 632736
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Some things never change.
by Alfman on Wed 3rd Aug 2016 21:40 UTC in reply to "RE[5]: Some things never change."
Alfman
Member since:
2011-01-28

Lennie,

I believe Microsoft doesn't even use the same network bandwidth for this. And a lot is still handled by Akamai as well.


I don't know if this is still accurate, but I had read that windows 10 was going to distribute updates via a P2P network:

http://www.winbeta.org/news/windows-10-uses-peer-peer-networking-di...
Microsoft is planning to distribute future Windows 10 updates using a peer-to-peer (P2P) protocol.



P2P has unbeatable performance and shifts the bandwidth burden/costs away from the source and to the users. If MS is using P2P tech, then all microsoft would have to do is to seed it using modest resources.

The main reason to stagger updates over a longer period doesn't isn't bandwidth but to limit the damage caused by a faulty update, giving MS time to detect & fix it before the next batch of of "production testers" get the update ;)

Reply Parent Score: 4

quackalist Member since:
2007-08-27

P2P updates was one of first 'features' I disabled on 10. Hopefully it can still be.

Reply Parent Score: 3

Lennie Member since:
2007-09-22

The main reason to stagger updates over a longer period doesn't isn't bandwidth but to limit the damage caused by a faulty update, giving MS time to detect & fix it before the next batch of of "production testers" get the update ;)


That I fully agree with.

Reply Parent Score: 3

ahferroin7 Member since:
2015-10-30

They do have the option, and from what I can tell, the protocol is pretty much BitTorrent with X.509 certificates involved in the hashing and the magic numbers changed (I've looked at packet captures, and the traffic patterns are very similar to BitTorrent). The problem is that many people turn this off (I get turning off sending updates to random people on the internet, but not even sharing them between local systems is stupid, the downloads get verified just the same as regular windows update downloads, and it's actually harder to inject something in a P2P network than a regular download). On top of that though, they don't appear to be distributing the upgrade through this network.

In all seriousness though, the whole 'You'll get a notification when the update is ready for your system, or you can click here to download it now' thing with pseudo-random selection of what systems get the update automatically screams attempting to conserve bandwidth.

Reply Parent Score: 3

dionicio Member since:
2006-07-12

Amazed at this P2P involvement!

Reply Parent Score: 2