SDXHelper.exe

Application ProcessMicrosoft Corporation

Also called sdxhelper, office sdx, sdx helper

WindowsApplication

Office and Microsoft 365 Shared identity helper (Office SDX). It is shared sign-in and licensing support, not WINWORD.EXE.

What you need to know

SDXHelper is Office shared helper, not WINWORD.

SDXHelper.exe is the Office Shared identity helper. It lives in the Click-to-Run vfs Office16 shared folder. WINWORD.EXE still edits documents. Ending SDXHelper does not save or close the Word buffer.

Safe?: Yes, with Microsoft 365 Apps
Is it Word?: No. SDXHelper is the shared helper
Should I end it?: Sign-in or licensing can stall

Feex says

If SDXHelper is here and Word just asked me to sign in, I leave the helper. I do not end WINWORD to "stop Office identity."

What is SDXHelper.exe?

SDXHelper.exe is Office shared helper, not WINWORD.EXE. SDX is the shared identity and experience stack Microsoft 365 Apps use for sign-in and license checks.

What does it do?

It helps Office apps share identity work so Word, Excel, and Outlook do not each invent a second sign-in host. It does not render the document canvas.

Why is it running?

An Office app signed in, renewed a license, or opened a shared identity prompt. A quiet helper after you close Word can still be finishing that job.

Is it safe?

Usually safe

A Microsoft-signed SDXHelper under the Office vfs shared folder is the helper. An SDXHelper.exe in Temp is not. This is still not WINWORD.

A legitimate copy normally runs from:

C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\OFFICE16\SDXHelper.exe

Click-to-Run vfs path is common
32-bit Office can use ProgramFilesCommonX86
Not Office16\WINWORD.EXE

Can I end it?

Office sign-in can stall

Ending SDXHelper.exe can leave an Office account prompt hanging. WINWORD.EXE can stay open with the document. This is not a Word quit.

Can I remove it?

Uninstall Microsoft 365 Apps

Do not delete SDXHelper.exe. Remove Office from Settings > Apps. Deleting WINWORD.EXE does not remove the shared helper.

Should it start with Windows?

Office starts it when identity work is needed. It is not a Word Startup add-in.

Normal resource behavior

These are contextual labels, not universal averages.

CPU: Short spike during sign-in or license refresh
Memory: Small
Disk: Low
Network: Microsoft 365 identity endpoints while signing in

File information

SDXHelper.exe file information
Executable name	SDXHelper.exe
Common legitimate path	C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\OFFICE16\SDXHelper.exe
Publisher	Microsoft Corporation
Signature expectation	Signed by Microsoft Windows

Common problems

Filename mills treat any Office helper as Word malware

Path and Microsoft signature decide this one. WINWORD.EXE is the editor. SDXHelper is shared identity.

Activation loop after someone killed the helper

Sign out and back in from an Office app File > Account. Do not replace WINWORD to fix licensing.

Troubleshooting

Diagnose before you change anything destructive.

Sign out, then sign in from File > Account

Do that in Word or Excel. SDXHelper is the helper for that flow. Task Manager End on WINWORD only drops the document.

Open file location before you blame Word

vfs\...\Microsoft Shared\OFFICE16\SDXHelper.exe is this article. Office16\WINWORD.EXE is Word.

Technical details

SDXHelper.exe technical details
Image name	SDXHelper.exe
Role	Office Shared identity / SDX helper

Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.

Microsoft Learn: Office authentication essential service · Office identity and licensing are shared services, not the Word editor
Microsoft Support: Office sign-in · Account and activation live outside WINWORD
Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.

Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.