Normally leaving the Header Image setting empty in the Customizer does not generate the issue you had, so there must have been some other WordPress or Weaver Customizer interface bug that allowed that. I’m just trying to figure out how to prevent that issue in the future.
