Office updater logs false “UpdateEnabled not found” warning despite registry compliance

Body: OfficeClickToRun.exe logs the following during scheduled updates:

Code
UpdateEnabled property not found in registry.
Click-to-Run client found. Triggering update...
Office update routine completed.

However, all relevant registry flags under HKLM\SOFTWARE\Microsoft\Office\ClickToRun are correctly set (UpdateEnabled, EnableAutomaticUpdates, OfficeAutomaticUpdates, etc. = 1).

ProcMon confirms the updater queries this path, yet logs NAME NOT FOUND.

Updates still succeed (LastScenarioResult: Success), so this appears to be a cosmetic error from legacy registry validation. It confuses admins and monitoring systems.

Ask: Can Microsoft standardize updater checks to avoid false warnings? Is this legacy logic still active in current Office builds?