F5F Stay Refreshed Software Operating Systems I saved a big directory in Windows and File Explorer shows only one file missing, even though they are the same.

I saved a big directory in Windows and File Explorer shows only one file missing, even though they are the same.

I saved a big directory in Windows and File Explorer shows only one file missing, even though they are the same.

S
Samb142001
Junior Member
3
11-10-2016, 07:38 PM
#1
The message clearly explains the issue. I created three copies of a large folder using SyncBack Pro and Windows File Explorer. After making the copies, I checked their properties to confirm everything was correct. However, I noticed one file was missing. SyncBack confirmed all files matched perfectly, but File Explorer indicated that one copy still had an extra tiny file. The SSD version had the extra file, while the others were missing from separate HDDs. This discrepancy might be the cause. Thank you for your time.
S
Samb142001
11-10-2016, 07:38 PM #1

The message clearly explains the issue. I created three copies of a large folder using SyncBack Pro and Windows File Explorer. After making the copies, I checked their properties to confirm everything was correct. However, I noticed one file was missing. SyncBack confirmed all files matched perfectly, but File Explorer indicated that one copy still had an extra tiny file. The SSD version had the extra file, while the others were missing from separate HDDs. This discrepancy might be the cause. Thank you for your time.

P
palesul
Member
79
11-11-2016, 11:29 AM
#2
Windows generates a concealed "Thumbs.db" file under specific conditions, such as when you open it with larger icons (it stores thumbnail images created by the explorer). You can disable this behavior via the registry or Local Group Policy Editor if you find it bothersome. Enable hidden files and check the original folder; alternatively, use WinMerge to compare directories and identify differences accurately.
P
palesul
11-11-2016, 11:29 AM #2

Windows generates a concealed "Thumbs.db" file under specific conditions, such as when you open it with larger icons (it stores thumbnail images created by the explorer). You can disable this behavior via the registry or Local Group Policy Editor if you find it bothersome. Enable hidden files and check the original folder; alternatively, use WinMerge to compare directories and identify differences accurately.

_
_DarkStone_
Member
227
11-12-2016, 02:24 AM
#3
Thank you! I see you're looking for an explanation of the notification symbol. It usually indicates a file update or completion in WinMerge.
_
_DarkStone_
11-12-2016, 02:24 AM #3

Thank you! I see you're looking for an explanation of the notification symbol. It usually indicates a file update or completion in WinMerge.

M
MCjeepers1009
Member
212
11-12-2016, 05:19 AM
#4
The symbol indicates it appears on just one side of the comparison. The file name is likely "desktop.ini," which holds folder configuration details for Windows.
M
MCjeepers1009
11-12-2016, 05:19 AM #4

The symbol indicates it appears on just one side of the comparison. The file name is likely "desktop.ini," which holds folder configuration details for Windows.

T
TheBeast360
Junior Member
8
11-12-2016, 07:11 AM
#5
It seems the issue lies in desktop.ini, which hasn't been detected by syncback as a change. The first three files in the folder now begin with "~$" instead of their usual names. This could be a bug, a bit flip, or an error I made during setup. Since they aren't critical and are no longer accessible, you might want to delete them. You're wondering what's causing this odd behavior so you can avoid it in the future—haha.
T
TheBeast360
11-12-2016, 07:11 AM #5

It seems the issue lies in desktop.ini, which hasn't been detected by syncback as a change. The first three files in the folder now begin with "~$" instead of their usual names. This could be a bug, a bit flip, or an error I made during setup. Since they aren't critical and are no longer accessible, you might want to delete them. You're wondering what's causing this odd behavior so you can avoid it in the future—haha.

C
coolaoliver
Junior Member
26
11-19-2016, 05:09 PM
#6
I've noticed that when an MS Office program launches a file and then crashes, it often creates temporary files that Office typically removes when it closes correctly. The original files are likely still present, and these temporary files can be safely deleted without any issues. After some investigation, I'm curious: (I've always been intrigued by how Office handles this...)
C
coolaoliver
11-19-2016, 05:09 PM #6

I've noticed that when an MS Office program launches a file and then crashes, it often creates temporary files that Office typically removes when it closes correctly. The original files are likely still present, and these temporary files can be safely deleted without any issues. After some investigation, I'm curious: (I've always been intrigued by how Office handles this...)

G
GodPlayer312
Member
60
11-19-2016, 08:28 PM
#7
It's clear you're recalling something important. Thanks for sharing, and you're welcome!
G
GodPlayer312
11-19-2016, 08:28 PM #7

It's clear you're recalling something important. Thanks for sharing, and you're welcome!