A computer feature or peripheral that has completely stopped should be separated into driver, permission and physical-connection layers before assuming component failure. For Chromebook account and settings sync, first verify the exact account and sync categories on another trusted browser.
What this covers
- Chromebook account and settings sync with this exact failure state
- Diagnosis across local profile versus Google Account sync, policy and network
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleCheck Device Manager or System Information for whether the hardware is even detected, and whether an error code is shown. Expected behavior: restore the intended bookmarks, apps and preferences for the signed-in profile.
Isolate the component boundary
ReversibleVerify the exact account and sync categories on another trusted browser. Test the peripheral on a different port or user account, and test a different peripheral on the same port. Boundary to separate: local profile versus Google Account sync, policy and network.
Correct only the proven cause
ReversibleEnable the needed category or remove/re-add the profile only after local files are backed up. Reinstall or roll back the driver, or grant the missing app permission.
Verify and stop safely
ReversibleConfirm the feature works after a full restart in at least two different applications. Do not remove the owner profile or Powerwash with unbacked-up Downloads.
Evidence ledger
Sources behind this answer
Exact questions