Is 'Refresh' still working in DE? Trouble reading MFT map after failing the first time

[ThomasH]

I've had too many instances recently where if the customer drive wasn't stable-enough to read the MFT Map the first time, that even after fixing and choosing "Refresh", it still won't read the MFT markers (or whatever is necessary) that allow to make a map of the MFT or do a data analysis and Scan MFT.
However, if a new DE task is started after the repairs, (and sometimes without even doing repairs... just retrying from scratch), it will read the MFT just fine, so that the MFT map can be cloned, and Scan MFT+INDX is an option.
In the past, it always seemed that just clicking "Refresh" would open up the Scan MFT options after repairs within the DE project. Now it never seems to unless starting fresh.

Anyone else facing this issue recently... in the last 2 updates of DE?
Is there some other way to try to get DE to search again for MFT info?
See Pics of the greyed out options.

[digitalsupport]

Probably you need to un check "skip sectors on reading errors" DE will not try to read sectors with errors again at refresh.

[ThomasH]

Source of the post Probably you need to un check "skip sectors on reading errors" DE will not try to read sectors with errors again at refresh.

Thanks for the suggestion, but that was one of the first things I checked. It's unrelated to how that box is ticked, although it would seem related to the issue. The sectors are actually reading properly when tried via regular cloning, but the 'DE Browse/Explorer' feature is not refreshing the new successful reads to the file tree (is my best generic guess / explanation).
I'm very surprised nobody else seems to be complaining about or have this issue...

[300ddr]

This may be completely unrelated, but do you image to HDD or Image File/VHD? I've heard of stat/map issues when imaging to Image File (after imaging a map, some sectors are still unread). I've not noticed your issue, or the stats issue, but I only image to HDDs.

[DataMedics]

Did you try refreshing at each level? Refreshing the "2 [07]" as well as the "NTFS" and "Root" folder below it? Sometimes I've found you have to just work it from the top down and then it all works. I almost exclusively work from image files and haven't noticed any issue, but I've yet to start working with the very latest version.

[ThomasH]

I always image to drives and not img files. And, yeah, I've tried refreshing on each level. Both good questions/suggestions though.

I don't have an active case with the issue right now. It only presents itself when something doesn't read right the first time tried, yet should read ok after repairs/fixing.
There's been an update or 2 since my last experience with it, so I'm not sure if the problem still exists currently.