Windows devices may fail to boot after installing KB4041676 or KB4041691 Workaround

蔚落 2024-04-18 18:27 16阅读 0赞

## Windows devices may fail to boot after installing October 10 version of KB4041676 or KB4041691 that contained a publishing issue ##

Applies to: Windows Server 2016Windows 10, version 1607Windows 10, version 1703

--------------------

### Overview ###

--------------------

Microsoft is aware of a publishing issue with the October 10th, 2017 monthly security updates for Windows 10 version 1703 (KB4041676) and version 1607 (KB4041691), and Windows Server 2016 (KB4041691) for WSUS/SCCM managed devices. Customers that download updates directly from Windows Update (Home and consumer devices) or Windows Update for Business are not impacted.

We have corrected the publishing issue as of the afternoon of October 10th and have validated the cumulative security updates. We recommend all customers take these cumulative security updates.

We have reports of the following symptoms impacting Windows Server Update Services (WSUS) and System Center Configuration Manager (SCCM) customers. Mitigation plans for the following user reported scenarios can be found below.

1.  **WSUS/SCCM Administrators that synced the October 10th update (KB4041676 or KB4041691) before 4pm PDT October 10 may still have these KBs cached.**
2.  **WSUS/SCCM managed devices that downloaded the October 10 KB4041676 or KB4041691 update with publishing issues and have devices in a pending reboot state.**
3.  **WSUS/SCCM managed devices that installed the October 10 KB4041676 or KB4041691 update and are unable to boot and/or may land on a recovery screen.**

### Issue Details ###

--------------------

[Scenario 1: WSUS/SCCM Administrators that synced the Delta Package versions of KB4041676 or KB4041691 before 4pm PDT October 10 may still have these KBs cached][Scenario 1_ WSUS_SCCM Administrators that synced the Delta Package versions of KB4041676 or KB4041691 before 4pm PDT October 10 may still have these KBs cached]

**Workaround**

WSUS/SCCM administrators should re-scan for updates to automatically resolve the publishing issue. The issue is already resolved in WSUS hierarchies that have scanned since 4PM on October 10th. Ensure your upstream and downstream servers are in sync.

[Scenario 2: WSUS/SCCM managed devices that have downloaded and staged the Delta Package versions of KB4041676 or KB4041691 but have not rebooted to install][Scenario 1_ WSUS_SCCM Administrators that synced the Delta Package versions of KB4041676 or KB4041691 before 4pm PDT October 10 may still have these KBs cached]

**Workaround**

If a device has downloaded and staged Delta Package versions of KB4041676 or KB4041691, a user may fail to boot after restarting. System administrators can remove pending updates by running the following commands from an administrative command prompt on the device:

`@echo off`

`REM Stop all update related services net stop usosvc net stop wuauserv net stop trustedinstaller`

`REM Delete pending.xml if it exists takeown /f %windir%\winsxs\pending.xml >NUL 2>&1 icacls %windir%\winsxs\pending.xml /grant Everyone:F >NUL 2>&1 del %windir%\winsxs\pending.xml >NUL 2>&1`

`REM Modify the components hive reg unload HKLM\Components >NUL 2>&1 reg load HKLM\ComponentsHive %windir%\system32\config\COMPONENTS reg delete /f HKLM\ComponentsHive /v PendingXmlIdentifier >NUL 2>&1 reg delete /f HKLM\ComponentsHive /v PoqexecFailure >NUL 2>&1 reg delete /f HKLM\ComponentsHive /v ExecutionState >NUL 2>&1 reg delete /f HKLM\ComponentsHive /v RepairTransactionPended >NUL 2>&1 reg delete /f HKLM\ComponentsHive /v AIFailureInformation >NUL 2>&1 reg delete /f HKLM\ComponentsHive\Installers\RegKeySDTable /v Install >NUL 2>&1 reg delete /f HKLM\ComponentsHive\Installers\RegKeySDTable /v Uninstall >NUL 2>&1 reg delete /f HKLM\ComponentsHive\Installers\RegKeySDTable /v Uninstall >NUL 2>&1 reg unload HKLM\ComponentsHive`

`REM Stop Poqexec from running reg delete /f HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Configuration /v DontRunPoqexecInSmss >NUL 2>&1 reg delete /f HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Configuration /v PoqexecCmdline >NUL 2>&1 reg delete /f "HKLM\System\CurrentControlSet\Control\Session Manager" /v SETUPEXECUTE >NUL 2>&1 REG ADD "HKLM\System\CurrentControlSet\Control\Session Manager" /v SETUPEXECUTE /t REG_MULTI_SZ /d \0 /f`

`dism /online /remove-package /PackageName:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~15063.674.1.8 /norestart >NUL 2>&1 dism /online /remove-package /PackageName:Package_for_RollupFix_Wrapper~31bf3856ad364e35~x86~~15063.674.1.8 /norestart >NUL 2>&1 dism /online /remove-package /PackageName:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~14393.1770.1.6 /norestart >NUL 2>&1 dism /online /remove-package /PackageName:Package_for_RollupFix_Wrapper~31bf3856ad364e35~x86~~14393.1770.1.6 /norestart >NUL 2>&1`

[Scenario 3: WSUS/SCCM managed devices that installed the Delta Package versions of KB4041676 or KB4041691 and are unable to boot and/or see a recovery screen][Scenario 1_ WSUS_SCCM Administrators that synced the Delta Package versions of KB4041676 or KB4041691 before 4pm PDT October 10 may still have these KBs cached]

**Workaround**:

Important

These steps should only be followed on a device that fails to boot.

1.  Plug into AC power and turn on the device.
2.  If the device fails to boot, Windows will attempt to repair your device and enter the Windows 10 Recovery Environment. Select “Advanced options” on the Automatic Repair screen.

![Auto Repair][]

1.  Select “Troubleshoot”, then “Advanced Options”, and then “System Restore”. If a restore point is available prior to the installation of KB4041676 or KB4041691, use the System Restore wizard to restore to the earlier Restore Point. If a restore point does not exist, close System Restore’ and continue to the next step.
2.  Select “Troubleshoot”, then “Advanced Options” and then “Command Prompt”. You may be asked to enter a BitLocker Recovery Key or username/password. If prompted for a username/password, you must enter a local account. If you do not have credentials, you many need to create and use a [Recovery Drive][].

![Advanced Options][]

1.  After the Command Prompt launches, run the following to load the software registry hive:

`reg load hklm\temp <drive letter for windows directory>\windows\system32\config\software`

**Example**: `reg load hklm\temp c:\windows\system32\config\software`

1.  Run the following command to delete the SessionsPending registry key. If the registry value does not exist, proceed to the next step.

`reg delete “HKLM\temp\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending” /v Exclusive`

1.  Run the following to unload the registry:

`reg unload HKLM\temp`

1.  Run the following command, which will list all pending updates:
    
    `dism.exe /image:<drive letter for windows directory> /Get-Packages`
    
    **Example**: `dism.exe /image:c:\ /Get-Packages`
2.  Run the following command for each packages where “State = Install Pending”:
    
    `dism.exe /image:<drive letter for windows directory> /remove-package /packagename:<package name>`
    
    **Example**: `dism.exe /image:c:\ /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad365e35~amd64~~15063.674.1.8`
    
    `dism.exe /image:c:\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad365e35~amd64~~15063.674.1.8`
3.  Close the Command Prompt and click ‘Continue’ to exit the recovery environment.

--------------------

Last Updated: Oct 14, 2017

[Scenario 1_ WSUS_SCCM Administrators that synced the Delta Package versions of KB4041676 or KB4041691 before 4pm PDT October 10 may still have these KBs cached]: https://support.microsoft.com/
[Auto Repair]: https://imgconvert.csdnimg.cn/aHR0cHM6Ly9tc2VnY2Vwb3J0aWNvcHJvZGFzc2V0cy5ibG9iLmNvcmUud2luZG93cy5uZXQvYXNzZXQtYmxvYnMvNDA0OTA5N19lbl8x?x-oss-process=image/format,png
[Recovery Drive]: https://support.microsoft.com/help/4026852/windows-create-a-recovery-drive
[Advanced Options]: https://imgconvert.csdnimg.cn/aHR0cHM6Ly9tc2VnY2Vwb3J0aWNvcHJvZGFzc2V0cy5ibG9iLmNvcmUud2luZG93cy5uZXQvYXNzZXQtYmxvYnMvNDA0OTA5OF9lbl8x?x-oss-process=image/format,png