This post is more than 5 years old
6 Posts
0
8446
October 14th, 2016 19:00
Updating Server 2016 chipset driver on R720XD
I tried installing the Server 2016 chipset driver on my R720XD but was met with the following error message: ''Update is terminated, as the lockdown mode is enabled. Disable the lockdown mode and try the update again"
The OS is the RTM version of Server 2016. Nothing else is installed, apart from Dell OMSA 8.4. The Hyper-V role is enabled with no VMs running.
This is the driver I was trying to install: http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=GKXMM
I was able to work-around the problem by extracting the installer with 7-zip and then running the Intel chipset installer directly.
What is lockdown mode and how do I turn it off? Or is this a driver installer error?
ludwigit
4 Posts
3
October 26th, 2016 12:00
I was able to install the driver after I extracted the contents of the Dell EXE using 7-Zip. You obviously shouldn't have to do that, but it works.
mvoss2503
1 Message
1
December 8th, 2016 22:00
Hi, I have successfully installed the driver, by unzipping the package.
First I tried to install the chipset driver of Poweredge R630 by using SUU. But installation was terminating, all times.
Then, I downloaded the same driver seperately from support.dell.com. Using a doubleklick, I get the same error.
But after unzipping the package, I was able to install the driver without problems by using the SetupChipset.exe
adbl
6 Posts
0
October 14th, 2016 19:00
Update - I get the same error message after removing the Hyper-V role on the server
ablanken
3 Posts
0
October 17th, 2016 16:00
The previous chipset driver installs without any warnings - http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=5WJX9.
It appears to be packaged differently than the new driver which fails to install
DELL-Josh Cr
Moderator
•
9.2K Posts
0
October 17th, 2016 18:00
Hi,
How far along does it go before it gives that error? The older driver didn't have 2016 support, so the cchanges to driver signing may be the cause. Is secure boot enabled? Was the driver downloaded directly to that system or copied from another system?
ablanken
3 Posts
0
October 17th, 2016 18:00
Hi Josh,
That error is the first thing that appears after starting the updater.
Windows is reporting that the secure boot status is 'unsupported'
The installation package was copied from another system. I unblocked it via file properties but it didn't make a difference.
Here's the setup log:
C:\ProgramData\Dell\UpdatePackage\log\Chipset_Driver_GKXMM_WN64_10.1.2.77_J00.txt
[10/18/16 13:14:36] Update Package Execution Started
[10/18/16 13:14:37] Original command line: "C:\Temp\Chipset_Driver_GKXMM_WN64_10.1.2.77_J00.EXE"
[10/18/16 13:14:37] DUP Framework EXE Version: 3.4.5.40
[10/18/16 13:14:37] DUP Release: GKXMMJ00
[10/18/16 13:14:37] Initializing framework...
[10/18/16 13:14:37] Data in smbios table is (hex)value = 97 , Chasis type (hex)value = 17 , System type is : Server
[10/18/16 13:14:37] Server Infrastructure Detected...Proceeding with PM Module...
[10/18/16 13:14:37] Querying Personality Module for data via ..GetPersonalityInfo()
[10/18/16 13:14:45] LockDown: True
[10/18/16 13:14:45] Lockdown feature is enabled.Quitting.
[10/18/16 13:14:49] Name of Exit Code: SUCCESS
[10/18/16 13:14:49] Execution terminated at date-time 10/18/16 13:14:49
[10/18/16 13:14:49] ######
Here's some additional logging from the log file 'dsmipmi_internal': http://pastebin.com/7YDwKHMz
HuggaBounce
37 Posts
0
November 22nd, 2016 20:00
I had the same problem yesterday on my R320 machine but with Windows Server 2012 R2, although I didn't check the installer log, just the error dialog is the same.
Both our servers share the same 12G PowerEdge chipset driver Intel C600/X79 Series Chipset_Driver_GKXMM_WN64_10.1.2.77_J00.EXE
I ended up downloading Chipset_Driver_H2V95_WN32_10.1.2.10_I00.EXE which was satisfactory for my OS version. The only difference I really see between the 2 executable is that the older one is 32-bit whereas the newer one is 64-bit (without the need for WoW).
Maybe the error has nothing to with "lockdown mode". As far as I know this is a VMware function, and I also have no VMs of any kind.