How can I fix the Fast Incremental Tracking error after every reboot

This guide explains how to create and deploy a script that automatically resolves the fast incremental tracking error caused by Sentinel One after a system reboot.

Servosity provides this guide as a reference. It is your responsibility to test the script in your environment to ensure it performs as expected and does not interfere with other system operations.

Steps to Fix the Error

If you are seeing the Fast Incremental Tracking Error on your system after installing Sentinel One or after a reboot with Sentinel One installed, you can fix it by running the following command in an administrative command prompt:

fltmc attach stcvsm c:

This will reattach the storage driver to the C volume and allow ShadowProtect backups to run again.

Steps to Automate the Fix

Create the Script
Use a text editor (e.g., Notepad) to create a script that runs the fix command.
Example script (for Windows systems):

@echo off
:: This script will run the command "fltmc attach stcvsm c:" on startup
:: It creates a new log file for each execution in the specified log folder

:: Define the log folder path
set LOGFOLDER="C:\Program Files\Servosity One\logs"

:: Create the log folder if it does not exist
if not exist %LOGFOLDER% (
mkdir %LOGFOLDER%
)

:: Get the current date and time for the log file name
setlocal enabledelayedexpansion
set TIMESTAMP=%DATE:~10,4%-%DATE:~4,2%-%DATE:~7,2%_%TIME:~0,2%-%TIME:~3,2%-%TIME:~6,2%
set TIMESTAMP=!TIMESTAMP: =0!

:: Define the log file path with timestamp
set LOGFILE=%LOGFOLDER%\attach_stcvsm_%TIMESTAMP%.log

:: Start logging
echo Starting fltmc attach stcvsm c: command execution... > %LOGFILE%
echo Log Date and Time: %DATE% %TIME% >> %LOGFILE%
echo ------------------------------------------------ >> %LOGFILE%

:: Run the command and log the output
fltmc attach stcvsm c: >> %LOGFILE% 2>&1

:: Check the error level to determine if the command was successful
if %ERRORLEVEL% neq 0 (
echo ERROR: fltmc attach stcvsm c: failed with error code %ERRORLEVEL% >> %LOGFILE%
) else (
echo SUCCESS: fltmc attach stcvsm c: executed successfully. >> %LOGFILE%
)

:: Optional: Display the log file path
echo Log file created at: %LOGFILE%

Save the file as attach_stcvsm.bat.
Set the Script to Run on Reboot
Use Task Scheduler to execute the script whenever the system reboots:
- Open Task Scheduler.
- Click Create Task on the right panel.
- Under the General tab, name the task (e.g., “Fix S1 Issue on Reboot”).
- In the Triggers tab, create a new trigger:
  - Set it to run At startup or On reboot.
- In the Actions tab, set the script to run:
  - Select Start a Program and browse to attach_stcvsm.bat.
- Save the task.
Test the Script
Run the attach_stcvsm.bat script from an administrative command prompt to confirm it is working. You can check the log to verify that the command was run. If the command has already been run manually since reboot you will probably see a log file that looks similar to this example:

Starting fltmc attach stcvsm c: command execution...
Log Date and Time: Tue 01/28/2025 15:21:04.56
------------------------------------------------

Attach failed with error: 0x801f0012
An instance already exists with this name on the volume specified.
ERROR: fltmc attach stcvsm c: failed with error code 1

This should be considered a success, as it means the command did run.
Monitor for Issues
Ensure backups are working correctly after future reboots. If problems persist, manually run the fix command and contact Servosity Support so we can check the logs for issues.