Just FYI.. We identified the issue to be with 1 startup .ps1 script (Part of the GPO). Thats in place to un-install default MS apps that gets installed. The script was removed. Thank you!
Group Policy's loopback feature on windows 11 24H2 is crashing explorer for domain users.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
I'm part of IT Support for an organization and currently dealing with an issue. We have KIOSK machines setup in our office with Group Policy's loopback feature. It is currently in "replace" mode as we wanted it that way. All was fine until we decided to upgrade our Windows 11 systems from 23H2 to 24H2. Post the upgrade the explorer keeps crashing consistently and domain users who login basically cannot do anything. The screen keeps flickering/refreshing every 10 sec or so. We have a local admin account with LAPs enabled which seems to be working fine. Any help will be appreciated
Log Name: Application
Source: Microsoft-Windows-Winlogon
Date: 4/9/2025 7:41:37 PM
Event ID: 1002
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: XXXXXXXXXXXXXXX
Description:
The shell stopped unexpectedly and C:\windows\system32\userinit.exe was restarted.
Event Xml:
1002
0
4
0
0
0x80000000000000
2998
Application
XXXXXXXXXXXXXXX
C:\windows\system32\userinit.exe
Log Name: Application
Source: Application Error
Date: 4/9/2025 7:18:53 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: XXXXXXXXXXXXXXX
Computer: XXXXXXXXXXXXXXX
Description:
Faulting application name: Explorer.EXE, version: 10.0.26100.3624, time stamp: 0x42353d5a
Faulting module name: ucrtbase.dll, version: 10.0.26100.3624, time stamp: 0x45295404
Exception code: 0xc0000409
Fault offset: 0x00000000000a4ace
Faulting process id: 0x26F4
Faulting application start time: 0x1DBA9561F2A5332
Faulting application path: C:\windows\Explorer.EXE
Faulting module path: C:\windows\System32\ucrtbase.dll
Report Id: 4bd7482d-aaa6-40ba-b715-f919c7b7548b
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
1000
0
2
100
0
0x8000000000000000
2661
Application
XXXXXXXXXXXXXXX
Explorer.EXE
10.0.26100.3624
42353d5a
ucrtbase.dll
10.0.26100.3624
45295404
c0000409
00000000000a4ace
0x26f4
0x1dba9561f2a5332
C:\windows\Explorer.EXE
C:\windows\System32\ucrtbase.dll
4bd7482d-aaa6-40ba-b715-f919c7b7548b
Windows for home | Windows 11 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
3 answers
Sort by: Most helpful
-
Anonymous
2025-04-23T11:36:55+00:00 -
Anonymous
2025-04-15T11:31:49+00:00 Hey Zack,
Thank you for the response. I'll try to follow the steps you suggested. Drivers and patches have been updated however the steps 1 and 2 will probably take some time. This policy is currently linked to other OUs as well hence I need to be cautious. I'll update here if I have anything new.
-
Anonymous
2025-04-14T17:44:38+00:00 Hello Bengia,
Welcome to Microsoft Community,
I can totally understand your concern. Please follow these steps to troubleshoot the issue.
1) Test with Loopback in "Merge" Mode:
- Change the loopback processing mode from "Replace" to "Merge" in Group Policy settings.
- Restart the affected machines and test domain user login.
2) Check Group Policy Settings:
- Review applied policies for conflicts, especially those affecting the shell or user environment.
- Disable non-essential policies temporarily to identify the problematic one.
3) Update Windows and Drivers:
- Ensure all systems are fully updated, including drivers and patches for Windows 11 24H2.
4) Revert to 23H2:
- If the issue persists, consider rolling back to Windows 11 23H2 until compatibility issues are resolved.
If the issue still persists. Please reach out to Microsoft live support on - Contact Us - Microsoft Support or get help app.
I hope this will work for you.
Kind regards
Zack | Microsoft Community Support Specialist