HxTsr.exe: Safe Microsoft Process, High CPU, or Error?

HxTsr.exe is usually a legitimate Microsoft communications process from the legacy Windows Mail and Calendar app package, also described as Microsoft Outlook Communications. It can remain in Task Manager after those apps have been retired, but it is not a core Windows service and should not be confused with the executable for the new Outlook app. Check the running file against its installed app package before trusting it. The usual location is a versioned microsoft.windowscommunicationsapps folder under the protected WindowsApps directory. A same-named file in Downloads, Temp, Startup, or another writable folder needs a malware check.

What is HxTsr.exe?

HxTsr.exe is associated with the microsoft.windowscommunicationsapps package that provided the built-in Windows Mail, Calendar, and People apps. The process handled communication with mail and calendar services, so brief network activity was normal when those apps synchronized an account.

Microsoft ended support for Windows Mail, Calendar, and People on December 31, 2024 and says those apps can no longer send or receive emails or events. It recommends moving accounts to the new Outlook for Windows or Outlook.com. That does not make every remaining HxTsr.exe file malicious. A PC can still retain the older app package, its data, or an incomplete migration. It does mean that repeatedly reinstalling the retired Mail app is no longer the best long-term fix.

Is HxTsr.exe part of Windows 11 or new Outlook?

HxTsr.exe can remain on Windows 10 or Windows 11 when the legacy communications-app package is still installed. It is not a Windows kernel component, and seeing it does not prove that the new Outlook app is using it. Check Settings > Apps > Installed apps to identify which Mail, Calendar, or Outlook package is present before repairing or removing anything.

How to tell if HxTsr.exe is safe

• The process path matches the installed Microsoft communications package. This supports the legitimate-app explanation. Check the publisher and the actual alert or symptom before allowing a connection or restoring a quarantined file.
• The matching package crashes or keeps using CPU, memory, or disk. Follow the app-error steps below. Resource use alone does not tell you whether the executable is malicious.
• The file runs from Temp, Downloads, Startup, or an unrelated app folder. Treat it as unverified. Block an unexpected connection and scan it before running or allowing it.
• Windows denies access to the folder, or Open file location is unavailable. Use the package check below. Protected-folder permissions and an exited process can obstruct inspection; that is different from finding a suspicious executable.

Check the path and publisher

Open Task Manager with Ctrl + Shift + Esc, find HxTsr.exe, and choose Open file location from its context menu. If it is grouped under an app, expand the group or look in the Details tab. Record the full path shown by Windows or by the security alert; do not launch a found file just to identify it.

The usual path follows this pattern. The package version and architecture can vary; {package-version} below is a placeholder, not text to paste into Explorer.

C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_{package-version}\HxTsr.exe

Open Properties > Digital Signatures when available and inspect the signer and signature status. A Details entry saying Microsoft is descriptive metadata, not the same as a verified signature. If a signature is missing or cannot be verified, keep the file unverified while you check the package and scan; do not conclude either “safe” or “virus” from that one field.

If WindowsApps will not open: identify the installed package

You do not need to take ownership of WindowsApps or change its permissions. Open Windows PowerShell under the Windows account where you see the problem and run this read-only command:

Get-AppxPackage -Name Microsoft.WindowsCommunicationsApps |
    Format-List Name, PackageFullName, InstallLocation, Publisher

• A package is listed: compare its InstallLocation with the full HxTsr.exe path from Task Manager or the alert. Check that the reported publisher identifies Microsoft. A matching package explains why the old component remains; it does not authenticate a separate same-named file elsewhere.
• No output: the command did not find that package registered for the current user. It does not prove that every copy on the PC is malicious or that no other user has the package. Recheck the recorded path and account before deciding what to remove.
• An error or blank location: identification is still incomplete. Keep the error text and ask an administrator to inspect a managed PC; do not change protected-folder permissions to force access.

This checks installed-package information, not the contents of the running executable. If the path, publisher, and alert disagree, scan and investigate the actual file before making an exception.

If you need a broader checklist for a downloaded or unfamiliar executable, use our guide to checking whether an EXE file is safe. Do not upload a private work document or proprietary executable to a public scanner without permission.

What the Task Manager and folder checks look like

These screenshots show the legacy app in an older Windows interface. Menu styling and package-version numbers may differ on your PC.

In Task Manager, select the HxTsr.exe process and open its context menu.

The expected executable is inside the protected Microsoft communications-app package. A similarly named file elsewhere should not inherit that trust.

Why does HxTsr.exe connect to the Internet?

Communication with email and calendar services was the legitimate process’s purpose. A remaining legacy package may still attempt background activity, even though the retired apps are no longer a supported way to send or receive mail. A connection attempt is not proof that synchronization succeeded or that new Outlook needs this file.

For a firewall prompt, compare the full executable path with the installed package and review the destination and reason for the connection. Do not permanently allow it just because the filename looks familiar. If the old app is no longer needed, migrate its local data and remove that app through Settings instead of accumulating firewall exceptions.

How to fix an HxTsr.exe application error or high CPU

1. Record what failed. Keep the full executable path and exact application-error text. Compare the path with the installed package. If it points to an unrelated location, use the suspicious-copy scan steps instead of repairing Mail.
2. End the task once and reopen the related app. Background app activity can launch a genuine process again. Check whether the same file returns and whether resource use settles. A restart alone is not malicious persistence; sustained activity from a different or unexplained path needs investigation.
3. Install available Windows and Microsoft Store updates. Restart the PC afterward so an older package is not kept in a half-updated state.
4. Repair only the app identified by the failing path. For the legacy communications package, look for Mail and Calendar in Settings > Apps > Installed apps (Windows 11) or Apps & features (Windows 10). Choose Advanced options > Repair if offered. Do not reset new Outlook merely because the old process is called Microsoft Outlook Communications. Some apps do not offer Repair or Advanced options.
5. Preserve local data before Reset or uninstall. Confirm what is available in your provider’s webmail and export any local emails, calendar events, or contacts you still need using Microsoft’s migration guidance in References. Do not assume that signing in again will restore local-only items. Then move to new Outlook or Outlook.com. Repairing the old package does not reverse the retirement of its mail service.
6. Scan when the behavior does not match the package. An unexplained path, security-tool detection, or a process repeatedly launched from an unfamiliar Startup entry or scheduled task warrants scanning. High CPU by itself does not identify the cause.

Do not download a replacement HxTsr.exe from an EXE-download site or delete the protected copy to fix the error. Address the owning app. If the issue is actually classic Outlook rather than the Windows communications package, use Outlook-specific profile or Office repair steps. HxTsr.exe is not the same as OUTLOOK.EXE, so deleting it will not repair a damaged PST/OST file or Outlook profile.

Should HxTsr.exe run at startup?

HxTsr.exe is normally launched by its app package when mail or calendar work is needed; it is not a conventional Windows service that everyone must keep running. Do not delete the executable to stop it. If you no longer use the retired Mail and Calendar apps, first migrate any local data, confirm that new Outlook works, and then remove the obsolete app through Windows settings if the option is available.

If Windows shows a separate HxTsr.exe entry in a user-writable Startup folder, treat that as suspicious. Our suspicious startup apps checklist explains how to verify the file and disable the entry without deleting evidence too early.

Is HxTsr.exe a virus?

The genuine Microsoft-package copy is not a virus, but malware can reuse the name. Record the security product’s exact detection name and affected path: a filename is not a malware-family diagnosis. A detection of the expected package may be a false positive, but the folder alone is not a reason to restore it. Update the security tool, recheck the file, and use its vendor’s false-positive review process if the package evidence supports that possibility. Keep an unexplained detection quarantined while it is investigated; do not add a WindowsApps-wide exclusion.

What to do with a suspicious copy

1. Block the unexpected network request and note the full file path.
2. Do not sign in to mail or other accounts from the PC until the file is checked.
3. Download and install Gridinsoft Anti-Malware, update its databases, and run a Full Scan to check the executable, startup entries, scheduled tasks, and related files.
4. Review the detections, apply cleanup to confirmed threats, restart Windows, and check the original symptom. Scan again if the suspicious activity returns.
5. Change important passwords from a clean device only if the suspicious file ran or account activity is unexplained.

A public file scanner can help with a non-private sample, but a full device scan is more useful when the process returns because the visible executable may not be the component that launches it.

References

1. Microsoft Support. “Outlook for Windows: The Future of Mail, Calendar, and People on Windows 11.” Microsoft, accessed November 5, 2026. Mail, Calendar, and People retirement and migration
2. Microsoft Support. “Repair apps and programs in Windows.” Microsoft, accessed November 5, 2026. Repair apps and programs in Windows
3. Microsoft Learn. Get-AppxPackage (Appx). Microsoft, accessed November 5, 2026.