You have an external data source or a link to another FileMaker database somewhere, which it tries to connect to on open and that could time out after a while.įileMaker is configured with a startup database, which may be on a network share or on a remote server, which may be slow to connect to. Performing these checks takes time, but should only happen on a macOS upgrade. And then you get a message telling you to throw the app away and download a new copy. If the updater updates the files and the code signature, but misses to remove an older file, which is no longer needed, the check later will fail.

You may have seen people with FileMaker Pro updated with the in-app updater. So it checks code signature and notarization state. MacOS Ventura may check regularly whether an app is still valid. Your recent files list references a network drive, so FileMaker may look for that drive on startup, which may take time and maybe time out.įileMaker tries to login to Claris/FileMaker ID and that times out if the required domain is not reachable. Then the start time should be back to normal for a while. In that case you may want to check firewall to let Windows contact it's update server to refresh the certificates once.

If you turn the Wifi/LAN off and start FileMaker offline, it may be much faster to do so.

This fails and after a few seconds, it gives up and continues doing the verify with the certificates on disk. Windows itself wants to refresh the certificates every week and does a network query to do so. Sometimes we get queries about whether our plugin may slow down FileMaker Pro starting and we like to show you various ways the startup of FileMaker may be slower than usual:įileMaker tries to verify the code signature of the plugin via Windows API calls.

Claris file maker pro