AppVShNotify.exe

Application ProcessMicrosoft Corporation

Also called appvshnotify, app-v shell notify, click to run notify

WindowsApplication

App-V / Click-to-Run notify helper. Virtualized Office apps use it for shell notifications. It is not OfficeClickToRun.exe, the Click-to-Run service host.

What you need to know

AppVShNotify is virtual-app notify, not OfficeClickToRun itself.

AppVShNotify.exe is the Application Virtualization shell notify helper. Click-to-Run Office is App-V virtualized. OfficeClickToRun.exe is the updater and virtualization service. Ending the notify helper does not stop Word.

Safe?: Yes, with Click-to-Run Office
Same as OfficeClickToRun?: No. That host updates and virtualizes Office
Should I end it?: A virtual-app toast can fail

Feex says

If a Click-to-Run balloon appeared and this name is here, I leave OfficeClickToRun alone. This process is the toast helper, not the service that keeps Office current.

What is AppVShNotify.exe?

AppVShNotify.exe is virtual-app notify, not OfficeClickToRun.exe. Click-to-Run places it under Microsoft Shared\ClickToRun.

What does it do?

It surfaces notifications for a virtualized application package. OfficeClickToRun.exe still downloads updates and manages the virtual environment. WINWORD.EXE is still Word.

Why is it running?

An Office app started, a Click-to-Run package needed a shell notify, or an App-V publish finished. The helper should be quiet after the toast.

Is it safe?

Usually safe

The ClickToRun folder copy signed by Microsoft is the notify helper. An AppVShNotify.exe in Temp is not. OfficeClickToRun.exe is still a different image.

A legitimate copy normally runs from:

C:\Program Files\Common Files\Microsoft Shared\ClickToRun\AppVShNotify.exe

Click-to-Run / App-V notify
Not OfficeClickToRun.exe
Also seen under Office VFS paths

Can I end it?

Toasts can miss

Ending AppVShNotify.exe drops an in-flight notify. Office apps can stay open. Ending OfficeClickToRun.exe is a different, worse idea during an update.

Can I remove it?

Do not delete AppVShNotify.exe. Repair or uninstall Microsoft 365 Apps if you want Click-to-Run gone. Leave the ClickToRun service host in place unless you are uninstalling Office.

Should it start with Windows?

Click-to-Run can start it with an Office app. It is not a chat Startup row.

Normal resource behavior

These are contextual labels, not universal averages.

CPU: Low except during publish or notify
Memory: Small
Disk: Low
Network: None by itself. Updates are OfficeClickToRun

File information

AppVShNotify.exe file information
Executable name	AppVShNotify.exe
Common legitimate path	C:\Program Files\Common Files\Microsoft Shared\ClickToRun\AppVShNotify.exe
Publisher	Microsoft Corporation
Signature expectation	Signed by Microsoft Windows

Common problems

People end OfficeClickToRun to stop this toast

That can stall Office updates. This helper is only notify.

Stuck notify after a failed publish

Repair Office from Settings > Apps. Do not replace AppVShNotify.exe.

Troubleshooting

Diagnose before you change anything destructive.

Open file location under ClickToRun

OfficeClickToRun.exe in the same folder is the service host. This file is the notify helper.

Repair Microsoft 365 Apps if virtual apps will not start

Do not download an App-V notify exe from a forum.

Technical details

AppVShNotify.exe technical details
Image name	AppVShNotify.exe
Role	App-V / Click-to-Run notify helper

Sources and verification

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

Microsoft Learn: App-V · Application Virtualization for virtual apps
Microsoft Learn: Microsoft 365 update channels · Click-to-Run servicing is a different host
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.