The most likely reason for this discrepancy is that the version reported in the Chrome Enterprise Core compliance report might not be updated in real-time until Chrome is actively running and checks in. When an engineer logs in and launches Chrome, it likely completes the update process and reports the correct version. The auto-update feature generally works in the background, and a completely different unmanaged version (option C) or a persistent network block (option D) would likely prevent updates even when Chrome is launched. A malfunctioning auto-update (option A) is less likely to resolve itself upon manual launch.

===========