I have noticed for the last few days something odd that has never happened before to me. The File Explorer keeps coming up. Currently as I type this 4 instances of File Explorer are up. I had only seen this before after a power outage but once one instance. How can I fix this? It is slightly annoying.
Hi, what is your Windows build? Windows key + R, winver.
As you mention a power outage (past) please check your disks:
We need to try to check whether there's any form of corruption, and then try to check if it's being launched by some other source.
1. Hard Disk Sentinel (trial) gives the best textual summary I've seen on its GUI.
Please advise the result.
2. Now check your file system:
From an admin command or powershell prompt
[Windows key + X, click command prompt (admin)]
chkdsk C: /F
Your PC will need to restart.
Post back the result, which you can get after a restart as follows:
Read Chkdsk Log in Event Viewer in Windows 10 | Windows 10 Tutorials
or
How to read Event Viewer log for Chkdsk in Windows 10 [Tip] | dotTech
3. If ok, then from an admin command or powershell prompt please run
SFC /SCANNOW
and report the result.
If ok, please try a clean boot.
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts | Windows 10 Tutorials
Part 1
See if explorer is now launched.
If it is, please create a new user for test purposes. Log in as that user and see if explorer is now launched.
I will post more after reboot - okay no errors.
Microsoft Windows [Version 10.0.17134.285]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>SFC /SCANNOW
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
C:\WINDOWS\system32>
Last edited by Angbo0m; 08 Oct 2018 at 19:59.
Thanks for that so far.. Whilst your disks are physically fine, the HD Sentinel text is worth following up (check that for the other disks too). In one thread it was precisely correct- a cable needed replacing.
That may well be true, but whether it's related to explorer launching I obviously can't say- but anything potentially random is of interest.
Since rebooting it seems it has not come up. Seems problem is fixed? Did all the scans and went for dinner at my mom's for a few hours. Just got back now and no instances of File Explorer has launched on its own where as before many would have.
Thanks for your help! :)
Did have some new results before the reboot with Hard Disk Sentinel:
and referred me to Hard disk case: communication errorsProblems occurred between the communication of the disk and the host 178 times.
In case of sudden system crash, reboot, blue-screen-of-death, inaccessible file(s)/folder(s), it is recommended to verify data and power cables, connections - and if possible try different cables to prevent further problems.
More information: Hard disk case: communication errors
No actions needed.
Yep, that's worth following up as I said, so at least you've got a useful outcome.
Cables are not just about simple connectivity- impedance matching and possibly crosstalk are significant, as well as transmission losses- data rates are very high, so if signals are degraded or excessive over or undershoot, you could get data corruption.
HD Sentinel is given away from time to time- I posted on such a few days ago (expired now).
Quote
