Windows signed you in with a temporary profile

Protect the current session first

Files created or changed in a temporary profile can be lost when that session ends. Save open documents and copy them to a trusted external drive or another verified location outside the temporary profile. Open a copied file from that location to confirm the copy is readable.

Do not assume cloud sync has protected the session. Check the actual uploaded copy if relying on it. Avoid moving the only copy or allowing sync changes to replace known-good files elsewhere.

Confirm the account and profile path

Open Command Prompt and run the display command below. It prints the current profile folder without changing it. Compare that path with the expected account and the sign-in notification; folder names alone are not proof of corruption.

If the wrong account was selected, sign out only after safeguarding current work, then choose the intended account. If Windows explicitly created a temporary profile for the correct account, continue with profile diagnosis rather than repeatedly changing the password.

echo %USERPROFILE%

Retry a normal sign-in with evidence preserved

After saving the temporary-session work, use Restart and sign in to the intended account again. Check whether the notification returns and whether your usual Desktop and Documents open. Record the result instead of treating a familiar wallpaper as sufficient proof.

If the error recurs, use another existing administrator account only if you are authorized and know its credentials. A working second account suggests the failure is tied to the original profile; failures across accounts point toward a broader issue.

Check availability before profile repair

From a working account, inspect free space and any disk or file-access errors. Do not run repair utilities against an unstable drive before protecting important files. If the usual profile folder is present but inaccessible, preserve the permission error rather than taking ownership of the entire Users directory.

On a work or school PC, profile loading may depend on organization-managed storage and sign-in services. Send the error, account type, and timing to IT. A local registry recipe cannot safely substitute for knowing how that profile is managed.

Plan recovery without destroying the original profile

If the normal profile will not load, a replacement profile may be part of recovery, but verify a backup and administrator access first. Keep the original profile intact until documents, application data, and any encrypted files have a confirmed recovery path.

Do not delete profile registry entries, rename profile folders, disable security services, or reset the PC as an exploratory step. Copying ordinary documents into a new account does not automatically restore saved credentials, encryption access, or every application setting.

Verification

• Confirm the temporary-profile warning is absent after a normal sign-in.
• Open known documents from the usual profile and verify the saved work recovered from the temporary session.
• Create a harmless test file in Documents, sign out normally, sign back in, and confirm it remains available.

When to stop

Stop before profile deletion or registry repair if files are unbacked up, encrypted data is involved, no authorized administrator account works, or disk errors appear. Managed profiles require the organization’s recovery process; preserve the original data and error details.

Review the safe troubleshooting workflow before any broader recovery step.