Error: "ImportWinPE: Win PE version WinPE11 - x86 BCD install failed. Execution aborted. Error 1" when importing Windows ADK install of Windows 11
search cancel

Error: "ImportWinPE: Win PE version WinPE11 - x86 BCD install failed. Execution aborted. Error 1" when importing Windows ADK install of Windows 11

book

Article ID: 244276

calendar_today

Updated On:

Products

Client Management Suite Deployment Solution

Issue/Introduction

Importing Windows ADK for WinPE 11.0 stays on importing:

Information and Errors in the log viewer:

  • Deployment Solution: Windows ADK WinPE11 path is:'C:\Program Files (x86)\Windows Kits\10'.
  • ImportWinPE: Win PE version WinPE11 - x86 BCD install failed. Execution aborted. Error 1.
  • Deployment Solution: ImportWinPE failed.

BDCWinPE install failed.
   [System.InvalidOperationException @ Symantec.Deployment]
   at Altiris.Deployment.PrebootEnvironment.WinPeImportTask.ImportADK(String winPeToCreate)

  • Error executing task 'WinPE11 import task' (c9fe080d-c267-4920-b19c-66c04bb0a1a5).

  • Failure during task execution c9fe080d-c267-4920-b19c-66c04bb0a1a5.

    Task execution failed.
       [System.InvalidOperationException @ Symantec.Deployment]
       at Altiris.Deployment.PrebootEnvironment.PrebootImageCreationSchedule.ExecuteAndWait(Guid taskGuid)

Other similar log messages that you may see are:

Entry 1:
Deployment Solution : Windows ADK 11.0 is installed.
-----------------------------------------------------------------------------------------------------
Date: 9/15/2022 6:13:12 AM, Tick Count: 34832375 (09:40:32.3750000), Size: 327 B
Process: w3wp (5268), Thread ID: 274, Module: Symantec.Deployment.Common.dll
Priority: 4, Source: Altiris.Deployment.Common.WinPE11.IsWindowADKInstalled

 

Entry 2:
Deployment Solution: Check command parameter :: -install -q -os WinPE11 -x86 :: -install -q -os WinPE11 -x64 
-----------------------------------------------------------------------------------------------------
Date: 9/15/2022 6:13:12 AM, Tick Count: 34832437 (09:40:32.4370000), Size: 397 B
Process: w3wp (5268), Thread ID: 274, Module: Symantec.Deployment.Common.dll
Priority: 4, Source: Altiris.Deployment.Common.MultipleWinPE.CheckBDCWinPEInstallRunning

 

Entry 3:
Deployment Solution: Attempting WinPE:WinPE11 isBDCWinPEInstalled: false, isWindowADKInstalled: True, checkBDCWinPEInstallRunning: True
-----------------------------------------------------------------------------------------------------
Date: 9/15/2022 6:13:12 AM, Tick Count: 34832437 (09:40:32.4370000), Size: 357 B
Process: w3wp (5268), Thread ID: 274, Module: w3wp.exe
Priority: 8, Source: PrebootConfigPolicyPage

 

Entry 4:
ImportADK: Preboot environment version WinPE11 - x86 BCD install failed. Execution aborted. Error 553.
-----------------------------------------------------------------------------------------------------
Date: 9/15/2022 6:13:13 AM, Tick Count: 34833453 (09:40:33.4530000), Size: 381 B
Process: AeXSvc (1796), Thread ID: 151, Module: Symantec.Deployment.dll
Priority: 1, Source: Altiris.Deployment.PrebootEnvironment.WinPeImportTask.ImportAdk

 

Entry 5:
Deployment Solution: ImportADK failed.

BDCWinPE install failed.
   [System.InvalidOperationException @ Symantec.Deployment]
   at Altiris.Deployment.PrebootEnvironment.WinPeImportTask.ImportAdk(WinPE peToCreate, String peVersionToCreate, PrebootArcitecture& architecture)

Exception logged from: 
   at Altiris.Deployment.PrebootEnvironment.WinPeImportTask.ImportAdk(Altiris.Deployment.Common.MultipleWinPE+WinPE, String, Altiris.Deployment.PrebootConfiguration+PrebootArcitecture&)
   at Altiris.Deployment.PrebootEnvironment.WinPeImportTask.ImportWinPe()
   at Altiris.Deployment.PrebootEnvironment.WinPeImportTask.ExecuteTask(System.Collections.Hashtable, Altiris.NS.ItemTaskManagement.ItemTaskState)
   at Altiris.NS.TaskManagement.CoreTaskServiceThreadBase<T,TStartArgs>.ExecuteThreadProc(Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, Object)
   at System.Threading.ThreadHelper.ThreadStart(Object)

-----------------------------------------------------------------------------------------------------
Date: 9/15/2022 6:13:13 AM, Tick Count: 34833453 (09:40:33.4530000), Size: 1.59 KB
Process: AeXSvc (1796), Thread ID: 151, Module: Symantec.Deployment.dll
Priority: 1, Source: Altiris.Deployment.PrebootEnvironment.WinPeImportTask.ImportAdk

 

Entry 6:
Error executing task 'WinPE11 import task' (1e67ecd5-2152-419a-bcfa-954278ee488d).
-----------------------------------------------------------------------------------------------------
Date: 9/15/2022 6:13:13 AM, Tick Count: 34833453 (09:40:33.4530000), Size: 363 B
Process: AeXSvc (1796), Thread ID: 151, Module: Symantec.Deployment.dll
Priority: 1, Source: Altiris.Deployment.PrebootEnvironment.WinPeImportTask.ExecuteTask

 

Entry 7:
Operation completed: Executing core task ([00:00:01.4531721] 'WinPE11 import task' (1e67ecd5-2152-419a-bcfa-954278ee488d) (Altiris.Deployment.PrebootEnvironment.WinPeImportTask, id=[1e67ecd5-2152-419a-bcfa-954278ee488d], state=Completed, started=9/15/2022 6:13:12 AM, finished=9/15/2022 6:13:13 AM)), total time=00:00:01.4432032
-----------------------------------------------------------------------------------------------------
Date: 9/15/2022 6:13:13 AM, Tick Count: 34833468 (09:40:33.4680000), Size: 553 B
Process: AeXSvc (1796), Thread ID: 151, Module: AeXSVC.exe
Priority: 16, Source: CoreTaskServiceThread

 

Entry 8:
Failure during task execution 1e67ecd5-2152-419a-bcfa-954278ee488d.

Task execution failed.
   [System.InvalidOperationException @ Symantec.Deployment]
   at Altiris.Deployment.PrebootEnvironment.PrebootImageCreationSchedule.ExecuteAndWait(Guid taskGuid)

Exception logged from: 
   at Altiris.Deployment.PrebootEnvironment.PrebootImageCreationSchedule.ExecuteAndWait(System.Guid)
   at Altiris.Deployment.PrebootEnvironment.PrebootImageCreationSchedule.ExecuteWinPEImagingTask()
   at Altiris.Deployment.PrebootEnvironment.PrebootImageCreationSchedule.ExecuteWinPEImagingTasks()
   at Altiris.Deployment.PrebootEnvironment.PrebootImageCreationSchedule.OnSchedule(String)
   at Altiris.NS.Scheduling.ScheduleService.ProcessScheduleImpl(String, Altiris.Profiling.CodeProfiling.CodeProfiler, Altiris.NS.Security.SecurityContext, System.Guid)
   at Altiris.NS.Scheduling.ScheduleService+<>c_DisplayClass0_0.<ProcessSchedule>b_0(Altiris.NS.Security.SecurityContext)
   at Altiris.NS.Security.SecurityContext+<>c_DisplayClass46_0.<ExecuteAsOwner>b_1(Altiris.NS.Security.SecurityContext)
   at Altiris.NS.Security.SecurityContext.ExecuteAs<T,TK>(Altiris.NS.Security.EExecuteAs, TK, System.Func<TK,Altiris.NS.Security.SecurityContext>, System.Func<Altiris.NS.Security.SecurityContext,T>)
   at Altiris.NS.Scheduling.ScheduleService.ProcessSchedule(String)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr, Object[], Object, Object[]&)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage)
   at System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage)
   at System.Runtime.Remoting.Messaging.ServerContextTerminatorSink.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage)
   at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessageCallback(Object[])
   at System.Runtime.Remoting.Channels.ChannelServices.DispatchMessage(System.Runtime.Remoting.Channels.IServerChannelSinkStack, System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessage&)
   at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage(System.Runtime.Remoting.Channels.IServerChannelSinkStack, System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Channels.ITransportHeaders, System.IO.Stream, System.Runtime.Remoting.Messaging.IMessage&, System.Runtime.Remoting.Channels.ITransportHeaders&, System.IO.Stream&)
   at System.Runtime.Remoting.Channels.SoapServerFormatterSink.ProcessMessage(System.Runtime.Remoting.Channels.IServerChannelSinkStack, System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Channels.ITransportHeaders, System.IO.Stream, System.Runtime.Remoting.Messaging.IMessage&, System.Runtime.Remoting.Channels.ITransportHeaders&, System.IO.Stream&)
   at System.Runtime.Remoting.MetadataServices.SdlChannelSink.ProcessMessage(System.Runtime.Remoting.Channels.IServerChannelSinkStack, System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Channels.ITransportHeaders, System.IO.Stream, System.Runtime.Remoting.Messaging.IMessage&, System.Runtime.Remoting.Channels.ITransportHeaders&, System.IO.Stream&)
   at System.Runtime.Remoting.Channels.Tcp.TcpServerTransportSink.ServiceRequest(Object)
   at System.Runtime.Remoting.Channels.SocketHandler.ProcessRequestNow()
   at System.Runtime.Remoting.Channels.SocketHandler.BeginReadMessageCallback(IAsyncResult)
   at System.Net.LazyAsyncResult.Complete(IntPtr)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, Object)
   at System.Net.ContextAwareResult.Complete(IntPtr)
   at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object, IntPtr)
   at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

-----------------------------------------------------------------------------------------------------
Date: 9/15/2022 6:13:14 AM, Tick Count: 34834046 (09:40:34.0460000), Size: 4.59 KB
Process: AeXSvc (1796), Thread ID: 100, Module: Symantec.Deployment.dll
Priority: 1, Source: PrebootImageCreationSchedule

 

Entry 9:
WinPE build completed.
-----------------------------------------------------------------------------------------------------
Date: 9/15/2022 6:13:14 AM, Tick Count: 34834062 (09:40:34.0620000), Size: 253 B
Process: AeXSvc (1796), Thread ID: 100, Module: AeXSVC.exe
Priority: 4, Source: PrebootImageCreationSchedule

 

Entry 10:
Bootwiz log error
-----------------------------------------------------------------------------------------------------
CBootWizardApp::ExitInstance - Ending application instance
        Exit code: (20) 20 BDC_EXIT_INVALID_OS_TYPE - Invalid OS Type
***************************************************
        Application End
***************************************************

Environment

ITMS 8.x

DS 8.x

Cause

Windows 11 is not available in a 32-bit architecture, so the 32-bit version of Windows PE for Windows 11 is not supported; and Deployment solution looks for WindowsPE x86 which does not exist in the Windows kits folder.

Resolution

Support for the WinPE 11 is available in ITMS 8.6 RU1 and WINPE 11 22H2 is supported in ITMS 8.7 per the Deployment Solution OS Support Matrix and Client OS Support Matrix.

Workaround 1:

  • Copy the the prebootO.ini file from 'Program Files\Altiris\Deployment\BDC\bootwiz\' to another folder.
  • Right Click> Edit
  • Under '[WINPE11_X86]', change the INSTALLED=False to INSTALLED=True
  • Save.
  • Delete the main prebootO.ini file from 'Program Files\Altiris\Deployment\BDC\bootwiz\' and paste the new edited one there.
  • Try again the import WinPE11 process

Workaround 2:

  • Create a X86 folder with AMD64 content at the default ADK installation location:
  • C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment
  • (Clone the amd64 folder and re-name it to X86, or obtain the X86 folder from older ADK installation)
  • After that you can perform Import from console as normal

Additional Information

Powered by Wolken Software