Yes, that's right - the opposite to the usual.
I have an old external HDD that until a recent Win10 update was seen by Defraggler as an HDD, and was therefore defragg-able. Lately, though, it is being seen as an SSD, and I foolishly "optimised" it, using Defraggler. The drive is now almost filled up with "dfoptimize_nn.bin files (where "nn" is one or more numerals).
2 questions, then:
1. Can I safely delete these files?
2. How can I get Defraggler to treat it as a normal HDD?
Forgot to say I am using the current free Defraggler (v2.22.995 (64 bit).
if they were created by DF then you can delete them, you may then want to clean up Restore Points and Recycle Bin depending on how the system handled shadowing as the drive filled up.
yep, DF has gone full circle and now reports drives the opposite wrong way for some users.
there is no 'work-around' as this version was supposedly the fix for the same (reversed) issue initially.
there was talk of introducing a manual switch that the user can tell DF what type of drive you have if it wrongly auto-detects it, but that never eventuated.
Nita - thanks very much for your reply. I'll try deleting the files & see what happens.
I've deleted the files & nothing bad has happened. I found that if you right-click the drive you still get a "defrag" option, and it has in fact cleaned up better than it has for years!
Nita - I'm running the "Home" edition of Win10, and I think that VSS is turned off by default, so hopefully I won't have any shadowing issues (assuming that is what you meant?
Thanks again.
if DF thinks the drive is a SSD, right clicking it will so Optimise Drive as well as a Defrag Drive option (no idea why - I guess old habits die hard and some users simply still defrag a SSD).
for HDD, only the Defrag Drive option is shown (obviously).
glad you got it sorted.