This is fixed, we have identified a GPO being applied enabling DisableWindowsUpdateAccess registry key. After disabling it, it got fixed.
