You could maybe try searching these forums for similar questions, as there have been hundreds, and it's virtually certain whatever the reason is, it's been covered before. With the absence of detail provided so far (for example: old/new paths (exactly, maybe with screenshots), resources/devices involved, how you moved them, Windows version, SB version - every little helps.), it's unlikely anyone can tell for sure (or even guess).
The other frequent culprit is not realizing that the profile is displaying 'absence' of corresponding files on your 'new' Destination if a filename is listed faintly on one side with no date/time/size shown, it means SB can't see it on that side at all, suggesting your Destination string actually doesn't match the new location (typos, etc). Given that you haven't stated what your Destination (nor your Source) is, and what protocols are being used to connect to either of them, nor any other profile settings that might change default functionality, it's hard for people to speculate further, but it may be that whatever process you used to 'move' the files did not preserve the LastModified date/time stamp, so now they don't match the Source (they may now be stamped with the date/time of the move, for example). What the differences are, and what caused those differences is probably the question you need to figure out (SB is only detecting/displaying them). Your profile is presumably set to detect differences & remedy them by overwriting one side with copies of the other. The clue is in the window name, and if files are listed / copying proposed, differences have been detected. You need to check the Differences window and see what differences it has detected? (No-one else can see your screen right now but you.).
0 kommentar(er)
