I have been using 3.2.7 PRO 64-bit for quite some time and more recently for the last 2 years on Windows 10 without issue.
Several months back the Windows 10 Creators Update was rolled out and installed on my HP laptop, I am now experiencing a bug that now renders this software unusable. The Scan Complete window (process) in Duplicate Cleaner does not find any Folders and Files and gives "0/0 Files Scanned (0 bytes) ..." In other words the Scan process is not finding any files on my file system/external hard disk. Any suggestions please since I really like the 3.2.7 user layout and don't want to upgrade to release 4. Many thanks for any advice in advance. /Mike
3.2.7 PRO does not detect files after Win 10 Creaters Update
- DigitalVolcano
- Site Admin
- Posts: 1864
- Joined: Thu Jun 09, 2011 10:04 am
Re: 3.2.7 PRO does not detect files after Win 10 Creaters Up
It works fine here on Win 10/Fall creator update.
first check that Scan Location Tab->"Scan subfolders" is checkmarked.
It's possible that the update has changed some of your permissions/drive settings. (Especially where the OneDrive folders are concerned).
-Try unchecking the 'Don't scan system files/folders' option/.
-Try unchecking 'Don't Follow NTFS Mountpoints and junctions' option.
There are other suggestions to try here-
https://digvolsoft.freshdesk.com/suppor ... ere-found-
One last thing to try is a factory reset-
https://digvolsoft.freshdesk.com/suppor ... e-cleaner-
first check that Scan Location Tab->"Scan subfolders" is checkmarked.
It's possible that the update has changed some of your permissions/drive settings. (Especially where the OneDrive folders are concerned).
-Try unchecking the 'Don't scan system files/folders' option/.
-Try unchecking 'Don't Follow NTFS Mountpoints and junctions' option.
There are other suggestions to try here-
https://digvolsoft.freshdesk.com/suppor ... ere-found-
One last thing to try is a factory reset-
https://digvolsoft.freshdesk.com/suppor ... e-cleaner-
Re: 3.2.7 PRO does not detect files after Win 10 Creaters Up
Thanks for the quick reply. The issue was resolved by removing the data files from under the Application Data folder. Thanks again. /Mike