# Legacy config warnings prevent every command after a Windows update

**URL:** <https://community.openclaw.ai/t/legacy-config-warnings-prevent-every-command-after-a-windows-update/66>\
**Category:** Troubleshooting\
**Tags:** approvals, configuration, troubleshooting, updates, windows\
**Created:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/legacy-config-warnings-prevent-every-command-after-a-windows-update/66 "2026-09-14T22:31:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\
**Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/legacy-config-warnings-prevent-every-command-after-a-windows-update/66/1 "2026-09-14T22:31:02Z")

</div>

> **Adapted community discussion:** Paraphrased and condensed from an anonymized public OpenClaw Discord support conversation from August 2026. Technical guidance was reviewed for OpenClaw 2026.9.3.

After updating on Windows, every OpenClaw command stops at legacy-config warnings. The report names retired Tailscale behavior, an old model policy, and a legacy exec-approvals file. I cannot get far enough to start the Gateway.

---

<div class="post-metadata">

**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\
**Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/legacy-config-warnings-prevent-every-command-after-a-windows-update/66/2 "2026-09-14T22:31:02Z")

</div>

The excerpt is a migration warning, not the underlying crash. Run `openclaw --version`, then `openclaw doctor --fix` and `openclaw config validate`. If it still fails, capture the complete Doctor output and the first real error from the Gateway logs. Avoid copying the decorative diagnostic box back into PowerShell.

---

<div class="post-metadata">

**Author:** ![ArchivedMember](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@ArchivedMember](https://community.openclaw.ai/u/ArchivedMember)\
**Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/legacy-config-warnings-prevent-every-command-after-a-windows-update/66/3 "2026-09-14T22:31:02Z")

</div>

The fuller output shows that `openclaw.json` is invalid, and the connection refusal happens because the Gateway never starts. Several old keys remain after the attempted migration.

---

<div class="post-metadata">

**Author:** ![OpenClawSupport](https://avatars.discourse-cdn.com/v4/letter/o/49beb7/32.png) [@OpenClawSupport](https://community.openclaw.ai/u/OpenClawSupport)\
**Post date:** [September 14, 2026, 10:31pm UTC](https://community.openclaw.ai/t/legacy-config-warnings-prevent-every-command-after-a-windows-update/66/4 "2026-09-14T22:31:02Z")

</div>

Back up both the config and legacy approvals file before changing anything. Stop the Gateway, let the current Doctor migrate supported fields, then validate the resulting config before starting the service. If validation still names retired properties, remove only those exact properties and move settings only where the current validator documents a replacement. Preserve model configuration, state databases, and the approvals backup.