ConfigDeviceHealthMonitoringServiceInstance - Error 404 - The system cannot find the file specified.


I have a machine (perhaps many, though I haven't searched widely yet) that is throwing the following error in the Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin log every time it syncs and reapplies settings from Intune.

MDM ConfigurationManager: Command failure status. Configuration Source ID: (908E6CB3-91A8-4F26-9383-F7B8C284976F), Enrollment Name: (MDMDeviceWithAAD), Provider Name: (Policy), Command Type: (Add: from Replace or Add), CSP URI: (./Vendor/MSFT/Policy/Config/DeviceHealthMonitoring/ConfigDeviceHealthMonitoringServiceInstance), Result: (The system cannot find the file specified.).


I don't believe I have any configurations setting this value -- in fact, i don't even think this is a setting that can be set intentionally via Intune.  I don't know what it does if you do manage to set it.  I've dug around in the registry and I've found the Configuration referenced by the Source ID and it appears as follows --




There is no ConfigDeviceHealthMonitoringServiceInstance specified at all.  The merged view under the current key shows no alternative source for the setting either.



What else can I even look at to get to the bottom of this?






5 Replies
Hi, Which windows version/build are you using. What kind of error is intune giving you when you look at the device health monitoring policy? Most of the times it's licensing or the windows version/build

@Rudy_Ooms_MVP, thanks for responding.


Windows 10, Version 21H1 (OS Build 19043.1237)


The device passes all pertinent device compliance policies and the only "Windows health monitoring" profile we deploy reports that a "Deployment Status" of Succeeded.


If I might ask, what kind of licenses did you setup? and are those device pro or enterprise? As I have seen this happening a lot when the device needs to be enterprise.. But looking at the other settings like AllowDeviceHealthMonitoring = 1 and ConfigDeviceHealthMonitoringScope... they are pushed like they should

I guess i didnt read the question that good :) . When looking at the device health monitoring CSP.

The ConfigDeviceHealthMonitoringServiceInstance is not in it... so When it's not in the csp, you will get that warning indeed. If you are not expecting issues.. i guess you could just ignore it