Microsoft Admits to Disabling Third-Party Antivirus Code

I for one do not have an issue with this.

And CE didn't break any applications for me. I just had to update my audio driver.
 
I don't know if that's true or not. I know at some point, Norton quit working and MS's took over, but when I reinstalled Norton, it worked like a charm. So did Norton fix a problem that required me to reinstall? I don't know. Maybe it wasn't related to this at all, because Norton hasn't said anything AFAIK.
My take is that IF they disable the s/w, they should notify you, so you know to go look to your s/w provider for a solution. In my case, I just don't know when it happened, so I can't say whether it was the CU that caused it or not. And that, to me, is a problem that MS needs to fix.

I for one do not have an issue with this.
And CE didn't break any applications for me. I just had to update my audio driver.

I may have had to do that too, though because it mostly worked, I didn't really notice it for a while either. I still don't think my new driver works as well. Every now and then, for reasons I don't understand, it switches from my speakers to my dell monitor, which is annoying (but easy to fix).
 
So much for most of the replies actually reading the short description much* less the linked article :)

People here can't read.

Some of our AVG installs got disabled after the creators update, but that was strictly because they were on an old version, the users who had updated their installs had no issues. Out of curiosity we re enabled one of the old AVG installs after the update and Network connectivity and the windows firewall just went completely south, so did domain access permissions for some reason. Either way I was silently thanking MS because having your AV shut down on you until you do your updates on it is a far better alternative to the system failing half way through and spending god only knows how many hours trying to roll back updates instead.

That is exactly the reason they were disabling software, because it was an older version that wasn't supported. While some people are going to bitch about it, disabling it was the best option. Now they should have probably done a better job letting people know they disabled it and why, but keeping the system running is the best way to go.
 
That is exactly the reason they were disabling software, because it was an older version that wasn't supported. While some people are going to bitch about it, disabling it was the best option. Now they should have probably done a better job letting people know they disabled it and why, but keeping the system running is the best way to go.

I believe they should have told you before installing creators update and given you the option to continue or just stay with the working combination.
 
I believe they should have told you before installing creators update and given you the option to continue or just stay with the working combination.

I believe they shouldn't be responsible for helping keep other vendors software up to date at all, even to that degree. I wouldn't do it if I were making software.
 
My take is that IF they disable the s/w, they should notify you, so you know to go look to your s/w provider for a solution. In my case, I just don't know when it happened, so I can't say whether it was the CU that caused it or not. And that, to me, is a problem that MS needs to fix.

It should have appeared as a message in your system tray where it gives you alerts about updates, security issues, etc.

I believe they shouldn't be responsible for helping keep other vendors software up to date at all, even to that degree. I wouldn't do it if I were making software.

This is more a case where they want to help keep their product safe for the consumer. I don't think it is about helping other vendors as much as helping their customer.
 
I believe they shouldn't be responsible for helping keep other vendors software up to date at all, even to that degree. I wouldn't do it if I were making software.
If they're disabling the software, it's a very minor change (probably less than 5 lines of code) to pop up a dialog that says, "<app name> is out of date and is being disabled." It may actually be a single line of code, but I'm not very familiar with w32 APIs,
 
I believe they shouldn't be responsible for helping keep other vendors software up to date at all, even to that degree. I wouldn't do it if I were making software.

To me the problem stems from Microsoft releasing new versions of windows too frequently.
 
It should have appeared as a message in your system tray where it gives you alerts about updates, security issues, etc.

I don't recall seeing that, but I also think that's not a great place for this. It's really easy to miss those notifications, especially since most are just things from the news app or email.[/QUOTE]

To me the problem stems from Microsoft releasing new version of windows too frequently.

I'm pretty sure you can put off major updates for quite a while. I didn't install AU until last October
 
If they're disabling the software, it's a very minor change (probably less than 5 lines of code) to pop up a dialog that says, "<app name> is out of date and is being disabled." It may actually be a single line of code, but I'm not very familiar with w32 APIs,

Those lines of code put them on the hook for notifying the client it's out of date. No matter how easy it is, it's not their problem.
 
I don't recall seeing that, but I also think that's not a great place for this. It's really easy to miss those notifications, especially since most are just things from the news app or email.

I guess I don't understand how it is not a great place for it? That is where it gives you notifications about security issues and updates... Where else would you put it?
 
Those lines of code put them on the hook for notifying the client it's out of date. No matter how easy it is, it's not their problem.
They've already disabled the software, because they think it's out of date. Saying, "We've disabled X because it's out of date" puts them on the hook for nothing. When you upgrade from 7 or 8 to 10, they tell you which programs won't be carried over (which is essentially the same thing, except in this case they don't uninstall it).

I guess I don't understand how it is not a great place for it? That is where it gives you notifications about security issues and updates... Where else would you put it?
I'd pop up a dialog just like they do when you're upgrading form one version of the OS to another. It's been almost 2 years, but as I recall when I did it, it ran off the names of programs that would be disabled (or were disabled if the message was after the fact).
 
They've already disabled the software, because they think it's out of date. Saying, "We've disabled X because it's out of date" puts them on the hook for nothing. When you upgrade from 7 or 8 to 10, they tell you which programs won't be carried over (which is essentially the same thing, except in this case they don't uninstall it).


I'd pop up a dialog just like they do when you're upgrading form one version of the OS to another. It's been almost 2 years, but as I recall when I did it, it ran off the names of programs that would be disabled (or were disabled if the message was after the fact).

What you'd do and what happens are quite different. If they do that then why aren't they monitoring the software proactively to warn people? (that question will arise) It's not M$'s job to monitor third party software beyond exactly what they do now.
 
What you'd do and what happens are quite different. If they do that then why aren't they monitoring the software proactively to warn people? (that question will arise) It's not M$'s job to monitor third party software beyond exactly what they do now.
Using your logic, they shouldn't tell you when a program isn't going to work in Windows 10 when upgrading. And FYI, if you disable software running on my computer, IT IS YOUR JOB TO TELL ME.
 
Using your logic, they shouldn't tell you when a program isn't going to work in Windows 10 when upgrading. And FYI, if you disable software running on my computer, IT IS YOUR JOB TO TELL ME.

I believe it's not, thus the reason we disagree. Let's leave it at that.
 
I believe it's not, thus the reason we disagree. Let's leave it at that.

Everyone is entitled to their own opinions.

I do want to say that there is one minor issue with your comment which might just be how you are presenting it.

You seem to be misunderstanding how things work now, and what the person's statement is saying.

Your statement is that they shouldn't monitor 3rd party programs any more than they do now and that if they did what he said then they would be monitoring more than they should. But his request isn't to monitor any more than they already are. It is just handling what they do now differently. When you upgrade from Windows Vista to Windows 7 it ran a program that told you these programs will not run so please update or uninstall these before you continue. The same thing was in Windows 7 to 8, 8 to 10... This is not new, this has been in Windows for years.

For Windows 10 Creator Update they added a new feature that in the background they decided to detect if a program was not going to work (the AV program) and if it was decided not to work they turned it off. Or that has been there and this was the first time a AV program was found to be not usable between service pack levels like this. So they are already monitoring said program at the time of upgrade to know to do something with it. The concern is that they didn't have a similar popup like they did when you went from 8 to 10 that tells you I am going to turn this program off because it will break things. He is not asking for any change in monitoring, he is not asking for a change in how they handle bad programs. Just that WHEN they know that a program is going to be bad, which is done via existing monitoring / validation in place today, they warn you the same for if you are going from Windows 10 to Windows 10 release 4 as they do for Windows 8 to Windows 10. Both are upgrade processes, you see the same upgrade cycle run there is nothing else visually different from the upgrades except for a single screen missing. A summary. So if they are going to monitor, and they are going to react to said monitoring, let customers know what you did. If they don't want to monitor and don't want to react to what they find, that is fine. But the statement is when they have already done all the other work let the customers know. That isn't increasing how much they are monitoring that is telling us what they change. Two very different things.
 
I've had to roll back the creators update strictly for compatibility reasons. Mainly remote desktop doesn't work to non creators update pcs.


I guess I am a lucky one, have Creators update on one of my main work PC's and I RDC all day long to other systems from Server 2003 to 2012 R2 to Windows 7 and numerous Windows 10 devices that are still on 1607.
 
I guess I am a lucky one, have Creators update on one of my main work PC's and I RDC all day long to other systems from Server 2003 to 2012 R2 to Windows 7 and numerous Windows 10 devices that are still on 1607.

Mine is working fine too.
 
I cannot for the life of me comprehend how users defend the actions of Microsoft in cases such as this, whose PC is it? Where does this all end? Is the day where it's all 'software installation via Windows Store only' because MS know's what's best for the end user irregardless of skill level getting closer?

You're all not a part of the unknowledgable masses, you should all know better and you should all be jumping up and down and telling Microsoft to stick to making the OS and leave third party developers to do their own thing considering your permission on your PC.

But no. Years of Microsoft brainwashing results in PC enthusiasts actively defending such outwardly manipulative tactics like spineless morons - As a comment in general and not aimed at anyone specific. As a 30+ year computing enthusiast, I think such an attitude is downright embarrassing. Take off the VR headset and wake up to the decline of the world around you.

I'm not hating on Microsoft, I'm over the spinelessness of computing enthusiasts regarding civil liberties and personal information. "Gaw, Microsoft's looking after all us dumb users!" Come off it, you're all smarter than that.
 
Last edited:
I cannot for the life of me comprehend how users defend the actions of Microsoft in cases such as this, whose PC is it? Where does this all end? Is the day where it's all 'software installation via Windows Store only' because MS know's what's best for the end user irregardless of skill level getting closer?

You're all not a part of the unknowledgable masses, you should all know better and you should all be jumping up and down and telling Microsoft to stick to making the OS and leave third party developers to do their own thing considering your permission on your PC.

But no. Years of Microsoft brainwashing results in PC enthusiasts actively defending such outwardly manipulative tactics like spineless morons - As a comment in general and not aimed at anyone specific. As a 30+ year computing enthusiast, I think such an attitude is downright embarrassing. Take off the VR headset and wake up to the decline of the world around you.

I'm not hating on Microsoft, I'm over the spinelessness of computing enthusiasts regarding civil liberties and personal information. "Gaw, Microsoft's looking after all us dumb users!" Come off it, you're all smarter than that.

Last time I updated my Linux server I lost programs that were no longer compatible going from Centos 6 to Centos 7. This is nothing new.
 
Last time I updated my Linux server I lost programs that were no longer compatible going from Centos 6 to Centos 7. This is nothing new.

Exactly but when MS does it it's the end of the ffing world like they're not supposed to anything at all.
 
Perhaps you should try reading and researching the issue. Microsoft only disables AV software (~5% of the time) that is not compatible (and therefore not working anymore) or is not up to date (and therefore is not providing the proper protection anymore) and then it installs Windows Defender to help keep the person safer until they install a replacement or update the AV software. I don't see the issue here. Seems like MS is going out of their way to help the consumer, not be anti-competitive.
"rolling out software that makes an AV stop working then swapping in their software" doesn't sound anti-competitive at all. I guess if I ignore the stopping software from running part and take that as a given, you might have a point. Do we have a way of knowing the update innocently stopped competitor software? I don't see how that is possible.
 
"rolling out software that makes an AV stop working then swapping in their software" doesn't sound anti-competitive at all. I guess if I ignore the stopping software from running part and take that as a given, you might have a point. Do we have a way of knowing the update innocently stopped competitor software? I don't see how that is possible.

Guess they could turn it off and leave you with nothing. Sounds good.
 
"rolling out software that makes an AV stop working then swapping in their software" doesn't sound anti-competitive at all. I guess if I ignore the stopping software from running part and take that as a given, you might have a point. Do we have a way of knowing the update innocently stopped competitor software? I don't see how that is possible.

So allowing software to run that is not protecting your system and in fact can provide yet another method to infect your computer is the safe choice. Got it. Look there are always trade offs. Microsoft is trying to do the best by the customers to help protect them given all the crap that is out there. I also completely get people who don't like that. To those, I have suggested in this very thread even, that there are other choices out there that may be better for them. But honestly, this seems like a positive move for Microsoft given the majority of the user base.
 
Last time I updated my Linux server I lost programs that were no longer compatible going from Centos 6 to Centos 7. This is nothing new.

Did you choose to go from Centos 6 to 7 ? Because if so that's a level of choice Windows 10 doesn't give you. If you didn't want the Creators update too bad bend over and take it bitch.
 
Did you choose to go from Centos 6 to 7 ? Because if so that's a level of choice Windows 10 doesn't give you. If you didn't want the Creators update too bad bend over and take it bitch.

I don't have problems managing or deferring updates. The default out of the box behaviour might be thus but most people at least adjust the mirror and seat when they buy a new car without bitching.
 
I don't have problems managing or deferring updates. The default out of the box behaviour might be thus but most people at least adjust the mirror and seat when they buy a new car without bitching.

Deferring simply means they bend you over next week instead of today. Not much of a solution.
 
Back
Top