Auto-update creates orphaned TEMP / UMFD-0 profile folders in C:\Users on every update since 15.70.5

Question

Hi,

Anyone also experiencing the below ?

Environment: Windows 11 (build 26200)TeamViewer 15.81.5 (full client, service installed), automatic updates enabled.

Issue: Every time TeamViewer updates itself, Windows fails to create a profile for the Font Driver Host virtual account (Font Driver Host\UMFD-0, SID S-1-5-96-0-0). Each failure leaves two empty folders in C:\Users: UMFD-0.Font Driver Host.NNN and TEMP.Font Driver Host.NNN. The device now has 36 of these folders, one pair for every auto-update since October 2025.

Timing (26 Aug 2026, update from 15.80.4 to 15.81.5):

14:25:55.143: TeamViewer log records RunTVUpdate: Start update installer ...\Update\update.exe

14:25:55.569: TeamViewer log records ExitDelayedWithSessionRestore: Close GUI processes for update...

14:25:56–14:26:01: Windows Application log records repeated Event 1509 (User Profiles General: "Windows cannot copy file C:\Users\Default\ to C:\Users\UMFD-0.Font Driver Host.015\ – Access is denied"), then 1533 (cannot delete profile directory), 1511 (temporary profile), and 1500 (profile cannot be loaded) for SID S-1-5-96-0-0

The same sequence happened on all 18 auto-updates between 22 Oct 2025 (15.70.5 → 15.70.6) and 26 Aug 2026. The failures start within about one second of the ExitDelayedWithSessionRestore step, well before the service is uninstalled and reinstalled.

What doesn't trigger it:

Update checks that find no new version.

Updates in Sept 2024 and July 2025 through the older GUI-initiated updater.

Updates installed externally via patch management systems.

Likely cause: The service-driven session-restore logic introduced around 15.70.5 appears to act on the font driver host's session-0 token (UMFD-0) as if it were a real user, which makes Windows try to load a profile for that account. Windows can't build a profile for UMFD-0, so each attempt fails and leaves two folders behind.

UserFrance555 · Answer

Hi,

I can confirm the same issue on my PC, and it is still occurring with TeamViewer 15.82.6.

I found many orphaned folders in C:\Users, following exactly the same pattern:

UMFD-0.Font Driver Host.xxx
TEMP.Font Driver Host.xxx

Windows Event Viewer shows the same recurring errors. For example, on 3 October 2026 at 16:11:56, Event ID 1533 reports that Windows cannot delete C:\Users\TEMP.Font Driver Host.015 because of Access denied, followed by Event ID 1511 saying that Windows cannot find the local profile and is logging on with a temporary profile. The same 1533 error is then recorded for C:\Users\UMFD-0.Font Driver Host.015.

I have the same sequence for previous occurrences, including:

* 1 Sep 2026 → .014
* 31 Jul 2026 → .013
* 26 Jun 2026 → .012
* 10 Jun 2026 → .011
* 3 Jun 2026 → .010
* 14 May 2026 → .009
* and several earlier occurrences.

I deleted all the orphaned Font Driver Host folders and disabled automatic installation of TeamViewer updates, while keeping the weekly update check enabled.

After rebooting Windows, none of the folders were recreated. I will check again when the next TeamViewer version is available and perform the update manually to see whether the issue is specific to the automatic updater or to the update process itself.

So this looks very consistent with the issue reported in this thread, and it appears that it is still present in TeamViewer 15.82.6.

Has TeamViewer acknowledged this issue or confirmed that a fix is planned?

Geoff Walker · Answer

@TVnoob67  I can't answer your question, but I looked and I have the same pairs of files in C:\Users, except only for 10/17/25 through 11/25/25.  I'm on Windows 10 with TV 15.81.5.  Now at least you know that the files aren't unique to you.