KB32480179 Hotfix for Configuration Manager 2503

Microsoft has released hotfix KB32480179 for Configuration Manager version 2503, specifically resolving PXE boot issues. Released on May 8, 2025, this update can be installed via the Updates and Servicing node in the Configuration Manager console.

The initial release of ConfigMgr 2503 CB update (KB31909343) included fixes for approximately 350 bugs that have affected system performance and user experience. However, the fix for the PXE boot error 0x80090008 wasn’t included with it.

The KB32480179 hotfix is aimed at administrators who used a PowerShell script to obtain the early update ring for SCCM 2503. After updating to version 2503, PXE clients were stuck in the “Waiting for Approval” stage.

Note: The update KB 32480179 doesn’t show up in the console on sites that downloaded version 2503 on April 23, 2025, or a later date. This hotfix is applicable only for early update ring adopters of 2503.

Issues fixed in KB32480179 Update

According to Microsoft documentation, the PXE clients remain stuck in the “Waiting for Approval” stage after updating to Configuration Manager version 2503. If the option to “Require a password when computers use PXE” is not checked, the issue is triggered.

The SMSPXE.log file contains errors like the following.

PXE::CRYPT::CalcHMACBuffer failed; 0x80090008
PXE::CRYPT::CreateVarFileKey failed; 0x80090008

If you’re encountering the above PXE issues in your setup, install the KB32480179 hotfix to get them resolved.

Install the KB32480179 Hotfix

Launch the Configuration Manager console on the server. Navigate to Administration\Overview\Updates and Servicing. Right-click Configuration Manager 2503 Hotfix (KB32480179) update and select Install Update Pack.

The hotfix includes updates to Configuration Manager site server (5.2503.9135.1003). Other components such as Configuration manager clients and console aren’t affected by this update.

Complete the steps included in the Configuration Manager hotfix installation wizard and wait for the hotfix to install. This update doesn’t require a computer restart but will initiate a site reset after installation.

To verify if the KB32480179 hotfix is installed, open the console and go to Administration > Updates and Servicing. If the State column for the hotfix shows ‘Installed‘, it means the update installation is completed.

Updating KB32480179 on Secondary Sites

After installing the hotfix update KB32480179 on a primary site, pre-existing secondary sites must be manually updated. This must be done on all the secondary sites present in your setup.

On the Secondary site server, open the Configuration Manager console. Go to Administration > Site Configuration > Sites > Recover Secondary Site, and then select the secondary site. Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:

select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')

If the above command returns value 1, it means the site is up-to-date, with all the hotfixes applied on its parent primary site. If the value 0 is returned, the site has not installed all the fixes that are applied to the primary site. You should use the Recover Secondary Site option to update the secondary site.

Update your Boot Images

After installing hotfix KB 32480179, update both your default and custom boot images across all distribution points. Configuration Manager 2503 requires ADK version 10.1.26100.2454 (Updated Dec 2024) and the corresponding ADK-PE; otherwise, the task sequence will fail to start.