search cancel

After Upgrade to GSS 3.3 RU4, bcedit.exe is missing at Bootwiz's Installer folder and newly created Automation folder cannot be deployed properly


Article ID: 198551


Updated On:


Ghost Solution Suite


After upgrading to GSS 3.3 RU4, bcdedit.exe and BootSect.exe are missing under the following folders:
C:\Program Files (x86)\Altiris\eXpress\Deployment Server\Bootwiz\platforms\Windows\x64\Installer
C:\Program Files (x86)\Altiris\eXpress\Deployment Server\Bootwiz\platforms\Windows\x86\Installer

When a new Automation Folder installer is generated it includes Installer folder content to its package, however when the mentioned files are missing, Automation Folder cannot be deployed properly.

It exits with error ERROR_FILE_NOT_FOUND 
FileOperation (sSrc='C:\Windows\TEMP\apt0\bcdedit.exe', 
sDst='C:\boot\altiris\iso\bcdedit.exe', wAction=2, fFlags=0614) returning 2 (success = 0)

OR in the log file for the automation folder install:

2020/08/09 16:31:39 autoinst(2070) I: -IniEntrysCopy - Copy 'C:\Windows\TEMP\apt0\bcdedit.exe' to 'C:\boot\altiris\iso\bcdedit.exe'
2020/08/09 16:31:39 autoinst(2070) D: FileOperation (sSrc='C:\Windows\TEMP\apt0\bcdedit.exe', sDst='C:\boot\altiris\iso\bcdedit.exe', wAction=2, fFlags=0614) returning 2 (success = 0)
2020/08/09 16:31:39 autoinst(2070) D: FileCopy (sSrc='C:\Windows\TEMP\apt0\bcdedit.exe' -> sDst='C:\boot\altiris\iso\bcdedit.exe') returning 117 (success = 0)
2020/08/09 16:31:39 autoinst(2070) I: IniEntrysCopy - Could not copy 'C:\Windows\TEMP\apt0\bcdedit.exe' to 'C:\boot\altiris\iso\bcdedit.exe' - error 117
2020/08/09 16:31:39 autoinst(2070) I: End CClient::IniEntrysCopy - returning 117
2020/08/09 16:31:39 autoinst(2070) I: End CClientBootMgr::Install - returning 117 (success = 0)

When trying to boot to Windows automation you get and error "Unable to boot to windows automation error 116". If you open "BCDEDIT", it does not show the "c:\boot" as an option, only the Windows Boot Manager.

Not reproducible after a clean install of GSS 3.3 RU4.


Known Issue.


GSS 3.3 RU4


This issue has been reported to Symantec Development team. A fix for this issue has been included to our next release (GSS 3.3 RU5).

Copy mentioned files to corresponding folders at GSS server manually and recreate Automation Folder package:

1 - Create dummy bcdedit.exe (create new .txt and rename it to .exe)
2- Create dummy BootSect.exe (create new .txt and rename it to .exe)
3- Copy both files to the following locations on GSS server:

  • C:\Program Files (x86)\Altiris\eXpress\Deployment Server\Bootwiz\platforms\Windows\x64\Installer\
  • C:\Program Files (x86)\Altiris\eXpress\Deployment Server\Bootwiz\platforms\Windows\x86\Installer\

4- Reinstall "automation folder" using newly generated automation folder packages.

  • to reinstall automation folder on affected clients, you need to uninstall existing not working "automation folder" and then install new
  • if you want to install automation folder from menu Advanced > 'Install Automation Folder...', make sure that you removed "bad" automation folder created during previous installs from C:\Program Files (x86)\Altiris\eXpress\Deployment Server\AutoFolderPkgs before reinstalling automation folder.
  • if you want to install "automation folder" manually using created EXE package you need to create new automation folder package via Boot Disk Creator tool.