Installation or a Scripted install returns Error 3010 in Deployment Server, Patch Management, or Software Delivery
Last Updated July 16, 2019
An installation or a Scripted install returns Error 3010 in Deployment Server, Patch Management, or Software Delivery.
Deployment server error codes are based on the component (in this case the msi install script) sending back the return code. In this case the scripted install returns an error 3010 is based the Microsoft Error codes.
As an example: an install of service pack 3 with no problem using the -q -z -o switches. It completes with no problem. However when using using /q:a /r:n with an installation of any update the installation completes but returns the error code 3010.
Common Command-Line Switches for Self-Installing Update Files (Software may not support all switches listed here):
Specifies quiet mode, or suppresses prompts, when files are being extracted.
Specifies user-quiet mode, which presents some dialog boxes to the user.
Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
Never restarts the computer after installation.
Prompts the user to restart the computer if a restart is required, except when used with /q:a.
Always restarts the computer after installation.
Restarts the computer after installation without prompting the user.
Common Switches for Service packs:
Force other programs to quit at shutdown
Quiet mode (no user interaction required)
Unattended Setup mode
Do not restart the computer after installation
What does error 3010 mean?
The requested operation is successful. Changes will not be effective until the system is rebooted.
This isn’t really an error but is just a code stating that the operation completely successfully and requires a reboot to become effective.
What Switch is causing the problem?
The problematic switches in many of the scripted install process are:/q, /q:a, /z, /r:n.
These switches either suppress the prompt that tells the user that they need to reboot the computer for the install to finish or force the install without a reboot.
When deploying these types of Scripted installs from either Deployment Server or Notification Server the solution would be these options:
Force a reboot after the install to finish the installation process within the script use the /f or the /r:a switches.
This is not merely a suggestion but a requirement in software delivery as far as Altiris Technical Support is concerned.
Two options in dealing with this error:
Remove the /q:a or /q from the command line used. This will stop the occurrence of the 3010 error and then force the reboot of the client machine.
Use Error handling within your scripts to work through that error. If with Software Management, add 3010 and 0 to the success codes in order to properly report a success
Here is a script example:
REM Installing Hotfix MS03-026 \\ServerName\express\server\common\packages\hotfix\q823980\q823980w2k.exe /u /z /q if ERRORLEVEL 3010 goto success if ERRORLEVEL 0 goto success goto failure :success set %ERRORLEVEL% = 0 goto end :failure echo Failed EXIT 1 #goto end :end
Imported Document ID: TECH12314
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe