Default App Change and Desktop Flashing Issue After Hybrid to Entra Join Migration

Question

I ran into this on three computers today. They were migrated from Hybrid-joined to Entra-joined. Users who have previously logged into the PC cannot change their default applications, and all icons on the Desktop flash regularly, as one would expect them to do when the default application has changed. A user who has never logged into the computer does not experience this issue. Any advice?

Question Posted by Greg Ernest in the HTMD FB group

Default App Change and Desktop Flashing Issue After Hybrid to Entra Join Migration- Fig.1
Default App Change and Desktop Flashing Issue After Hybrid to Entra Join Migration – Fig.1
solved 0
, admin 2025-05-28T15:44:27+05:30 4 Answers 198 views Beginner
0

Answers ( 4 )

  2. VAISHNAV K
    1
    2025-06-12T23:21:21+05:30
    Reply

    Hi Rasmi,
    The issue you’re describing, flashing desktop icons and inability to change default applications after migrating from Hybrid Azure AD Join to Entra Join, is commonly associated with profile corruption or permission inconsistencies in the user’s local profile. Since the issue only affects previously logged-in users (before the join type changed), the following root causes and solutions apply.

    Likely Root Cause:-
    Residual hybrid join artifacts in the profile:-
    Registry keys or profile entries tied to the old domain SID or hybrid join state conflict with the new Entra join environment.

    Broken UserChoice registry permissions:-
    Windows 10/11 stores default app settings in HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts\UserChoice. If the Entra-joined identity doesn’t have permission to modify these entries (still locked to the hybrid user SID), the system will attempt to update them and fail repeatedly, resulting in icon refresh loops.

    FSLogix (if used):-
    If FSLogix is used for profile containers, improper cleanup of legacy identifiers can cause similar issues when the join method changes

    Solution:-
    Since new users don’t experience the issue, creating a fresh profile for the affected users will usually resolve it.
    Rename the existing profile (e.g., C:Usersolduser → olduser.bak).
    Reboot and log in again to let a new profile be created.
    Migrate the necessary data manually from the old profile folder.

    Or try Fix Registry Permissions:-
    Open Regedit > Navigate to HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts
    Expand extensions like .pdf, .htm, .jpg, etc., and delete the UserChoice subkeys.
    Restart Explorer or reboot the PC.
    Now, try setting the default apps again.
    You can also use a Remediation Script via Intune.

    Best answer
  4. adamscott3231
    0
    2025-05-31T14:10:00+05:30
    Reply

    good

  6. Rasmi p
    0
    2025-05-28T19:38:37+05:30
    Reply

    Replied by Jeff Loiselle

    You migrated production machines from hybrid to Entra?

    Replied by Greg Ernest

    It turns out the 2025-05 Cumulative patch for Windows 11 broke the process with a third-party vendor.

  8. Rasmi p
    0
    2025-05-28T19:38:10+05:30
    Reply

    For more details – Compare Hybrid Vs Entra Joined for Autopilot Avoid Using Entra Hybrid Joined with Autopilot – https://www.anoopcnair.com/compare-hybrid-vs-entra-joined-for-autopilot/

    Replied by Joseph Lavallee

    The local cached user account is no longer the same SID / UUID…. New account, essentially. I would expect weird stuff to happen.

    Replied by Greg Ernest

    How do I fix this? Otherwise, it would seem the user’s local Profile is shot. With 150 PC’s done, I’ve never seen this.

    Replied by Rickard Brander

    How do you ”migrate” from Hybrid to Entra?

Leave an answer

Sorry, you do not have permission to answer to this question .