Skip go content

FileCoAuth.exe

Application ProcessMicrosoft Corporation

Catalog search terms filecoauth, file co-authoring, onedrive file co-authoring

WindowsApplication

Office file co-authoring and sync lock helper for OneDrive and SharePoint. E dey coordinate who hold di file. E no be WINWORD.EXE.

Wetin you need know

FileCoAuth na co-authoring lock helper, no be WINWORD itself.

FileCoAuth.exe dey manage co-authoring locks for Office files on top OneDrive and SharePoint. WINWORD.EXE still dey edit di document. Burst of short FileCoAuth rows na often COM embedding, no be second Word.

E safe?
Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
Na Word?
No. Dis na di lock helper
Many short copies?
COM launch, den e fit exit
Feex tok say
If FileCoAuth dey flicker while I open shared Word file, I dey treat am as di lock helper. I no dey end WINWORD to "stop co-authoring malware."

Wetin be FileCoAuth.exe?

FileCoAuth.exe na di co-authoring lock helper, no be WINWORD.EXE. E dey stay near di OneDrive client for many PCs, and Office fit start am when cloud document need lock.

Wetin e dey do?

E dey coordinate sync locks make two people fit edit one cloud file. E no dey draw di Word ribbon. OneDrive.exe still get di tray.

Wetin make am dey run?

Word, Excel, or PowerPoint file on top OneDrive or SharePoint dey open, or Office check di lock. Short-lived copies with -Embedding dey common.

Wetin make many copies dey?

Several short FileCoAuth.exe rows fit be separate COM activations. None of dose copies na second WINWORD.EXE.

Inspect the running instance

Inside Windows PowerShell, this read-only query show matching process IDs, creation times and executable paths on this PC. (pcm)

Get-CimInstance -ClassName Win32_Process | Where-Object { $_.Name -eq 'FileCoAuth.exe' } | Select-Object ProcessId, ParentProcessId, CreationDate, Name, ExecutablePath | Format-List

No result or a path we no fit access is inconclusive. Protected processes fit restrict access, and process IDs fit be reused. Keep personal paths local. (pcm)

Use the file-identity guide to compare signatures and product metadata. A filename alone no fit establish safety. (pcm)

E dey safe?

Check dis running file

FileCoAuth wey Microsoft sign under di OneDrive version folder or Office16 na di helper. FileCoAuth.exe inside Temp no be am. Dis one still no be Word.

Compare the recorded location with the actual file. A familiar folder alone no fit establish identity. (pcm)

C:\Users\<you>\AppData\Local\Microsoft\OneDrive\<version>\FileCoAuth.exe

  • Dem still dey see am under Microsoft Office\root\Office16
  • Dey often start with -Embedding
  • No be WINWORD.EXE

I fit end am?

Cloud file locks fit fail

To end FileCoAuth.exe fit drop co-authoring session. Di document window still be WINWORD.EXE. Save inside Word if di UI still dey respond.

I fit comot am?

Unlink OneDrive or uninstall Office

No delete FileCoAuth.exe. Stop to use cloud co-authoring by working on top local copy, or unlink OneDrive. To delete WINWORD no dey comot dis helper.

E suppose start with Windows?

Office or OneDrive dey start am on demand. E no be Startup Apps entry wey dem name FileCoAuth.

Measure resource use

Measure the current process rather than assume a universal baseline
CPU and memory Compare several observations for the same PID and workload. This entry get no independently measured universal baseline. (pcm)
Disk and network Attribute activity to the actual process and current task; a filename alone no fit establish expected destinations or transfer volume. (pcm)

File information

FileCoAuth.exe file information
Executable name FileCoAuth.exe
Recorded installation path C:\Users\<you>\AppData\Local\Microsoft\OneDrive\<version>\FileCoAuth.exe
Publisher Microsoft Corporation
Signature check Inspect the actual file; this entry no dey certify its certificate identity. (pcm)

Common wahala dem

Many processes dey fear people

COM fit start helper per document probe. Dat one no be Word clone farm. Check how long each row dey live.

File lock after pesin kill di helper

Close di Office app, den reopen di cloud file. No delete WINWORD to clear SharePoint lock.

How to troubleshoot

Diagnose before you change anything wey fit scatter things.

Close di Office document, den reopen from OneDrive

Dat one dey restart di lock helper cleanly. To end WINWORD mid-edit dey put di buffer for risk.

Confirm say di path na OneDrive or Office16

AppData\Local\Microsoft\OneDrive or Office16 na dis article. FileCoAuth.exe on top desktop na different file.

Technical details

Technical details
FileCoAuth.exe technical details
Image name FileCoAuth.exe
Role Office / OneDrive co-authoring lock helper

Check the identity of running file

A filename alone no fit establish safety. Verify the actual path, signature and product identity. (pcm)

Sources and verification

Recorded source label: August 2026. Dis label no establish independent verification. How we dey do research.

Dis article make sense to you?

Yes or no dey enough. Choose reason if you want, or add short note.

Dis article make sense to you?