FileVoyager’s community is growing and now, FileVoyager runs on many environments and is used by many different user profiles.
Fortunately, a lot of users give feedback and among love or hate feedbacks, there are some interesting report about dysfunctional behaviour of FileVoyager.
This is a list of the most important issues identified by me or reported by the users:
Issues preceded by this icon are considered as critical and may cause a loss of data
Issues preceded by this icon are issues that can lead to a crash of FileVoyager
Issues preceded by this icon are non-critical issues or just have a cosmetic impact
In the Viewer, OpenStreetMap doesn’t work anymore because they restricted the use of the service. The only service working without registration is Yandex.maps. -> Resolved by using the new Mercator projection proposed by OpenStreetMap since 24.1.20
When in Folder Diff (Comparison), if on item is focused and one of its parent is collapsed, the opposite pane stay expanded.
When in Search panel, the button to select target folders doesn’t work.
 Thumbnails are not shown for Office and PDF with latest Office 2016 & Windows 10. Should be investigated -> Resolved by reinstalling Office. Was not a FileVoyager issue
On Windows, GetShortName can potentially be disabled for a partition. FileVoyager makes use of GetShortName to pass file/folder paths between processes. This disabling of GetShortName can prevent some features to work properly. Â -> Resolved in 19.5.1.0
When an incompatible version of libeay.dll and ssleay.dll are installed in a system folder, they supersede those deployed with FileVoyager. -> Resolved in 16.3.12.0
The consequence is that an error message is displayed at the start of FileVoyager.
When “killing” (permanently deleting) or moving a junction or a symbolic link, the operation impacts the target of the junction or symbolic link. This issue has a high priority for the next release. -> Resolved in 15.6.15.0
When deleting items to the Recycle Bin on a partition that has no Recycle Bin, the items are permanently deleted without warning. This issue has a high priority for the next release. -> Resolved in 15.6.15.0
The shell context menu of the files or folders is themed. On some rare specific cases, this theming impacts the rendering of the context menu. In the next release, the theming of the context menu will be deactivated by default. It will be up to the user to activate it and keep it so if the rendering is not deteriorated. -> Resolved in 15.6.15.0