Intel (R) CSME SW Instalacion
Intel (R) CSME SW Instalacion
March 2024
Revision 1.5
Intel Confidential
1 Introduction
This guide describes overview of, how to install, configure and troubleshoot the Intel®
Converged Security and Management Engine (Intel® CSME) software components.
This guide provides comprehensive information about various systems, including both
existing sustaining platforms and new platforms that have not yet undergone
Production Validation (PV).
§§
2 Software Components
Overview
This section lists the software components supplied with the Intel® CSME software kit
and provides a short overview of each component.
It also provides Intel® CSME with various host operation abilities. For instance, it
enables Intel® CSME technologies to write user notifications to the local host OS event
log for the purpose of notifying end users of predefined events, such as when support
personnel connect remotely to the platform for a healing session. Intel provides
documentation on how ISVs can extract these events from the event log for use in
their applications.
After Windows* 10 RS3 or later with Intel® MEI driver 2124.100.0.1096 or newer,
Intel® SOL LMS Extension is required along with Intel® LMS. Intel® LMS will be
functional only if Intel® SOL device exists and Intel® SOL LMS extension INF is
installed.
The provider has switched to INF installation support. Refer to section 5 for more
detail of installing method.
When the application is running on the platform, an icon is displayed in the notification
area. Clicking the icon opens the application.
By default, the icon is loaded and displayed every time Windows* starts. The icon will
be gray if Intel® LMS is not running or Intel® MEI driver is disabled or unavailable.
Note: If the application starts automatically because of the user logging on to Windows*, the
icon will be loaded to the notification area only if Intel® AMT, Intel® SBA or Intel® Standard
Manageability exists on the system. If the application starts manually (via the Start menu or
file manager), the icon is loaded even if none of these technologies exists.
Note: The information displayed in the application is refreshed at pre-defined intervals. The
application dynamically hides tabs that are not relevant. For example, on platforms that do
not support Intel® AT, the Intel® AT tab is hidden.
Wiman is only present and functional on Corporate sku FW image for Coffee Lake
platform and above.
The main usage is for ISSE FW measurement attestation via SPDM protocol and for
Trusted Domain eXtension (TDX) attestation.
The driver itself is just a pipe between Host App (Host Client) and FW App (FW Client),
the driver does not aware or care about the payload between the clients.
The library is the recommended way to communicate between Host and FW. The
library is cross-platform and shall provide C API. (for User-space and Kernel)
Note: ISSEI software differs from CSME software, but it is included in the CSME software kit
for OEM convenience.
§§
3 Installer List
This section describes the installation packages for the Intel® CSME software.
3.1 Legacy
The installation program in this folder installs the Intel® CSME software components
required for the platform on which you are installing, and installs only those
components that match your platform’s capabilities.
Note: This installer only supports for sustaining platforms including Intel ® Coffee Lake and
older platforms on Windows* 10.
The following table describes the components that are installed for the different
platform capabilities:
If the platform includes this These software components are installed
capability.…
Intel® AMT, Intel® SBA, Intel® Intel® MEI driver, SOL driver, Intel® TCS,
Standard Manageability Intel® LMS, Intel® CSME WMI provider,
Wiman(1) driver, Intel® DAL(2)
Intel® Dynamic Application Intel® MEI driver, Intel® DAL(2)
Loader
None of the above Intel® MEI driver, Intel® TCS, Intel® CSME
WMI provider
1. Wiman is only installed and functional on corporate sku FW image for Coffee Lake
platform and above.
2. The Installer provides the option to install only Intel ® MEI driver and Intel® DAL
service by running the installer with the following flag: setup.exe –meidalonly.
3.2 Main_DCH
The installation program in this folder installs the Intel® CSME software components
which are compliant with Microsoft DC requirement. The installation program installs
only those components that match your platform’s capabilities.
Note:
1. Intel® MSS application is not installed by this installer. For installation of Intel®
MSS refer to section 5.1.3.
2. Intel® Silicon Security Engine Interface (ISSEI) is not installed by this installer, for
installation of ISSEI refer to section 3.3
Following is a complete list of the components in the installer. The drivers that get
installed are determined by the platform's capabilities and the specific platform SKU.
• Intel® Management Engine Interface (Intel® MEI) driver
• Serial Over LAN (SOL) driver
• Intel® Local Manageability Service (Intel® LMS)
• Intel® CSME WMI provider
• Intel® Dynamic Application Loader (Intel® DAL)
• Intel® Trusted Connect Service (Intel® TCS)
• Intel® Wireless Manageability (Wiman) driver
The following table describes the components that are installed for the different
platform capabilities:
If the platform includes this These software components are installed
capability.…
Intel® AMT, Intel® SBA, Intel® Intel® MEI driver, SOL driver, Intel® TCS(1),
Standard Manageability Intel® LMS, Intel® CSME WMI provider,
Wiman(2) driver, Intel® DAL(3)
Intel® Dynamic Application Intel® MEI driver, Intel® DAL(3)
Loader
None of the above Intel® MEI driver, Intel® TCS(1), Intel®
CSME WMI provider
1. Depending on platform type, Intel® TCS may be not installed by Intel® CSME SW
installer. Detail refers to TA#734356.
2. Wiman is only installed and functional on corporate sku FW image for Coffee Lake
platform and above.
3. The Installer provides the option to install only Intel ® MEI driver and Intel® DAL
service by running the installer with the following flag: setup.exe –meidalonly.
Note that Intel® DAL is deprecated after Meteor Lake platform running ME18.
3.3 Drivers
This package includes the INF installers for Intel® CSME software components and
Intel® MSS APPX package.
Note: The driver INF in the SW kit for pre-PV platforms are Microsoft pre-production signed
drivers. The prerequisites and provisioning Steps for systems that require enabling Secure
Boot can be found at the following link: https://learn.microsoft.com/en-us/windows-
hardware/drivers/install/preproduction-driver-signing-and-install
4 System Requirements
To enable installation and use of the Intel® CSME software components, the following
are required on the platform:
• Windows* 10 / Windows* 11 / Windows Server* 2016 64 bit versions / Windows
Server* 2019.
• Microsoft* .NET Framework: version 4.8 or above.
• Microsoft* Visual C++ 2015 Redistributable: released with Intel® MSS APPX and
required for Intel® MSS application.
The installer has command line options for specific installing configuration, under
command line mode execute setupME.exe -? Will display the available options as
follows:
-?
Displays this help dialog.
-b
Reboots the system without prompting after setup is complete, if reboot is
required.
-l <LCID>
Specifies the language of the setup dialogs.
-nodrv
Does not install the driver.
Note: with this parameter, the installer will install Intel® MSS anyway. If Intel® MSS is not
required, add –noimss to skip it.
-overwrite
Ignores the overwrite warning.
-p <path>
Changes default directory location for application files.
Warning: User who chooses to use –p flag must make sure the destination directory is a secure
folder (write access by admin). Otherwise, it can lead to a security issue.
-report <path>
Changes the default log path.
-s
Does not display any setup dialogs (silent install).
-ver
Displays driver versions.
-drvonly
Installs drivers only.
-noIMSS
Does not install Intel® MSS.
-meidalonly
Installs Intel® Management Engine Interface, Intel® Dynamic Application Loader
only.
-preinst
Installs all drivers even if hardware is not present.
-tcs
Installs only Intel® TCS.
-skipstartmenu
Does not add the Intel® MSS shortcut to the Start menu
-nowiman
Does not install Wireless Manageability
-wmionly
Install and register only Intel® CSME WMI Provider.
The installation logs can be found at <user folder>\Intel\Logs.
Users or system manufacturers should follow the list in section 3.3 to install required
software components.
System manufacturers can do offline injection via DISM. More information about DISM
can be found at:
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-
dism
Note: Intel® MEI driver and SOL driver are recommended to be installed before other
drivers/components.
Wiman Extension is required along with Wiman driver. Wiman will be functional only if
Wiman extension INF is installed.
SOL LMS Extension is required along with SOL device and Intel® LMS. Intel® LMS will
be functional only if SOL device exists and SOL LMS extension INF is installed.
The following devices will be shown in the device manager if the according
components are installed on compatible devices:
Note: The MEI driver INF in Drivers\MEI\win10 is singed for Windows* 10 RS5 and later,
while the MEI driver INF in Drivers\MEI\win8 is signed for windows* 8.1 and later. Refer to
DOC#618680 in RDC for more detail.
Intel® CSME WMI Provider: Software components \ Intel(R) Management Engine WMI
Provider
Intel® Silicon Security Engine Interface (ISSEI): Security devices\ Intel(R) Silicon
Security Engine Interface
User may use installer SetupME.exe in the Main_DCH folder to facilitate the
installation:
1. Double-click the installer to install the software components.
2. Follow the steps in the installation wizard to complete the installation.
3. When the installation is complete, click Next in the Setup Progress window, then
click Finish in the Setup is Complete window.
Note: The installer SetupME.exe may not be forward compatible with update of Windows*
OS and may fail due to new update of Windows patches. Consult Intel for more detail and
issues.
The installer SetupME.exe has command line options for specific installing
configuration, under command line mode execute setupME.exe -? will display the
available options as follows:
-?
Displays this help dialog.
-b
Reboots the system without prompting after setup is complete, if reboot is
required.
-l <LCID>
Specifies the language of the setup dialogs.
-nodrv
Does not install the driver.
-overwrite
Ignores the overwrite warning.
-p <path>
Changes default directory location for application files.
Warning: User who chooses to use –p flag must make sure the destination directory is a secure
folder (write access by admin). Otherwise, it can lead to a security issue.
-report <path>
Changes the default log path.
-s
Does not display any setup dialogs (silent install).
-ver
Displays driver versions.
-drvonly
Installs drivers only.
-meidalonly
Installs Intel® Management Engine Interface and Intel® Dynamic Application
Loader only.
-preinst
Installs all drivers even if hardware is not present.
-tcs
Installs only Intel® TCS.
-nowiman
Does not install Intel® Wireless Manageability
-wmionly
Install and register only Intel® CSME WMI Provider.
To get the debug log for the installer, users can execute the installation using the
command line with the parameter "-report <path>". The debug logs can be found at
<user folder>\Intel\Logs.
Note: Intel® MSS is for Intel® AMT systems only, it is not required to be installed on NON-
Intel® AMT systems.
User may download and install Intel® MSS from Microsoft* store, or install
IMSS_HSA_EXTENSION INF, which will pull Intel® MSS from Microsoft* store and
install Intel® MSS in the background when SOL device and internet connection exist.
Intel® MSS APPX installation package is for pre-install, and the installation package is
in the Drivers\IMSS folder.
For pre-PV platforms, there may be a test version of IMSS installation package which
has postfix _Test added in the folder name and the folder structure looks like:
2. Execute PrivacyIconClientPackagingProject_xxx.cer
3. Run install.ps1 with power shell. During execution, The following window will be
pop up. Turn on developer mode, and continue with power shell by choosing
[Y]Yes.
For MSFT* signed version of Intel® MSS installation package, the folder structure
looks like:
System manufacturers may use DISM to install MSFT signed version of Intel® MSS
APPX. Refer to https://docs.microsoft.com/en-us/windows-
hardware/manufacture/desktop/preinstall-apps-using-dism for more detail.
Microsoft Visual C++ 2015 Redistributable is released with Intel® MSS APPX and may
be installed with Intel® MSS APPX using DISM.
where c:\test\offline is the folder where you mounted the WIM image
<pre-install kit Folder Path> is the folder where the package is extracted to
1603 ERROR_INSTALL_FAILURE General failure code. The error could have been an
unanticipated error or one of the expected errors
such as:
• Not admin
• No device matches
• OS requirement not met
• .NET requirement not met
Note: The installer may return other error codes in cases where an application or other
process called returns one. The error code returned will be passed through.
5.3 Windows* PE
The Intel® MEI driver can be installed on Windows* PE OS, and this is primarily used
during manufacturing, when attempting to run Windows*-based manufacturing line
tools.
When running the Intel® MEI driver on Windows* PE 3 (based on Windows* 7), it is
necessary to ensure that the KMDF 1.11 coinstallers are added to the Windows* PE
image build, using the DISM command.
Each Intel® CSME Software Installer package contains a file called the ‘mup.xml’
which can be used to identify the SPV. The mup.xml describes the following
information: Example:
<fullpackageidentifier>
<msis>
<msi componentID="100950">
<identifyingnumber>{1CEAC85D-2590-4760-800F-
8DE5E91F3700}</identifyingnumber>
<upgradecode>{1CEAC85D-2590-4760-800F-8DE5E91F3700}</upgradecode>
<version> YYWW.BR.BUILD.PFU</version>
</msi>
</msis>
</fullpackageidentifier>
The ‘fullpackageidentifier’ section points out where to look for the package version and
what it should be in order to be the latest. The ‘DisplayVersion’ and {GUID} above are
found Microsoft* Windows* registry in the locations below:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GU
ID}\DisplayVersion
Service name for Intel® LMS, Intel® DAL or Intel® TCS can be found in Services tab in
task manager or services in Microsoft Management Console:
Intel® LMS: LMS / Intel(R) Management and Security Application Local Management
Service
Intel® DAL: jhi_service / Intel(R) Dynamic Application Loader Host Interface Service
If Intel® LMS, Intel® DAL or Intel® TCS are installed via installer SetupME.exe in
Legacy folder, the components file location is
7 Advanced Configuration of
Intel® Management and
Security Status Application
Note: This section is only for legacy MSS and not applicable for Intel® MSS APPX. Refer to
Intel® MSS user guide for Intel® MSS APPX.
To change the logo, add a bitmap file called oemlogo.bmp to the Intel® Management
and Security Status application folder (located at Program Files\ Intel\ Intel®
Management Engine Components\IMSS, or at Program Files (x86)\ Intel\
Intel® Management Engine Components\IMSS for 64-bit operating systems). The
default logo will appear if the bitmap file is invalid or missing.
Note: The bitmap dimensions should be 62 (width) by 48 (height) and size of file no larger
than 8 KB. If the image file shall exceed 8 KB, the logo may not be well visible. If the bitmap
dimensions are smaller than 62x48, the logo image will be centered into its designated area.
To disable application load on startup for all users, add a value named
AppAutoStartDefaultVal with value 0 to the following registry location
HKLM\SOFTWARE\Intel\PIcon\Setting.
To return to the default behavior, change the data of the same value to 1, or delete
the value.
Note: The application will still be available from the Start Menu, regardless of the value in
this registry key.
Note: The user selection overrides system values in the registry key.
To return to the default behavior, change the data of the same value to 0, or delete
the value.
Note: The application will still be available from the Start Menu, regardless of the value in
this registry key.
Note: The user selection overrides system values in the registry key. Meaning that in case
the user will uncheck the Intel® Management and Security Status will be available next time I
log on to Windows check box the application will not load in ”disabled state”.
To return to the default behavior, change the data of the same value to 1, or delete
the value. The user selection overrides system values in the registry key.
The link pointed to by the “Click here for more details” text inside the Learn more
dialog can be modified to link to a page of the manufacturer's choice.
To perform this change, add a value named HelpURL with the URL of your choice
(e.g. http://www.intel.com/) to the HKLM\SOFTWARE\Intel\PIcon\Setting key in
the registry. To return to the default behavior, delete the value.
LMS.exe is installed along with the other software components. Note the following
installation circumstances:
Note: The following keys are not mandatory and Intel® LMS will function as required without
their existence. All changes to registry keys are noted at Intel® LMS startup only. To force the
changes to be noted, restart Intel® LMS.
Note: Partial Firmware Update is a feature new from Intel® ME 8 that allows update of
specific sections of Intel ME, without requiring a system reset.
Note: Disabling Partial FW Update will eliminate the user's ability to change the user consent
language and to replace the wireless adapter type without affecting Intel ® AMT functionality
over wireless LAN.
Note: The path can't point to a network shared folder. It must point to a local folder.
The following Registry keys could be added for configuring which events will be shown
in Event Log. This is a DWORD Value. Setting value to 0 will prevent the event from
appearing, while setting value to 1 will cause the relevant event to appear. Note that
the settings only take effect when Intel® LMS is (re)started.
Users wishing to override the default setting in Intel® CSME firmware may add the
following registry key under:
HKEY_LOCAL_MACHINE\SOFTWARE\Intel\IntelAMTUNS
If you are installing the inf drivers manually – from the Drivers folder, you should
uninstall them manually:
• Right click the device name in device manger and choose uninstall
• Or use pnputil command to uninstall
Note: If some system dlls have been removed between the installation and uninstallation of
the Intel® CSME software, the uninstallation may fail. This has been noted, for example,
when uninstalling Microsoft* Visual C.
Note: Do not manually uninstall Intel® CSME software components via device manager if you
installed them using installer SetupME.exe.
There are 3 different Wiman’s (WiMan-WiFi for Canon Lake/Coffee Lake/Whisky Lake,
WiManH for Comet Lake/Tiger Lake, WiManHu for Alder Lake and above). When user
uses the NIC that is relevant for Canon Lake/Coffee Lake/Whisky Lake on upper
platform version he will get the WiMan-WiFi as hidden device in device manager, and
the WiMan-WiFi will be as a “zombie”.
If users installing SOL LMS extension INF want to downgrade Intel® CSME software,
the existing Intel® CSME software including SOL LMS extension INF should be
removed firstly.
SOL and Intel® LMS device must be removed before SOL LMS extension INF is
uninstalled.
10 Troubleshooting
The Intel® Management and Security Status application will display unspecific error
message if no appropriate Microsoft* .NETframework in the system, e.g.
If these kinds of issues happen, check the installed Microsoft* .NET Framework. The
required version refers to section 4.
If the actions above do not resolve the problem, it is recommended to contact your
Information Technology department.
While the Intel® MSS application is running, the Intel® MSS icon is visible in the
notification area. This icon will appear blue if any one of the aforementioned
technologies is enabled on the computer. In any other case, the icon will appear gray.
Note: The icon will also be gray if Intel® LMS service is not running or the Intel® MEI driver
is disabled or unavailable.
legacy OEM extension INF has been installed (and not removed), user will see
redundant software components in device manager after Intel® MEI driver is
installed/updated with version 1931.14.0.1323 or later.
This symptom doesn’t impact the functionality of Intel® TCS, Intel® DAL and Intel®
LMS. If user still wants to remove these duplicate components from device manager,
user may remove oemextension INF via pnputil command.