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.

Permalink for comment 632651
To read all comments associated with this story, please click here.
TimMiltz
Member since:
2016-08-03

Be careful people

Classic Shell distro servers were hacked today

They have fixed the problem.

It wipes your Master Boot Record and you will not be able to boot again without careful repair.

If your file size says 6.81 MB (7,148,732 bytes) You have the infected version.

The NEW one they have up as of now says: 6.88 MB (7,220,496 bytes).


More info at Classic Shell Forums under bug reports.

I got zapped, fortunately was able to rebuild the MBR, otherwise you will get a 'spade' character on boot bottom left with a false prompt.

Some users got a message 'Your adventures end here'

In that I only own Windows 8.1 retail, my 'free' windows 10, while I did upgrade ? is not longer free, as of July 29th. So, if I had not been able to repair my master boot record (I used Windows 7 repair CD, and selected 'fix startup problems' command line tools did not work)? I would have to go BUY Windows 10 all because of this CultOfPeggle virus that was responsible for this.

So sad that such a wonderful product- Classic Shell was hit the DAY people would be saying 'where'd my Classic Shell go' ? after the update, they go download it - as I did- and if they got the infected one - kiss your machine goodbye unless you even know what an MBR is. CultOfPeggle twitter page says 'this will be a survival of the trouble-shootiest' - most unfortunate for many today.

Edited 2016-08-03 04:09 UTC

Reply Score: 4