Table of Contents

Known Limitations

The following limitations are currently known for idgard Sync:

  • Moving files in Windows Explorer is only supported within the same box. Files cannot be moved locally to another box or outside the idgard drive. In these cases, they can only be copied.
  • ERM-protected Data Rooms are not supported. They may appear in the list, but idgard Sync cannot open or sync their content.
  • View-only PDF documents cannot be opened in idgard Sync.
  • Users with view permission but without upload permission can only read content locally. If they edit files locally, the affected box will enter a blocking state and further changes may no longer sync.
  • Some actions performed while idgard Sync is not running are not detected correctly. This can affect changing, deleting, moving, or renaming folders and files and may cause problems during the next sync.
  • Uploads for users who do not have read permission are blocked.
  • User data is only cleaned up during uninstallation if the logged-on user uninstalls the application for themselves. When uninstalling silently or as an administrator who is not the idgard Sync user, user-specific data — including the sync root, registry entries, the idgard Sync drive, and the context menu extension — is not removed and must be cleaned up manually or by running a dedicated cleanup script.
  • When uninstalling interactively, the application data folder may not be fully removed in some cases, especially when a large number of files is involved. After uninstalling, check that the idgard Sync folder under %LOCALAPPDATA% no longer exists. If it does, delete it manually.
  • During an upgrade or uninstall, idgard Sync cannot always be closed automatically. Always close the application before starting an upgrade or uninstall. Otherwise, the process may continue running in Task Manager even though the tray icon is no longer visible, and must be terminated manually from there.