DISM source files could not be found

zbook said:

Isn't this the drive that had failed the Sea Tools short and long generic tests?

If so, then request a Return Merchandise Authorization (RMA).


Back up files manually or by custom install to create a Windows.old.

Files are then restored from the manual backup location or from Windows.old.
How to Restore Files from Windows.old Folder in Windows 10

Yeah it's the same drive. I ended up replacing it with a Crucial drive that i had ran seatools and a full surface test first before installing windows on it this time. Funnily enough i decided to try out dism and the source file error came back, although no chkdsk or sfc errors.

There were attempts to make backup images that had failed with CRC.

With the new Crucial drive which methods had you used to
a) install Windows
b) install or restore drivers
c) restore important files

Had you run chkdsk /b /v on the new drive?

Had you considered an in place upgrade repair to fix the source file error?

zbook said:

There were attempts to make backup images that had failed with CRC.

With the new Crucial drive which methods had you used to
a) install Windows
b) install or restore drivers
c) restore important files

Had you run chkdsk /b /v on the new drive?

Had you considered an in place upgrade repair to fix the source file error?

What i ended up doing was i used Macrium to image my original drive to my storage drive, and then restore that image to the new drive. For some reason there's a feature for imaging to ignore and log errors, but that did not work for cloning the drive.

It did have some errors but i ended up running chkdsk /r and sfc on it, and it seems like it fixed them. Currently i haven't seen any more chkdsk or sfc errors. I haven't run chkdsk /b or /v though, just /r.

In place upgrade seems like what i'll do if this source file thing persists. Strangely the tuneup bat file had resolved that source file issue previously, but not this time. At the same time i have no accompanying sfc corrupt files this time around.

Would it still be recommended to run chkdsk /b /v ? HD sentinel does not report this drive as having any bad blocks or clusters.

Unlike with the previous drive windows is not reporting bad blocks anymore, so there's that.

When there are bad blocks an image is better than a clone.

Routinely I'll run the deepest check of the drive with the /b switch since it runs overnight while sleeping.

Code:

/b	
Use with NTFS only. 
Clears the list of bad clusters on the volume and rescans all allocated and free clusters for errors. 
/b includes the functionality of /r. 
Use this parameter after imaging a volume to a new hard disk drive.

https://learn.microsoft.com/en-us/wi...s=event-viewer

Other members may comment on the above image.


With the new drive post images or share links displaying HD Sentinel result images for results on these tabs:

a) Overview
b) Temperature
c) SMART

Lifetime license for Hard Disk Sentinel (standard) - includes SSDs

zbook said:

Other members may comment on the above image.


With the new drive post images or share links displaying HD Sentinel result images for results on these tabs:

a) Overview
b) Temperature
c) SMART

Lifetime license for Hard Disk Sentinel (standard) - includes SSDs

I don't have a screenshot of it but i ran HDtune error scan prior to installing the drive and it came up with no errors/damaged blocks.

Looks good.

If you run chkdsk /b /v then post a share link into this thread.

https://www.tenforums.com/attachment...kfromevent.bat