We've seen a few cases where chrome://components can get into a bad state, and our standard remediation is to direct them to clear the component directory for their user data dir and trigger a component update.

If we could add an option to "Repair" the component, which would effectively perform the recommended "repair" steps:
  - Delete the component 
  - Check for update (download/ install)