The following error is reported to the console:
00000067 Failed to install SAVXP: A reboot was required.
First seen in
Sophos Anti-Virus for Windows 2000+
- This is triggered on a new installation of Sophos Endpoint Security and Control 10.6.0 when an existing pending reboot requirement is present.
- The local file '
C:\Windows\Temp\Sophos Anti-Virus Major Install Log.txt' will contain the following error:
ERROR: A system reboot is pending - unable to upgrade
- The endpoint computer has not been rebooted since the last major update.
- The flag file
C:\Windows\Temp\SophosNoUpgrade.txt is present on the endpoint computer and preventing the upgrade of the endpoint software.
What To Do
Reboot the endpoint computer to ensure that the previous installation/upgrade can be completed.
- On new installations of 10.6.0 Sophos checks for and installs Microsoft runtime software if not already present. A pre-requisite of runtime installations is the lack of any existing pending reboot requirements. If there is a requirements the computer will need rebooting to allow the installation to proceed.
- The file
SophosNoUpgrade.txt is a flag file which is created when a computer upgrades from one version of the Sophos Anti-Virus (SAV) version to another.
The file is created so the installer can determine whether or not a full reboot has occurred. After a reboot the file is automatically removed.
If this file is present it will stop the computer from upgrading again until the file is deleted (i.e., the computer has been rebooted) and to prevent multiple version jumps of SAV without a full reboot. If several major version where to be installed without a reboot there may be complications for new drivers, services and other important files.