Updates, profiles and uninstall
Change installations without discarding engineering work.
Before an update
Check release availability, the platform/architecture and the supplied source revision, hash and signature information. A source commit or browser preview is not an independently qualified native installer.
Save your engineering documents and retain independent backups of projects, conversations and essential configuration. Keep the last known-good installation until the new artifact has been verified. Do not overwrite an actively running installation.
Verify an artifact
Use the copyable SHA-256 commands in installation, then compare the entire value with the published value for that exact file. Check that an existing desktop shortcut points to the intended edition and revision. Never install an older artifact merely because it starts more easily.
On Linux, follow the documented archive/runtime prerequisites rather than copying a whole unrelated SDK or application profile. On Windows, preserve previous installations and user data while testing a private qualification artifact.
Profiles and local work
Application settings, conversation storage and project files have different purposes. Removing an installation is not a safe way to clear a stuck request. A fresh profile does not necessarily isolate all operating-system settings; do not reset shared settings as a casual diagnostic step.
Uninstall carefully
Close only the application instance you intend to remove, after saving its documents and checking active work. Remove the installation through its supported mechanism or remove its explicitly identified application directory. Do not delete project folders, app-owned conversations, operating-system credential stores or another edition's files to reclaim space.
Revoke connected desktop access separately if that machine should no longer use the customer service. Uninstalling local files alone is not proof that server credentials were revoked.