PC familiaux et partagés
Profiles, games, and why “I never use it” is not enough when others log in.
Windows keeps separate profile data under C:\Users\…. A program removed “for everyone” can still leave per-user shortcuts, cloud-sync stubs, browser profiles, and game saves in accounts you are not currently viewing. On a shared PC, the risk is not only breaking the OS—it is breaking someone else’s workflow without realizing it.
Ask before you assume idle software
The polite default is to ask every regular user whether they still launch the program, use its background updater, or rely on files in its install directory. Kids’ game clients and education portals are notorious for hiding large libraries under another profile’s Documents or a custom drive letter.
Checklists that prevent drama
- Confirm who else uses the machine and whether they still need the app—even if it looks unused on your desktop.
- Review each account’s Startup list (Settings → Apps → Startup) for updaters tied to the product you plan to remove.
- For game stores and creative suites, verify shared libraries and offline installers are not referenced by another login before you delete cache folders.
- Leave a short note on the desktop or shared doc listing what you removed and when, so the next “family IT” session starts informed.
Leftover scans on multi-user boxes
When you run a leftover scan, pay extra attention to paths under other users’ Données d'application trees. Deleting another person’s configuration folder “because the uninstaller finished” can reset their saved layout or signed-in add-ins. If in doubt, log in as that user once, launch the app to confirm failure mode, then decide.
Guest accounts and “loaner” profiles
If you use a shared guest profile for visitors, uninstall decisions there can still touch machine-wide components. Prefer removing software from the account that installed it when possible. For school or work devices, follow domain policy: roaming profiles can rehydrate shortcuts you thought you deleted.
Games, saves, and cloud sync
Many launchers sync saves to the cloud automatically. Uninstalling the launcher does not always delete cloud copies, but it can orphan local caches large enough to matter on small SSDs. Confirm whether family members still need offline access before you wipe a Steam or console-companion library folder.
Réponses rapides
- “Nobody uses this app” — is that enough?
- Only if you asked every person with a profile on the PC. Silent background updaters and shared game libraries are the usual surprises.
- Should I delete another user’s Données d'application leftovers?
- Only after you logged in as them or got explicit consent. Settings, extensions, and saved layouts often live only there.
- We share one Microsoft account for the Store. Any caveats?
- Store installs and licenses can be tied to that account across profiles. Document which apps were installed for whom before you remove anything with “Microsoft” in the publisher line.
Keep going: Shared PCs reward documentation: who uses what, which launchers own the big folders, and what you already removed. See the features overview and guides for uninstall hygiene the whole household can follow.