PowerEdge: 14G, 15G, and 16G Chipset DUP WDAC not signed errors when changed from audit to enforced
Summary: The PowerEdge 15G and 16G Intel Lewisburg C62xx Chipset Dell Update package (DUP) version 10.1.19485.8386, for Windows operating system, released as part of the December 2023 release (factory and web posting) includes non-signed components from Intel for Windows Defender Application Control (WDAC). The PowerEdge R6515/R7515 AMD Milan Chipset DUP version 2.18.30.202 (October 2023) was also found to include non-signed components from AMD for WDAC. The PowerEdge 14G Intel platform Chipset DUP package version 10.1.18807.8279 (#K69PV) targeted for the upcoming March 2024 block has been found to have the same issue with WDAC (enforced mode) as it includes non-signed components from Intel. ...
Symptoms
The PowerEdge 15G and 16G Intel Lewisburg C62xx Chipset DUP package version 10.1.19485.8386 (#VGX10) for Windows operating system, released as part of the December 2023 block release (factory and web posting), includes non-signed components from Intel for Windows Defender Application Control (WDAC).
The R6515/R7515 AMD Milan chipset driver DUP package version 2.18.30.202 (#NJ9WJ) for Windows operating system that was part of the October 2023 block release (factory and web posting) includes non-signed components from AMD for Windows Defender Application Control (WDAC).
The PowerEdge 14G Intel Lewisburg C72xx Chipset DUP package version 10.1.18807.8279 (#K69PV) targeted for the upcoming March 2024 block includes non-signed components from Intel for the Windows Defender Application Control (WDAC).
WDAC is a new feature from Microsoft initially released in the chipset driver package in December. Full feature integration requires iDRAC updates which are not yet available.
WDAC is described in the Microsoft article: Understand Windows Defender Application Control (WDAC) policy rules and file rules - Windows Security | Microsoft Learn. The initial setting for WDAC is in Audit mode.
If a WDAC is changed from Audit mode to Enforced mode, when attempting to install the Intel chipset DUP package (version 10.1.19485.8386), the install will fail with the following errors:
Status : NotSigned StatusMessage : The file C:\Temp\intel15G\Bootstrapper.dll is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170Path : C:\Temp\intel15G\Bootstrapper.dll Status : NotSigned StatusMessage : The file C:\Temp\intel15G\Chipset.Bootstrapper.dll is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170
Path : C:\Temp\intel15G\Chipset.Bootstrapper.dll Status : NotSigned StatusMessage : The file C:\Temp\intel15G\CommandLineUtility.dll is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170
Path : C:\Temp\intel15G\CommandLineUtility.dll Status : NotSigned StatusMessage : The file C:\Temp\intel15G\Intel.Tools.dll is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170
Path : C:\Temp\intel15G\Intel.Tools.dll Status : NotSigned StatusMessage : The file C:\Temp\intel15G\winterop.dll is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170
Path : C:\Temp\intel15G\winterop.dll Status : NotSigned StatusMessage : The file C:\Temp\intel15G\wix.dll is not digitally signed. You cannot run this script on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170
Path : C:\Temp\intel15G\wix.dll
Errors in the Windows CodeIntegrity log will be similar to:

Figure 1: Windows CodeIntegrity log example
The PowerEdge R6515/R7515 with the AMD Milan chipset DUP version 2.18.30.202 package encounters similar errors, but the filenames called out will be the AMD-related filenames that were not signed - such as nsExec.dll.
There are two known Dell use cases for WDAC as Enforced:
-
APEX Cloud Platform for Azure - WDAC as Enforced by default on all deployments
-
In-Market Solution with 23H2 also has WDAC as Enforced by default.
Cause
Resolution
Dell Engineering is aware of the issue when setting WDAC to enforced and is working on an updated DUP package with properly signed components from our vendor.
The current engineering recommendation is to install the updated chipset DUP packages when they are available.
The updated 15G and 16G Intel Chipset driver DUP package is planned to be web promoted in early January 2024 with a factory install targeted for June block 2024.
The updated 14G Intel Chipset driver DUP package is planned to be in the upcoming June block 2024.
The update AMD Chipset driver DUP package is planned to be web promoted and factory installed in April 2024 block.
The iDRAC enablement of the WDAC feature is targeted for a March block 2024 release.
The Solutions using WDAC configured to "enforced" uses other update methods until the updated DUP chipset packages are available.
This article is updated as new information becomes available.