Please provide your feedback in this short Flings' survey.
fling logo of VMware CPU Microcode Update Driver

VMware CPU Microcode Update Driver

version 2.1 — June 06, 2016

Contributors 4

View All

Comments 145

  • profile picture of GoneToPlaid
  • profile picture of Jacob Klein
  • profile picture of GoneToPlaid
  • profile picture of Jacob Klein
  • profile picture of GoneToPlaid
  • profile picture of Jacob Klein
  • profile picture of himtan
  • profile picture of Jacob Klein
View All

Summary

This Fling is a Windows driver that can be used to update the microcode on a computer system’s central processor(s) (“CPU”). This type of update is most commonly performed by a system’s firmware (“BIOS”). However, if a newer BIOS cannot be obtained from a system vendor then this driver can be a potential substitute.

Features

The driver can update the firmware on Intel or AMD CPUs. The driver attempts to update the processor when the driver is started, when the system is booted, or when the system resumed from a low power state (e.g., hibernation).

The driver will report its actions in the OS’s event log that can be examined using “Event Viewer”. The driver reports whether it found supported processors and if an update was attempted or successfully performed on a processor. This information lets the user know whether the driver is providing a benefit (otherwise they can uninstall it). For example, the processors might already have the latest firmware version.

eventvwr

Requirements

A system running Windows Server 2003 or later.

Instructions

1. Download the fling's zip file and extract the files contained within the zip.
2. Download these 2 files and place them in the same directory as where the files from #1 were placed:

https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/plain/amd-ucode/microcode_amd.bin
https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/plain/amd-ucode/microcode_amd_fam15h.bin

3. Obtain a microcode file for Intel processors and place the "microcode.dat" file in the
same directory as where the files from #1 were placed.

An example URL for a file to download is:

https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23829

This download is for a "tgz" file (i.e., a compressed tar file). You will need to extract
the "microcode.dat" file that is contained within the "tgz" file (this will likely require
the use of a 3rd party archive utility).

If you have an AMD processor and do not want to obtain an Intel firmware
file then you can also create an empty "microcode.dat" file instead.

4. Run (e.g., double-click on) the "install.bat" file. The install will attempt to report if it was successful.

The system's "Event Viewer" can be used to determine whether the fling was able to find an updated firmware for the processor and apply an update. The "Event Viewer" can be started by running the command "eventvwr" from the Start Menu. Inside "Event Viewer" you can use the left pane to navigate to "Windows Logs" and then "System". The middle pane will display the most recent system events, and there should be an event from source "cpumcupdate" that will report if an update was attempted or successful.

The fling has performed an update if the event reports "Successfully updated microcode on one or more CPUs". The firmware update must be applied each time the processor is turned on, so the driver must remain installed in order to keep the processor updated.

If the event reports "The model of the CPU is not supported", or "An update for this model of CPU was not found", or "An update for this model of AMD CPU was not found" then the fling is not providing a benefit and can be uninstalled.

The event "No CPUs needed an update" typically means that the fling is not providing a benefit and can be uninstalled. However, there is an exception. For example, if you install the fling, uninstall it, and then install the fling again then the first run can report "Successfully updated microcode..." and the second run will report "No CPUs needed an update". This is because the second run does not know the processor was already updated by the first run. To disambiguate this case you can shutdown the computer to a powered off state, turn the computer back on, and then look for the event that was generated while the system was booting.

 

Changelog

Version 2.1

A user reported our microcode update fling failed to load microcode on an AMD family 15h processor. It turned out there were a couple of minor problems:

  • IsGoodAMDUpdate was using a hardcoded size of 2048, but according to the BKDG for family 15h the size will be 4096.
  • The check for patches requiring x86 code to be executed in IsGoodAMDUpdate is not applicable on family 15h.

These problems are fixed in this 2.1 release.

Similar Flings

No similar flings found. Check these out instead...
Jun 02, 2021
fling logo of Resource-Efficient Supervised Anomaly Detection Classifier

Resource-Efficient Supervised Anomaly Detection Classifier

version 1.0.0

Resource-Efficient Supervised Anomaly Detection Classifier is a scikit-learn classifier for resource-efficient anomaly detection that augments either Random-Forest or XGBoost classifiers to perform well in a resource-constrained setting.

Dec 06, 2018
fling logo of Dispatch-Solo

Dispatch-Solo

version 0.0.5

Dispatch-Solo is lean version of Dispatch, which has been packaged as VM appliance.

Oct 28, 2013
fling logo of Lctree

Lctree

version 1.1

Lctree is a tool designed for the visualization of linked clone VM trees created by VMware vCloud Director. Linked clone is a feature available in vSphere that creates a clone of a VM from a snapshot point.

Nov 29, 2022
UPDATED
fling logo of Sample Exchange PowerShell ISE Integration

Sample Exchange PowerShell ISE Integration

SampleExchangePowerCLI Module
A PowerShell Module that contains integration between VMware's new sample code repository Sample Exchange, and PowerShell ISE. Sample Exchange contains an ever growing catalog of PowerCLI samples and snippets, and this module uses Sample Exchange REST web services to allow a user to paste sample code into their editors directly in PowerShell ISE.
Pre-Requisites
PowerShell version 4 or later.
Installation
1) Download (or clone) all files comprising the module.
2) Create a folder for the module in your module folder path, e.g. C:\Users\username\Documents\WindowsPowerShell\Modules\SampleExchangePowerCLI
3) Place the module files in the above folder. The SampleExchangePowerCLI.psd1 and SampleExchangePowerCLI.psm1 files should be in the root of the folder
NOTE: If you create the folder in the path above, then PowerShell ISE (and regular PowerShell windows) will load the module.
If you don't want to do this, you can manually install the module by running the command
PS C:> Import-Module -Force -Verbose C:\local\path\where\you\extracted\SampleExchangePowerCLI
where SampleExchangePowerCLI is the folder containing SampleExchangePowerCLI.psd1 and SampleExchangePowerCLI.psm1.
4) Restart PowerShell ISE
5) If you would like to have Sample Exchange samples available via the PowerShell ISE Snippets feature, Go to "Add-ons" > "Sample Exchange" > "Sync Snippets"
This command is the equivilent of calling the "Sync-SampleExchangeSnippetsWithISE" method directly. It downloads all samples and registers them as "Snippets" in PowerShell ISE thus making them available for use in the editor when you issue the "CTRL + J" hot-key.
If you later decide that you do not like this, you can simply go to C:\Users<user>\Documents\WindowsPowerShell\Snippets and delete all of the VMW*.ps1xml files and the snippets will go away.
Usage
Selecting Either Add-ons > VMware Sample Exchange > Search Samples, or hitting "CTRL + SHIFT + S" will bring up a dialog box which lists all available PowerShell language samples by default. You can additionally enter a search term and click the "Search" button to additionally filter the list.
Select any sample from the list and click the "Insert in Editor" button to insert the given sample code at the location of the cursor in the editor that had focus when the dialog was opened (yes, it doesn't work to select another editor after the dialog is opened, sorry).
If you click "OK" the sample content is pasted in the shell. "Cancel" simply closes the window.
To see a list of available functions:
Get-Command -Module SampleExchangePowerCLI

Oct 28, 2015
fling logo of Onyx for the Web Client

Onyx for the Web Client

version 1.0

Onyx for the Web Client is a Fling that translates actions taken in the vSphere Web Client to PowerCLI.Net code. This Fling was the winning entry in last year’s 2014 Fling Contest. It’s an update, of sorts, to the Onyx fling, as it allows for similar functionality in the web client.

Jun 18, 2012
fling logo of gemcached

gemcached

version 0.2

gemcached is a memcached server written in Java that understands memcached's ASCII protocol and translates it into GemFire operations.

View More