IssueDescriptionWorkaround
1E OEM Toolkit Wizard and installer log file may not be launched after installation.

In Windows Server 2019 when installation was initiated by the Built-in Domain Administrator and "Launch 1E OEM Toolkit Wizard" and "Show the Windows Install log" options were selected after installation then 1E OEM Toolkit Wizard and installer log file may not be launched. However, it works with other admin users.


To open 1E OEM Toolkit Wizard, launch Create1EOEMToolkitPackage.exe from the BIOSTOUEFI installation directory. To generate the log file, initiate the installation from elevated command prompt using /l*v properties. For example:

msiexec /i <installer.msi> /l*v <filename.log>

Do not use /q options because unattended installation is not supported.

Error is encountered during the extraction of downloaded Hardware of HP.

In the "Create1EOEMToolkitPackage" wizard, when user proceeds to download hardware tools of HP then below error occurs during extraction of tools.

Before running the Create 1E OEM Toolkit Package Wizard, download and extract the HP BCU as detailed in Manually downloading vendor tools. Then run the wizard and select the option "I've already downloaded the vendor tools to another directory" then specify the path to the extracted HP files.
A pop-up window for Site Code Selection is displayed when there are multiple SMS providers and a previously downloaded tools executable is used.If there are multiple SMS Providers and a previously downloaded OEM Vendor toolkit is selected in the Create 1E OEM Toolkit Package wizard, when the user proceeds a pop-up window for Site Code Selection is displayed.
An exception is displayed when user proceed with Locate Tools without providing any path on the wizard.When the user opts to use previously downloaded OEM Vendor tools and click Next button on Wizard without providing path and exception is displayed.
Error Unable to Extract tools is displayed when the download of OEM Vendor tools is in progress and network connection breaks.During the download of OEM Vendor Tools if network connection disrupts message is displayed on wizard as "Unable to Extract tools locally".
Grey bar is displayed next to listed SMS providers on OEM toolkit Wizard.If there are multiple SMS Providers and when the user proceeds with "Create1EOEMToolkitPackage" creation wizard, Grey bar is displayed next to listed SMS providers on OEM toolkit Wizard.
User cannot maximize the Wizard window.Create1EOEMToolkitPackage" creation wizard is not allowed to maximize the wizard however the user can resize the window.
Listed Distribution Point Groups are editable.When the user proceeds with "Create1EOEMToolkitPackage" creation wizard, on Distribution Point Group selection window its observed user can edit the listed group.
User proceed further on Wizard even when no hardware vendor is selected.If a user does not select any Vendor tool to download its observed that user can proceed with "Create1EOEMToolkitPackage" creation wizard.
After tools are downloaded and extracted error message is displayed.Message "A New Version of the console is available. cmdlets may not function as expected......" is displayed after tools are downloaded and extracted.
Installer log not displayed.The installer log is not displayed at the end of the installation.
Create 1E OEM toolkit package wizard fail to launch after installation.The toolkit is not launched at the end of the installation due to permission issues. The workaround is to run it from its installation folder.
1E OEM toolkit package creates new package for same source folder.It creates a new 1E OEM toolkit package even though the same source folder for the previous package was specified in the wizard.
Error when editing OSD task sequence with BIOS to UEFI steps in Configuration Manager 1610.

An error message similar to the following is displayed with "Failed to load class properties and qualifiers for class ONEE_BIOS2UEFI_PWD in task sequence."

If this error occurs, uninstall and reinstall BIOS to UEFI again.

TPM chip cannot be enabled/activated on some Lenovo machines such as the ThinkCenter M700, if the TPM chip is disabled.

This is a design limitation on some Lenovo systems (ThinkCentre series). If the chip is disabled, it can't be programmatically enabled. You must manually enable the chip.
On Dell machines, where no boot list item is present in the UEFI boot sequence, setting Boot Order to Windows Boot Manager/Hard disk fails.After switching to UEFI and partitioning the disk to a GUID Partition Table (GPT), if the Change Boot Order feature is used without a restart step in between, the task sequence step fails with error 20 – the system cannot find the device specified error. Please refer to changing the BIOS boot order.

Lenovo ThinkPad L450 (or machines with similar firmware): If the admin password is set, and in 1E BIOS to UEFI Password step it is set to be removed - Password is removed, but no other UEFI settings get set in BIOS and the system gets locked.

This is a limitation in Lenovo ThinkPad L450 and similar firmware machines, wherein if an admin password is already set and asked to be removed in '1E BIOS to UEFI Password Step', the password gets removed in BIOS. But, no setting can be set programmatically until the password is made saved to blank again manually in BIOS. It is recommended not to remove passwords if they are already set.
On Dell machines, TPM chip cannot be activated when it is pre-owned by an operating system, but is in disabled/inactive state.This is an intermittent issue. Even if the TPM activation fails, the task sequence step doesn't return an error, so that the task sequence continues to execute. Allow the TS to complete. Once the TS completes and the OS is installed on the system, TPM chip can be cleared and activated in BIOS manually.
Installer fails to run if you do not have local admin rights.

The account running the installer requires must have local admin rights. There may be instances where the installer returns an error prompting for admin rights when you double-click to run it even though you are logged in as a local admin.

When this happens, start a command prompt as administrator and run:

msiexec /I 1EBiosToUefi.msi
Installer fails on x86 machines.The BIOS2EFI installer will not run on x86 machine. The only component that can run on an x86 machine is the Configuration Manager Console. 

If the Console extensions are required on an x86 machine, then manually copy OneE_CustomControlTemplate.dll to the Console Install Directory\BIN folder on the target x86 machine.

Obtain the OneE_CustomControlTemplate.dll file using one of the following methods:

  • copy from a x64 device
  • copy the file from an admin installation, after running  msiexec /a 1EBiosToUefi.msi
Task sequence action fails to set UEFI CSM on Lenovo.Lenovo does not support configuring UEFI with Compatibility Support Module (CSM).
1E BIOS to UEFI Task Sequence action fails to terminate.1E BIOS to UEFI OEM does not return failure when UEFI CSM option fails. The Task Sequence will continue to execute despite the failure.
Create OEM Toolkit Package wizard fails to allow user to move back.The Create OEM Toolkit Package does not include a back button. If changes to previous screens are required, you must cancel the wizard and start again.
Create OEM Toolkit Package wizard error.The Create OEM Toolkit Package wizard displays status on the wizard screen for diagnostic purposes. Any errors will be displayed in the final screen (use the scroll bar to scroll up and view).
Create OEM Package wizard exception.OEM Package wizard installer throws exception if the Path to Dell Tools field on the Locate Dell Tools screen is blank and the user clicks Next.
Unattended installation not supported by Create OEM Toolkit Package wizard.The Create OEM Toolkit Package wizard does not support unattended execution.
Unable to change boot order sequence.This is a UI issue.To change the boot order options, you need to uncheck and recheck the Change Boot Order option.