How can I troubleshoot a temporary profile issue caused by an NTUSER.DAT error ?

Pradeep Singh Arora 40 Reputation points
2026-11-17T03:43:18.19+00:00

A user is signed in with a temporary profile because Windows cannot load the NTUSER.DAT file. How can I check for profile registry corruption, permission issues, disk errors, and supported recovery options?

After a restart, a user receives the message "You've been signed in with a temporary profile" and their settings are missing.

Windows for business | Windows 365 Business
0 comments No comments

1 answer

Sort by: Oldest
  1. Emmanuel ASIFIWE 0 Reputation points Independent Advisor
    2026-11-17T06:06:50.35+00:00

    Hi,

    Because the question is tagged Windows 365 Business, I’m assuming the affected device is a Cloud PC. If it is a physical PC, please let us know because the recovery options differ.

    First, save any work created in the temporary profile to OneDrive or another approved location. Windows may discard changes in that profile when the user signs out. The Microsoft Support article on temporary profiles describes this risk. Its later suggestion to create another local administrator account and copy the old profile’s files is general Windows guidance; that should not be the primary recovery method for an assigned Windows 365 Business Cloud PC.

    Find why the original profile failed to load

    From an elevated PowerShell session on the Cloud PC, run the following shortly after reproducing the issue. Adjust the four-hour window if needed:

    $Since = (Get-Date).AddHours(-4)
    
    Get-WinEvent -FilterHashtable @{
        LogName      = 'Application'
        ProviderName = @(
            'Microsoft-Windows-User Profiles Service'
            'Microsoft-Windows-User Profiles General'
        )
        StartTime    = $Since
    } |
    Sort-Object TimeCreated |
    Select-Object TimeCreated, ProviderName, Id, LevelDisplayName, Message |
    Format-List
    

    Review the events around the failed sign-in, including their complete messages and any file path or error reported. Then check Event Viewer > Applications and Services Logs > Microsoft > Windows > User Profile Service > Operational at the same time. Microsoft recommends correlating these two logs when investigating profile loading. It also says Event 1530 can safely be ignored; by itself, it does not establish the cause here. Troubleshoot user profiles with events.

    If Event 1515 says Windows backed up the profile, check whether the affected account has a matching .bak entry in ProfileList. Use the surrounding error messages to determine why loading failed.

    Check the profile mapping and file

    While the affected user is signed in, record the SID and current profile path in a non-elevated PowerShell window:

    whoami /user
    $env:USERPROFILE
    

    Have the user sign out completely. From a separate administrator account, open Registry Editor and inspect:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
    

    For the affected SID, check whether ProfileImagePath points to the intended profile folder, whether that folder contains NTUSER.DAT, and whether a second entry ends in .bak. Back up the user’s data and the registry key before considering any registry change.

    If the event reports access denied, inspect permissions on the actual folder and hive from elevated PowerShell, replacing the example path:

    $ProfilePath = 'C:\Users\<affected-profile-folder>'
    
    Get-Item "$ProfilePath\NTUSER.DAT" -Force |
        Format-List FullName, Length, Attributes
    
    Get-Acl $ProfilePath |
        Format-List Owner, AccessToString
    
    Get-Acl "$ProfilePath\NTUSER.DAT" |
        Format-List Owner, AccessToString
    

    Check access for the affected user and SYSTEM. Avoid broad permission resets. If an error specifically reports that another process is using NTUSER.DAT, Process Explorer can identify an open handle to that file.

    If the events instead report an I/O or file-system error, collect related System log events and run the non-repairing scan chkdsk C: /scan. Protect the data and assess the reported storage error before scheduling an offline repair. chkdsk command reference.

    Recover the Cloud PC if the profile cannot be repaired

    For a recent failure, consider a Windows 365 Business point-in-time restore. There are normally 10 short-term points taken every 12 hours and four long-term points taken every seven days. Select a healthy point before the failure that is as close to the current time as possible. Going further back increases potential data loss and the risk that rolling passwords, certificates, keys, or machine credentials no longer match. Changes to the Cloud PC after the chosen point are lost; data stored externally, such as in OneDrive, is not rolled back.

    The user can select the Cloud PC’s gear icon and Restore at windows365.microsoft.com, or an authorized Business administrator can restore it on their behalf. Afterward, verify that the user can connect and that management agents and application sign-in still work. Point-in-time restore for Windows 365 Business.

    If no suitable restore point works, Reset is a last resort. It reinstalls Windows and removes apps, locally stored files, and changes to settings. Confirm that required data is backed up before an administrator initiates it through Windows 365 Business management. Remotely manage Windows 365 Business Cloud PCs.

    If the issue persists, please share the profile events from the failed sign-in and the affected ProfileImagePath. Redact names, SIDs, device identifiers, and other sensitive details.

    If these steps resolve the issue, please consider selecting Accept Answer so others can find the solution.

    Best regards,

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.