Record the observed difference
Note what changed: favourites, skin, source list or an add-on's state. A different-looking interface does not establish a failed application update.
Record the Kodi version, package route and the point where the difference appeared, such as startup or loading another profile.
Inspect profile identity
Kodi's official documentation describes profile-specific settings and a supported profile-loading route. Identify the active profile through the actual interface and compare it with the intended user.
Do not assume every setting or add-on state is shared between profiles. The exact stored data depends on the configured arrangement.
Use a reversible profile comparison
Where authorised and supported, load the intended existing profile using Kodi's documented interface. Check one known personal item and ordinary navigation.
Do not create a new profile or overwrite data merely to test whether the existing one was selected. A known reference makes the comparison smaller and easier to interpret.
Separate source inventory from personal view
If the correct profile still lacks an item, inspect the current legitimate source and relevant filters. A profile change and a service catalogue change are different possible events.
A saved favourite is navigation data, not proof of continuing content entitlement or correct guide mapping.
Report the exact state
Give support the Kodi version, active profile, expected profile and the changed screen. Keep private source paths or credentials out of public notes.
No Kodi profile was loaded or inspected here. The guide follows official profile concepts and does not promise that switching profiles restores every app or account.
Check the return route with the intended viewer
After the supported comparison, verify the user can identify and return to the intended profile without relying solely on a remembered skin colour. A profile can affect navigation as well as stored preferences. If the viewer needs spoken controls, include that complete task in the check. Keep the active identity in the finished device note so a later startup choice is recognised as a profile event rather than prompting an unnecessary reinstall or reconstruction of a personal list. If the expected profile is unavailable, report that state before creating a replacement with the same name. A new empty profile is not recovery of the old data, and can make two identities look deceptively similar during later troubleshooting.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- Kodi profiles — Official current Wiki excerpt: profile-specific settings and loading; no assumption that every add-on state is shared.
- Kodi userdata — Official current Wiki excerpt: package/OS-dependent paths and profile data structure; no local Kodi files inspected.
