Hi David Afonso,
I understand how frustrating this must be, especially since you've already done most of the common troubleshooting. Based on the symptoms you've described, this points more toward a damaged Windows account authentication component or corruption within the affected user profile. Here's a few other things I can think of:
1 - Check date, time, time zone, and synchronization
Authentication errors such as 0x80048820 can occur when Windows authentication components detect time mismatches.
- Go to Settings > Time & Language > Date & Time > Enable:
- Set time automatically
- Set time zone automatically
- Click Sync now > restart Windows and check again.
- If the issue persists, press Win + S > find
Clockapp > App settings:- Scroll to the bottom, click Terminate > then Repair
- If the issue persists, go back and click Reset.
- Avoid Uninstall for now since you cannot sign into the Store at the moment and might not be able to reinstall Windows Clock. But if you still want to try:
- Click Uninstall and wait for app to be removed > restart PC.
- Visit apps.microsoft.com/detail/9wzdncrfj3pr > click Download
- Double-click the downloaded
.exeto reinstall the Windows Clock app.
2 - Reinstallation repair (keeping files and apps)
- Use built-in repair option
- Open Settings > System > Recovery > Fix problems using Windows Update
- Click Reinstall now > follow the onscreen instructions to reinstall Windows.
- If that fails, perform an in-place upgrade:
- Refer to Reinstall Windows with the installation media - Microsoft Support
- Navigate to the bottom of the page and expand In-place Upgrade > follow the instructions.
- You can also check out the instructions from one of the Moderators here: How to run In-place upgrade in Windows 11 - Microsoft Q&A
Disclaimer: Both Windows reinstallation and in-place upgrade will refresh your Windows files and operating system without removing files or applications. That being said, we always recommend that if you have important data, you should back it up first before making large system changes.
Since you tested with another Windows profile and it worked, I think it's more likely that something on your original profile was corrupted, hence the suggestions above. Just to make sure we are on the same page, you used the same account to test on the other profile, right?
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.