LiveMode is the feature that will cause the results to be displayed when the client is opened and is what causes the Console to show a match location as no longer existing.
Here is the details of the setting that enables/disables LiveMode:
Beginning with version 6 of the client, by default, results that are visible in the UI are automatically encrypted, saved on exit, and automatically displayed in the client UI when a user opens the client interactively and signs into their profile. The save uses a "machine key" to prevent the opening of the results file on another computer.
When CheckPreviousResults is enabled and the client is configured to communicate with the console, file results will be automatically and transparently checked for existence . If the files no longer exist (for example, they were deleted from within Windows Explorer), that information will be communicated to the console. To disable LiveMode, set this to "Disable" (0). When disabled, the other LiveMode settings will have no effect, regardless of their values.
In the client UI, the checkbox for "Display previous search results on startup" enables both this setting and ShowResultsInClientUI.
This check for the file existing is performed the next time a search is run in the same context as the search that found the match was run (Local Logged on User or Local System Account). So if the search is run with the user logging into the Client using a Profile then the Client would need to be run again using a Profile to have the results read from the previous search, and if the search was a task run as the Local System Account then another task would need to be run in that same context for the files to be considered to no longer exist if they were deleted outside of the Client.
It may also be that you are looking at the first time the match was found and not the most recent in the results on the Console. That behavior can be changed with the following setting on the Console's>Admin>Personal Settings screen:
Display the timestamp of the first time the identity match was found
By default, the Console displays the first date and time that the identity match was found. For example, when viewing the Results Grid, the Date/Time column will note the first time the result was found and that information will not be updated each subsequent time that the result is found. To modify this behavior to always display the most recent time that the result was found, clear this check box.
The results will not be removed from the Console but should be marked as no longer exists in the Actions column on the Results screen when viewing the latest time the match was found.
What is most likely occurring is that the livemode results from the previous search needs to be gone through and each location attempted to be connected to so the Client can determine if it still exists. This can take some time. You can see this behavior in a Client when you open the Client and it displays the previous searches results, which takes some time to load, and then when you click on a location to preview the match in the Client it can take a minute to load that information. For Scheduled Tasks run as the Local Logged on User you can just open the Client manually and let it sit to go through the previous searches livemode db file. When the previous search searched a very large set of data it may take a while to go through that previously searched data set. If the Client is only opened for a minute and it had not completed analyzing the previous searches data set then the next time the Client is opened it will continue on with that old data set before proceeding to the next searches data set. This can get backed up in time and the solution is to open the Client and leave it open so it can catch up with the old livemode data.
The issue with searches run as the Local System Account is that it may have a backlog of searches to go through and the Client is not open long enough for it to finish the old livemode data and you cannot just open the Client to let it catch up. The livemode process runs in the background so as long as the Client is open it can run. For the Local System searches you could run a very long search to allow the livemode to hopefully be all processed. You can view the livemode db files size to get an idea of how much had not been processed when you compare to other livemode db files that are up to date and immediately sending the no longer exists info to the Console.
Livemode is stored in a database always called “lastsearchresults.db”.
The local user's livemode db is in the following folder:
The Local System tasks always use the database located in the C:\ProgramData\Identity Finder\LiveMode folder
Each user task uses the database in the LiveMode folder in the users profile folder. A file called “lastsearchresults” (no extension) may also be seen in this folder. It contains the results from the previous search that will be displayed on the next interactive client startup. It has nothing to do with rescan to determine if the files still exist.
You could delete the livemode db file to have it start over on the next search if you wish.