file explorer crashes

Hello @Doug R James,

Doug R James said:

When ever you try to copy a file or shortcut to c:\ or even Desktop file explorer crashes. with the following error in the logs.

Faulting application name: explorer.exe, version: 10.0.19041.662, time stamp: 0x996782f8Faulting module name: KERNELBASE.dll, version: 10.0.19041.662, time stamp: 0xec58f015Exception code: 0x0eedfadeFault offset: 0x000000000002d759Faulting process id: 0x1524Faulting application start time: 0x01d6ce7132ed974eFaulting application path: C:\Windows\explorer.exeFaulting module path: C:\Windows\System32\KERNELBASE.dllReport Id: f3b5f97b-208f-4c39-a3b0-e4f9e62310c9Faulting package full name: Faulting package-relative application ID:

SFC And RestoreHealth

[Q1] Have you run sfc /scannow from an elevated cmd prompt?
[Q2] If so, were there any errors or integrity violations [ ?
[Q3] Have you run Dism /Online /Cleanup-Image /RestoreHealth from an elevated cmd prompt?

Elevated Command Prompt

[1] Open an elevated cmd prompt [ Administrative ] by pressing the Win + X keys together and selecting Command Prompt (Admin).
[2] Type sfc /scannow in the cmd prompt and press <ENTER>.
[3] Type Dism /Online /Cleanup-Image /RestoreHealth in the cmd prompt and press <ENTER>.

When the above has finished processing, COPY & PASTE the output data in the cmd prompt Window into your post . . .

[4] Right-click on the title bar of the cmd prompt window [ where it says Administrator: Command Prompt ].
[5] Scroll down to Edit and click Select All.
[6] Right-click on the title bar again.
[7] Scroll down to Edit and click Copy.
[8] Paste the data into your post.

IMPORTANT

If SFC finds file errors that it CAN'T repair, the usual fix is to run the SFC and DISM commands up to three time sequentially, or until there are NO errors.

SFC Error Report

However, if there are STILL SFC errors, type . . .

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\SFC_Details.txt"

. . . into an elevated command prompt and press <ENTER>. This will create a SFC_Details.txt file on the Desktop. COPY & PASTE the information into your post or use a shared link [ One Drive, Drop Box, or Google Drive ].

I hope this helps!

Windows 10 64 bit will "work" with 2GB of RAM (the Microsoft minimum recommended amount) but be painfully slow. It is recommended to have at least 4GB or more of RAM for 64 bit Windows. For 32 Bit Windows, you can have as little as 1GB RAM (the minimum recommended amount) but again this is painfully slow. It is recommended to have at least 2GB up to 4GB of RAM for 32 Bit Windows.

If you can't get the install to work with MS's media creation tool, I would suggest using Rufus to create the bootable drive. You'll need to visit MS MCT site, download the ISO file to your PC. Then download Rufus and create your bootable drive.

The MCT is known to be corrupt from time to time. I've made the switch to Rufus about a year ago for the same reason. Since then, no issues with a clean install with Rufus.

I agree, get your Iso file 1st, verify it, then create your installer.

Hello @Doug R James,

AddRAM said:

I agree, get your ISO file 1st, verify it, then create your installer.

I agree with @AddRAM.

ISO Resources

Here is a list of resources for downloading Win 10 ISO's [ including MS Servers ] . . .

> Download Universal Windows Downloader v0.2 - MajorGeeks
> Download UUP Dump files from Windows Update servers
> Download Windows 10 Disc Image [ ISO File ]
> Media Creation Tool & ISO Downloader - Rufus
> Microsoft Windows and Office ISO Download Tool 8.44 - MajorGeeks
> TechBench by WZT - Includes OLDER Windows 10 ISO's [ RECOMMENDED ]
> Universal Windows Downloader [ Portable ] - MajorGeeks
> Windows 10 ISO & Office ISO Download Tool - Heidoc
> Windows ISO - Windows 10 Download Database

Videos

> How to Download Any Version of Windows 10 from Microsoft [ Britec ]

Create USB

> How to Create Bootable USB Flash Drive to Install Windows 10 from

If you would like Instructions or Videos on how to Image or Backup the OS then please let us know.

I hope this helps!

Normally the crash is down to disk/file system fault run a full disk check