Help, FRV takes a lot of time to start

Submitted by alainvdm on Mon, 07/28/2025 - 12:01
Forums: 
General discussion

Hello,
For several months now, I've been experiencing an issue when starting FastRawViewer.
 
The splash screen appears immediately after launching the program, but it can take anywhere from at least 25 seconds to, at worst, over a minute before the application actually opens.
 
Previously, I never noticed this kind of startup delay, and my PC configuration hasn't changed since then.
 
I'm running Windows 11 Home (24H2) with the latest version of FRV (2.0.10).
 
Has anyone else encountered this problem? If so, how did you fix it?
Could a recent Windows update or background app be causing this?
Are there logs I could check to identify the bottleneck?
 
Thanks in advance for your help!
 
Regards,
Alain

lexa

Mon, 07/28/2025 - 12:41

Dear Alain:

Such problems are usually related to

  • 'Ghost' drives:  drive letter for some remote storage (NAS, other type of network storage) is present, but the media is offline (NAS turned off, remote storage disconnected)
  • Broken removable media or removable media reader (DVD drive, card reader, etc).

FastRawViewer inspects all connected media on start, if media is not connected or broken: this takes time.

To detect the 1st problem:  Start FastRawViewer 'As Administrator' (right click on application icon, select Run as Administrator). In this mode all network storage is disconnected (not available/not visible for the application that started 'As admin')

To detect the 2nd one: disconnect all removable storage from your computer.

To fix the problem:

  1. Disconnect/unmount ghost/broken media
  2. or use FastRawViewer Preferences - Other - Use reduced folders panel functions

If the 2nd option is used: some functions in the Folders panel will be not available; Also all media-type related settings (Preferences - Performance - Slow media) will not be used, all media will be considered local. So the 1st option is better.

--

Alex Tutubalin/FastRawViewer team

alainvdm

Mon, 07/28/2025 - 13:09

Thank you lexa, indeed I had a mapped offline network drive.
Removing it solved this issue.  Thank you very much for your quick reply and explanations.
Kr,
Alain

Alain

Add new comment