What you’re seeing
- teamsbootstrapper.exe runs on the Remote Desktop host and exits, but new Teams never appears for users.
- The bootstrapper returns a failure code or reports that the operation isn't supported on this system.
- Users on the terminal server are stuck with classic Teams or have no Teams at all, while desktop users have the new version.
- New Teams starts for the administrator account but not for ordinary users signed in to the session host.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- New Teams is distributed as an MSIX app package, and Windows Server 2019 handles that format differently from Windows 10, Windows 11 and newer server releases.
- The server is missing cumulative updates or prerequisite components that the new Teams package requires on this operating system.
- Policy on the session host restricts app package deployment or sideloading, so the package can't be provisioned for all users.
- Remnants of the classic Teams machine-wide installer conflict with the new client.
- Profile management or FSLogix exclusions leave out the folders where new Teams keeps its per-user data.
Why it matters
Staff who work through a terminal server rely on it for everything, including meetings and chat. If Teams won't install there, they're pushed to the browser version with weaker audio, video and screen sharing, or to personal devices outside your control. Classic Teams has been retired by Microsoft, so staying on it is not a long-term option and leaves the host running unsupported software. Meanwhile, customer calls and internal collaboration suffer for everyone on that server.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Can new Teams run on Windows Server 2019 at all?
Yes, on a properly prepared and fully updated host, but the install route differs from a normal desktop. An engineer confirms the server meets the requirements before attempting it.
Will the work disrupt people who are logged on to the server?
Package changes on a shared host can affect everyone signed in to it, so we agree a quiet window with you before making them.