#REAL PROBLEM 10 2 USING MICROSOFT SYNCTOY INSTALL#
#REAL PROBLEM 10 2 USING MICROSOFT SYNCTOY UPGRADE#

#REAL PROBLEM 10 2 USING MICROSOFT SYNCTOY UPGRADE#

I did an upgrade from SyncToy 1.4 or SyncToy 2.0 Beta to SyncToy 2.0 RTM and SyncToy appears to be running slower after the upgrade. The workaround is for the user to empty their Recycle Bin and re-try the sync operation. We have noticed that when a folder pair is marked with the option of Save Overwritten files in Recycle Bin, and the user’s Recycle Bin contains a large number of items (thousands), SyncToy may experience slower performance when trying to move deleted or overwritten files to the Recycle Bin. SyncToy 2.0 seems to run really slow sometimes when deleting files.

Once this sync is done, you can uncheck the option and continue normal operation. This will only copy the files where the content is actually different – but it will take more time to analyze the files since it will have to compare the file contents. After this you’ll start seeing normal SyncToy behavior for these folder pairs.Ģ) Temporarily change options on your folder pair to “Check file contents” and Run the folder pair. This “long” sync will only be required once after the upgrade, since SyncToy will ensure during this sync that the timestamp metadata is reconciled on both sides. This should be ok since you should have done a successful sync before upgrade. hit Run on the Preview window and let it complete). There are a couple of *one-time* workarounds to fix this issue:ġ) Go ahead and let the folder pair re-synchronize all files (i.e. The issue arises from the fact that SyncToy 2.0 has to re-create the folder pair metadata after the upgrade and FAT reports file times in local time and NTFS reports UTC times. memory stick or USB key), SyncToy 2.0 wants to re-synchronize all files because the file times look different. On the first sync after upgrade from SyncToy 1.4 or 2.0 Beta, where one endpoint is on a FAT16/FAT32 drive (e.g.

#REAL PROBLEM 10 2 USING MICROSOFT SYNCTOY INSTALL#

To change this – look at the nfig file in the SyncToy install folder and change the trace level from “Info” to “Verbose”. In order to get more detailed information for troubleshooting certain scenarios this logging level can be changed to “Verbose”. By default SyncToy logs information at a level of “Info”. It will also contain information about any errors that have happened during the sync. The log will contain summary information about the number of files that were synchronized and the different actions taken. Go to SyncToy 2.0 main menu and view 'File->View Log'.

I want to view information about my previous syncs.Ī.

Real problem 10-2 using microsoft synctoy