Microsoft Defender for Endpoint
Troubleshooting

Troubleshoot Service Startup Problems

In brief

The article no longer includes the entry showing the default ProductAppDataPath and its Windows Defender registry location.

What Defender admins need to know

Administrators using the article to troubleshoot service startup issues will no longer find this path reference there.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

|HKLM\SOFTWARE\Microsoft\Windows Defender\Diagnostics\RolledbackPlatformHealthData = <OVERALL>:<BAD>, <AGE>:<36>, <DIRTY_SHUTDOWNS>:<22>|Default\Diagnostics\RolledbackPlatformHealthData = 0| |Default\ServiceStartStates = 0x0|HKLM\SOFTWARE\Microsoft\Windows Defender\ServiceStartStates = 0x1| |HKLM\SOFTWARE\Microsoft\Windows Defender\ServiceStartStates = 0x1|Default\ServiceStartStates = 0x0| |Default\ProductAppDataPath = C:\ProgramData\Microsoft\Windows Defender|HKLM\SOFTWARE\Microsoft\Windows Defender\ProductAppDataPath = C:\ProgramData\Microsoft\Windows Defender| |Default\IsServiceRunning = 0x0|HKLM\SOFTWARE\Microsoft\Windows Defender\IsServiceRunning = 0x1| |Default\ProductAppDataPath = C:\ProgramData\Microsoft\Windows Defender|HKLM\SOFTWARE\Microsoft\Windows Defender\ProductAppDataPath = C:\ProgramData\Microsoft\Windows Defender| |Default\IsServiceRunning = 0x0|HKLM\SOFTWARE\Microsoft\Windows Defender\IsServiceRunning = 0x1|