Uninstall while retaining projects

Before you begin

• The build-specific removal instructions and a readable inventory of the intended Vector-owned components.
• Known original customer project/output folders and retained journals/accounting receipts.
• No unresolved native operation blocking removal, and saved work before affected host exit.

Follow the steps

1. Inspect unfinished work first

   Open active/recovery work and resolve or preserve the original outcome of each dispatched operation. Do not uninstall to clear an unknown-result hold.

   Checkpoint: Dependent native work is known/reconciled, or removal is explicitly blocked.

2. Record what you need to retain

   Identify customer .3dm/.rvt projects, exported artifacts, local history and necessary financial/recovery receipts. Read the exact removal plan and retained-data options for this build.

   Checkpoint: The removal scope excludes original customer folders and unrelated host settings/plugins.

3. Save and close affected hosts normally

   Save your host work and close all instances affected by connector registration changes. Do not force-kill a host or disable diagnosis because sign-in/entitlement expired.

   Checkpoint: The owned connector can be safely inspected and removed without an active host using its files.

4. Remove the owned connector through its supported flow

   Use the build's Connect removal plan and verified owned inventory. For Revit, owned registration and unreferenced payload must be considered together.

   Checkpoint: The result shows known owned removal/readback and no dangling registration; changed or foreign files produce a drift/repair report.

5. Use the normal app uninstaller

   Follow the build-specific per-user application removal instructions and review any retained-data choice before confirming. Preserve the agreed workspace/journal data.

   Checkpoint: The application installation has a known removal result; customer models and unrelated software remain outside its scope.

6. Check the remaining state

   Inspect retained project/artifact locations and the removal result. Treat account deletion, subscription cancellation and local uninstall as separate decisions.

   Checkpoint: You know what was removed and retained, without assuming a refund, canceled subscription or deleted cloud account.

Check the result

• Only verified Vector-owned installation/configuration is removed, with original models, unrelated settings and required receipts retained.
• An uncertain removal stays unresolved until inventory/registration readback explains it.

If something goes wrong

• Removal is blocked by an active or unknown native operation.

  Keep the app/journals available for inspection and reconcile first. Do not delete the package folder to force progress.

  Resume from: Known original native state.

• An owned file changed, another add-in shares the identity or the removal reply is lost.

  Inspect the original lifecycle journal and inventory. Do not delete a whole plugin directory or retry blindly.

  Resume from: Known owned registration/payload state.

• A project drive is missing.

  Restore the drive before assessing retained data. Missing access is not proof that the uninstaller deleted files.

  Resume from: Original local locations accessible.

Continue with a related guide

• Resolve work before removal
• Keep safe removal evidence
• Cancel a subscription separately
• Build-specific uninstall help