Microsoft Defender for Endpoint
Troubleshooting

Troubleshoot Service Startup Problems

In brief

The troubleshooting page corrects the `ProductAppDataPath` registry value from `Microsft` to `Microsoft` in the Windows Defender data path.

What Defender admins need to know

Administrators following the troubleshooting guidance now have the accurate registry path; no action is required.

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\Microsft\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|