Hacker News Reader

Comment by dsalfdslfdsa | Hacker News Reader

Sounds like you don't have much experience with Windows and MS software.

https://answers.microsoft.com/en-us/msteams/forum/all/why-do...

I administer a Windows domain at my job that I do 40 hours a week so your assessment of me is just wrong and also offensive.

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.

This is the thing: Windows admins praise Windows when they are running a completely different edition of Windows with different configurable behaviors. It looks a lot different for home users who almost certainly do not even know what a GPO is. And this also raises the suspicion of which exact Windows edition those admins are running on their home computer(s) and how they obtained the license for that...

> It looks a lot different for home users who almost certainly do not even know what a GPO is.

Sounds like the Windows version of saying "I don't understand why the whole world isn't running Linux."

You haven't re-created the described problem - Teams sets itself to auto-start again after you start it yourself. After all, it's very reasonable that you might want to join the occasional Teams meeting but not want it running after every boot.

I'm not sure if it's a particular version or environment that does this, but at the very least I can't replicate it on my home PC with Teams (personal). If I disable it in the task manager's autostart, it remains disabled if I start Teams. It won't even let me enable "Auto-start" in the Teams settings if it's disabled in the task manager.

lol, a GPO. Very reasonable solution for a home user.

not to mention that gp editor is disabled on non pro windows. i think there is some kind of a funky command line or registry hack to enable it. So yeah, I moved on from windows largely because of this force fed software.

Windows licensing is the hardest part of my job. Like if I want to have thin clients running Windows 11 VMs hosted on Windows Server 2022, how do I pay Microsoft so they will let me use the software in this way? I have no idea. I think you need to contact some kind of client services representative at Microsoft in order to figure out the whole licensing thing. By the way if it wasn't clear, I hate all of this. The only good thing about it is that I can make a living by dealing with it so other people don't have to.

Task Scheduler is available on Windows 10 Home. I think of it as "cron for Windows" even though despite being able to schedule the execution of specific tasks, it is really nothing like cron aside from that.

Not sure about other people here but I really liked how autostart used to work in 7 and before - just drop a shortcut in the Start menu folder and you're done. In 10 at some point, in order to have 3rd party software launched at login I had to use task scheduler.

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

You can still do that, the folder is at:

  %appdata%\Microsoft\Windows\Start Menu\Programs\Startup

I have a few sshfs[1] mounts there.

[1] https://github.com/winfsp/sshfs-win

I tried that path back then but it still didn't work for me - no program I tried to put there incl Windows ones was able to launch at the login. I had just entries in the task manager's startup page. Maybe something changed in 11 - dunno

I can guarantee you that the startup folder still works fine, but in some cases you must create the folder.

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.

Reply on news.ycombinator.com