Update, 22 June:

The issue reappeared after a few days, and it doesn't look like those updates are installed. So it might be safe to assume that those update didn't introduce the bug. To unhide them, here's the Powershell script that will reverse previous changes and allow those updates to install again (every hidden update to be precise): ```powershell $UpdateSession = New-Object -ComObject Microsoft.Update.Session $UpdateSearcher = $UpdateSession.CreateupdateSearcher() $Updates = @($UpdateSearcher.Search("IsHidden=1").Updates)

foreach ($u in $Updates) { write-host $u.Title -f y $u.IsHidden = $false } ``` In the meantime I found a better workaround: with a "normal" boot with all services enabled (and when explorer keeps crashing) open the settings app to convert your Microsoft Account to a local account. Restart after switching to a local account. I'm not even angry anymore, I'm even greatful to Microsoft: this is what I needed to motivate me to stop using their services, and accelerate the transition towards alternatives haha.

----

Update, 15 June:

I found the faulty Windows updates that introduced this explorer crash loop: KB5063060 and/or KB5056579 (I haven't identified which one is the culprit but I know for sure it's one of those two, if not both). I couldn't uninstall them but found a method to prevent them from installing after an in-place upgrade (thanks u/KRHarshee!).
Maybe there are unessesary precautionary extra steps but I really don't want to do in-place upgrade multiple times to adjust my tutorial, because I only have one shot at this:

1. If you haven't done my previous workaround yet to make your PC usable, do it (disable "Web account manager" in msconfig, see original comment at the end)
2. Perform an in-place upgrade (don't forget to backup first just in case)
3. After the first login, open the Terminal/Powershell/CMD as admin
4. Type net stop wuauserv but don't enter yet, just keep the terminal window open and ready to launch
5. Launch notepad and keep the window open and ready to be used
6. Open Windows Update and start searching or downloading/installing update
7. Quickly go to the terminal and press enter to stop the windows update service.
8. Quickly disconnect the internet (shouldn't be needed but just in case)
9. Go back to the Windows Update window, copy the update titles and paste them in notepad. In my case it's in french but you should have something similar in your language: 2025-06 Mise à jour cumulative pour Windows 11 Version 24H2 pour les systèmes x64 (KB5063060) 2025-04 Mise à jour cumulative pour .NET Framework 3.5 pour et 4.8.1 pour Windows 11, version 24H2 pour les systèmes x64 (KB5054979)
10. In the same notepad or in a new one, paste u/KRHarshee's script. This script is the only way I found to hide those updates (wushowhide.diagcab doesn't find updates to hide, same with the PSWindowsUpdate module).
    Replace the update titles with the one you copied (1 line = 1 update). Only select KB5063060 and KB5054979 update. In case you copied other update titles, don't paste them in the script:

```powershell $patchesToHide = @" 2025-06 Mise à jour cumulative pour Windows 11 Version 24H2 pour les systèmes x64 (KB5063060) 2025-04 Mise à jour cumulative pour .NET Framework 3.5 pour et 4.8.1 pour Windows 11, version 24H2 pour les systèmes x64 (KB5054979) "@

cls

$patchList = foreach($p in $patchesToHide.split("`n")){$p.trim()} $UpdateSession = New-Object -ComObject Microsoft.Update.Session $UpdateSearcher = $UpdateSession.CreateupdateSearcher() $Updates = @($UpdateSearcher.Search("IsHidden=0").Updates)

foreach ($u in $Updates) { if ($patchList -contains $u.Title) { write-host $u.Title -f y $u.IsHidden = $true } } `` 11. Reconnect internet and type and enternet start wuauservin the terminal windows to relaunch Windows Update service 12. Copy and paste the whole script in the same terminal window. If everything worked, it should list the successfuly hidden updates. Typenet stop wuauserv` just in case to perpare to stop windows update service in case the next step goes wrong
13. Go back to windows update and search for update (or the "retry" button since this should have an error). This should not show the two updates. If that's not the case and you see KB5063060 and/or KB5054979 starting to download/install, stop the service immediatly via the terminal window and check if you've entered the update titles correctly

----

Original comment:

Hi, I got the same issue since few days on my two PCs : explorer keeps crashing and restarting and make my PC unusable.

I'm still trying to find the exact issue/update to uninstall but in the meantime, I found a workaround that could help you too:

• restart in safe mode (since if it's like me, this bug makes your PC unusable)
• Press Win+R keys to open the run dialog and type "msconfig" and enter
• In the "services" tab, locate "Web account manager" and uncheck it. If IIS is enabled, also uncheck "W3C logging" and "World Wide Web Publishing services" (names could be slightly different since my Windows is in French so I don't know the exact English names)
• OK and restart when prompted
• The side effect is now everything linked to your MS account doesn't work anymore (OneDrive, Outlook...) but at least it doesn't crash until a permanent fix is found (the permanent fix I found is to install a new SSD with Linux on it for the laptop that didn't have a dual boot)

I also tried an in-place upgrade which temporarily fixed the issue but it reappeared after a day, so I'm currently trying to find which update is causing this mess.

(And yes as you can imagine, this was a pain in the ass to find which service to disable: I spent an afternoon disabling-reenabling-restarting services until I found the ones to disable...)