Not work explorer
I open the folder and it doesn't start. It is not possible to create a folder and files, etc.
Heya, Have you tried restarting your PC? I have noticed that restarting the explorer process can cause some weird issues sometimes. A restart usually fixes this.
@Raphire Yes , I've already tried everything, nothing helps. Only recovery , all files will be deleted , I 've been working on them a lot and now I can 't even copy them . How do I roll it back?
Are you able to use the Powershell Terminal to do all this?
@anmal2001 That's unfortunate. Don't reset your pc though, your files are fire. It's just explorer that's acting up.
What settings did you use with the script? The defaults, or did you select any custom options?
If you used the defaults, it's likely the change that disables web/bing search features. This can be re-enabeled with the registry file found here.
Use the button highlighted in the image below to download it.
Run that file. After that, restart or sign-out and back in to apply the change. This should fix it.
@Raphire , not work. I downloaded the file, ran it, rebooted the laptop, and it still doesn't work. It doesn't even start, when you click on a folder, it loads something and then stops
When trying to click on the folder several times, an error came out, ONCE - A failure when calling the procedure remotely.
@PrabodhGyawali yes, terminal is working
@anmal2001 That error does narrow things down. We can try a few things for that. If those fail. There's a few steps we can take to diagnose further.
First step
The first step would be to check Event Viewer for any possible errors or warnings that could point us in the right direction.
- Open
Event Viewerby searching for it in Windows Search. - Open and check both the
ApplicationandSystemWindows Logs, highlighted red.
- Filter the results for easier viewing. You can enter the filtering options via the option highlighted green in the image above.
- Apply the filters to only show
Critical,ErrorandWarningevents, and clickOK.
Please report back any recent events here.
Possible solutions
In the mean time, you can try a few common solutions.
1. Confirm/fix RPC services settings
- Open
Servicesby searching for it in Windows Search. Or by pressingWin + Rand typingservices.msc.
- Scroll down and select Remote Procedure Call (RPC). Check if this service has status
Running. - Click into the settings of this service and in the General tab, ensure that the Startup type is changed to
Automatic.
- Go to DCOM Server Process Launcher. As with the service above, confirm it is running and ensure that the Startup type is also set to
Automatic.
- Next, navigate to Remote Procedure Call (RPC) Locator, set the Startup type here to Manual.
After this, restart your PC and see if the issues persists.
2. Check for corrupt system files
This option is basically given as the default for any weird Windows issue. It may help here.
- Head to the Start bar and type CMD.
- Run Command Prompt as administrator. (Important)
- Type in
sfc /scannow, and hit Enter.
This should find and fix any corrupted files. Please report back if this finds any issues.
3. Resetting related services
It's possible some related service is not running correctly or corrupted. We can try manually stopping and starting them, and clear cache files that may be corrupted.
- Head to the Start bar and type CMD.
- Run Command Prompt as administrator. (Important)
- Copy the commands below into the Command Prompt 1-by-1 and press
Enterafter pasting each command.
net start rpcss
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
Boot into Safe Mode
If these options all fail to fix the issue, we can try booting into safe mode to see if the issue exists there aswell. You can enter it from the Setting app, but as you'll see Microsoft has made the process a bit tedious.
- Open Settings.
Win + I - Navigate to the
Systempage, then click onRecovery.
- On the Recovery page, in the Recovery Options section, click on the
Restart nowbutton next toAdvanced startup.
- Click
Restart now
- Once Windows reboots select
Troubleshoot
- Next go through the options shown below.
Advanced options>Startup Settings>Restart, then press4orF4to activate Safe mode. It's also possible to press5or6to boot into Safe mode with networking or Command prompt respectively.
Once you boot into Safe mode, check if Windows Explorer works and report back.
@Raphire After checking the events, only one error was detected in the explorer in the Application: The name of the failed application: explorer.exe , version: 10.0.22621.317, timestamp: 0xe1add17c The name of the failed module: Windows.UI.FileExplorer.dll , version: 10.0.22621.317, timestamp: 0x7d2315b6 Exception code: 0xc000041d Error offset: 0x0000000000016905 ID of the failed process: 0x0x1FEC Launch time of the failed application: 0x0x1DBB917EF4F8787 The path of the failed application: C:\Windows\explorer.exe The path of the failed module: C:\Windows\System32\Windows.UI.FileExplorer.dll Report ID: a1ae1feb-c333-4629-9eb3-fa8ca13591b6 The full name of the failed package:
- Confirm/fix the settings of the RPC services - it did not help
- Check if there are any corrupted system files: The start of the verification stage when scanning the system. The verification is 100% complete.
The Windows Resource Protection program detected the corrupted files and successfully restored them. For more information, see the CBS.Log file, which is located at the following path: windir\Logs\CBS\CBS.log. For example, C:\Windows\Logs\CBS\CBS.log . The details are included in the log file provided by the /OFFLOGFILE flag.
3 Resetting related services settings is done
4 Booting in safe mode - did not help
https://github.com/microsoft/microsoft-ui-xaml/issues/6482 - It's not decided
@anmal2001 thanks for reporting back. I find it interesting that the issue persists even in safe mode.
The exception code 0xc000041d suggests a possible error with communication between Windows and device(drivers) or an application. (See: https://superuser.com/questions/869526/what-does-the-error-message-0xc000041d-mean)
Do you happen to have any themes/tools or other software installed that interacts with or hooks into Windows Explorer or the context menu?
Another possibility could be connected usb or network storage drives. Do you have any of these connected? I have personally encountered file explorer hanging because of a connected storage drive that was not working properly.
Sfc seems to have found some corrupted files. You could try doing a more thorough repair using DISM. Open CMD as admin and run the following command to do that:
DISM.exe /Online /Cleanup-Image /Restorehealth
@Raphire I did not install themes/tools. I turned off all usb devices and rebooted them , but it didn 't help Launched DISM - successfully completed, rebooted did not help I'm making a decision to restore
@anmal2001 Have you been able to get your files? You could try using an alternative file explorer like Files, if you haven't already secured them.
@Raphire I restored the system - the explorer is normal, WHILE it's working) thank you
I wonder if a permanent patch can be made on this to resolve this if it happens again on someone else
Like a separate script and instructions or a addition in the main script to avoid this overall
I wonder if a permanent patch can be made on this to resolve this if it happens again on someone else
Like a separate script and instructions or a addition in the main script to avoid this overall
I'd happily do so, but I'm unsure what the underlying issue is.
For now, I have added the option to create a system restore point, which is enabled when running the script with the default settings. It should help people restore their systems in cases where the actual issue causing the problems is hard to pin down.
I wonder if a permanent patch can be made on this to resolve this if it happens again on someone else
Like a separate script and instructions or a addition in the main script to avoid this overall
I'd happily do so, but I'm unsure what the underlying issue is.
For now, I have added the option to create a system restore point, which is enabled when running the script with the default settings. It should help people restore their systems in cases where the actual issue causing the problems is hard to pin down.
I saw that when testing. IF I can get this to happen while testing again , I'll get you the steps to reproduce for more testing
I wonder if a permanent patch can be made on this to resolve this if it happens again on someone else Like a separate script and instructions or a addition in the main script to avoid this overall
I'd happily do so, but I'm unsure what the underlying issue is. For now, I have added the option to create a system restore point, which is enabled when running the script with the default settings. It should help people restore their systems in cases where the actual issue causing the problems is hard to pin down.
I saw that when testing. IF I can get this to happen while testing again , I'll get you the steps to reproduce for more testing
That would be greatly appreciated, as I haven't been able to reproduce this issue myself.
I deleted two comments, clearly spam.
@anmal2001 Do you remember if you selected the option to change the File Explorer home page to another page? From Home to OneDrive for example? I have found instances of people having issues with this specific change, which sound a lot like the issue you had.
@Raphire If I understood you correctly, then I chose "default" before launching. All the solutions you gave me, I tried and they didn't help. I have now installed Linux and everything seems to be fine. You should add a note: The file Explorer may stop working. You can also add the ability to create a backup and warn the user about it. I think this is a feature of the system, and the solution is to reinstall. Thanks for the help
@anmal2001 thanks for reporting back so quick. I have since made it so the script creates a system restore point before running, which should help in case this happens to anyone in the future.
Closing this issue as stale/unable to repro. If anyone encounters this issue in the future and/or has any more information on how to reproduce this, please create a new issue and link this.