Troubleshooting policy issue: temporary error suppression was prioritized over root-cause repair

[jmylot]

Summary

During Windows uninstall troubleshooting, the assistant initially moved toward suppressing error prompts instead of prioritizing root-cause repair (restoring missing uninstall binaries/installer state).

This created extra steps and reduced user trust, even though remediation was later redirected.

Problem

The assistant behavior was misaligned with user intent:

• User intent: fix (repair) the underlying cause.
• Initial assistant direction: reduce visible errors first.
• Result: delayed root-cause actions and unnecessary friction.

Why this matters

For system troubleshooting, users expect:

1. Root-cause diagnosis first.
2. Repair-first plan.
3. Any temporary workaround to be clearly labeled as temporary.
4. Immediate transition from workaround to permanent fix.
5. Guardrails around destructive or irreversible actions.

Observed behavior

• Temporary mitigation was proposed/performed before a stable repair path was enforced.
• Registry cleanup and visibility-oriented actions appeared before a fully constrained reinstall/rebuild plan.
• This gave the impression of "hiding symptoms" rather than "repairing the system."

Expected behavior

1. Detect and state likely root cause first.
2. Lock into a repair-first workflow when the user asks for "fix/repair."
3. Mark any stopgap action explicitly as temporary and optional.
4. Require a follow-up permanent remediation step automatically.
5. Block irreversible actions unless:
   • rollback/backup is confirmed, and
   • a validated repair path is ready.

Requested improvements

Intent guard:
If user says "fix/repair/修正," prioritize root-cause remediation and reject symptom-hiding defaults.

Workflow policy:
Diagnose → repair plan → execution → verification.

Safety policy:
For registry deletion or uninstall-entry cleanup, require backup + explicit recovery path.

UX policy:
Display "Temporary workaround" labels and auto-schedule permanent fix steps.

Suggested acceptance criteria

• In repair-intent sessions, assistant proposes root-cause repair as first option in >=95% of cases.
• Any workaround is labeled temporary and paired with a permanent follow-up step.
• Irreversible actions are gated by backup confirmation and rollback instructions.
• Post-action verification includes both functional check and state integrity check.

Environment

• OS: Windows
• Scenario: Installed apps uninstall errors ("path not found" across multiple apps)
• Context: Missing uninstall executables / missing installer cache references

---

Short version: The assistant should prioritize root-cause repair over symptom suppression in troubleshooting flows, especially when users explicitly ask to "fix" the issue. Temporary mitigations must be labeled and followed by mandatory permanent remediation. Irreversible cleanup actions should require backup + validated recovery path.