# Crossplane core fails to start after upgrade: uninstall the old CRDs first
Community-verified fix: uninstall the old Crossplane CRDs before the upgraded core starts. Commenter holgerson97 hit the same startup failure on the same upgrade path and resolved it by deleting the stale CRDs (kubectl delete crd on the crossplane CRDs), after which the new core applied its own cleanly. If you are jumping several minor versions at once, clear the old CRDs first rather than letting the new core try to patch over them.
## Context from the issue
gh:crossplane/crossplane#4557: Issue crossplane/crossplane#4557 (closed, 25 comments): After upgrading Crossplane from v1.7.0 to v1.13.2, crossplane core fails to start: "cannot initialize core: cannot apply crd: cannot patch object: CustomResourceDefinition...". The old CRDs from 1.7 clash with the new ones the upgraded core tries to apply.