https://answers.microsoft.com/en-us/msteams/forum/all/why-do...
I just restarted one of the workstations with Teams startup enabled and Teams ran when the computer restarted. Then I tried disabling Teams startup in the task manager on the same workstation and then restarted the workstation, and Teams hasn't started. I checked the startup tab in the task manager and Teams is still disabled after the restart. It hasn't appeared in the task manager either. This is Windows 10 Pro, so the behavior might be different on different versions/editions of Windows. Also this behavior might be affected by updates. These machines automatically install updates every Saturday, so they're running the latest Windows 10. Even if the setting is reset on a future update, I can create a GPO to disable it or even a scheduled task if I'm not allowed to manage this computer at the domain level.
Sounds like the Windows version of saying "I don't understand why the whole world isn't running Linux."
Also, funny thing: clicking this link pushes me thru https://login.microsoftonline.com/common/oauth2/v2.0/authori...(...) - feels like they're expecting me using Edge so they could log me in automatically with snatched MSA credentials
%appdata%\Microsoft\Windows\Start Menu\Programs\Startup
I have a few sshfs[1] mounts there.Microsoft does not screw around with backwards compatibility. There are multiple ways to start applications on launch now, including the user or public user startup folder, registry entries, and via scheduled tasks.
I feel like people want Windows to be evil so they oversell the issues.
That's not to say that Microsoft should be forgiven for their obvious over-promotion of internal products. They really need a strong hand to rein in all these departments with their own metrics and agendas.
It's not enough that we can just ignore or correct these things that are just happening on our own computers without our consent. These things should not be happening to begin with.
This, is it exactly.
Microsoft makes some very bad decisions, do not get me wrong. I agree with you and I think this is the core of why people complain so vehemently about Microsoft.
This goes to explain a lot of reactions that Very Online people tend to have to things. There must be a villain and that villain must be irredeemable. Even when, as the Brits would say, "cock-up" is a more likely explanation than "conspiracy."
Indeed, they've been playing shenanigans with OneDrive, but you can actually uninstall it now easily. That didn't used to be the case. Yes, it gets re-installed, yes it now is auto-enabling itself, but hey - you can easily remove it now.
I'm pretty sure I solved definitively the Teams autostart problem long ago, easily enough I can't recall what I did. It's not a problem for me, even on 'Home' machines.
Long, long ago we had names for software that auto-installs and auto enables even after you have removed it: malware, or spyware if it's not very destructive.
Then after za'o decades of stories like the above (it is merely the most recent of many) one might wonder how does Microsoft with so many programmers and so much money produce such kusogeware? That continues to waste my time?
1. Windows has an absurdly short maximum path length of 260 characters.
2. On Windows, moving files to a temporary directory can fail, if the temporary directory has a longer prefix than the original path.
3. When uninstalling, the python utility "pip" first collects files into a temporary directory, then deletes that temporary directory.
4. To avoid running into MAX_PATH limits, pip doesn't use a normal temp directory. Instead, it makes a temporary directory adjacent to the directory it is removing. (https://github.com/pypa/pip/pull/6029)
5. If pip is interrupted while uninstalling, the adjacent temp directory is never deleted.
So, in order to work around a Windows-only problem, pip stopped using standard file locations, creating a new problem that only existed due to the workaround. And then I'm left trying to figure out why I'm running out of disk space.
Yeah, I don't see Windows in the top 5.
This is something that languages/runtimes with more effort put into portability already handle for you:
https://github.com/openjdk/jdk/blob/master/src/java.base/win...
If Python doesn't do this it's just because the sort of people who write Python don't care about Windows enough to fix it.