Issue 1A Windows 8-based or Windows Server 2012-based computer experiences high CPU usage when it runs a Windows Update applicability scan. Additionally, the applicability scan takes longer than expected.
Issue 2Duplicate entries are logged in the CBS log file when the Windows 8-based or Windows Server 2012-based computer runs an automatic Windows Update applicability scan.
Note The path of the CBS log file is C:\Windows\Logs\CBS\CBS.log.
Issue 3Consider the following scenario:
- You start Windows Internet Explorer on a Windows 8-based or Windows Server 2012-based computer.
- You install the Microsoft update for Adobe Flash Player in Internet Explorer (update 2755399).
- You perform either of the following operations:
- You install an update that contains drivers.
- You install an update that does not contain drivers, and then you install an update that contains drivers.
- You install another update, and then you restart the computer.
Issue 4When you install all the latest driver updates on a computer that is running Windows 8 or Windows Server 2012, certain system drivers (for example, Acpi.sys) in the following location are not updated:
Issue 5Assume that you try to install a servicing update on a computer that is running Windows 8 or Windows Server 2012. If the servicing update contains a driver update (especially an audio driver update), the servicing operation fails, and you cannot install the servicing update.
Issue 6Assume that several updates cannot be installed because of a failure that relates to one of these updates on a computer that is running Windows 8 or Windows Server 2012. In this situation, the other updates that are installed bundled with this update cannot be reinstalled even when the failure is resolved. If you try to reinstall the other updates, you receive a "CBS_E_SOURCE_MISSING" error message.
Issue 7Assume that you try to install the Application Server role together with Microsoft SharePoint or an independent software vendor customer application on a Windows Server 2012-based computer. In the case of certain timing conditions, the installation operation fails, and then it rolls back and restarts in an infinite loop.
Note The Application Server role is installed by using the Add Server Role Wizard or the Deployment Image Servicing and Management (DISM) tool.
Issue 8When an update for a "Features on Demand" Windows feature (for example, the .NET Framework 3.5) is already installed on a computer, the feature cannot be enabled.
Note Windows 8 and Windows Server 2012 have the .NET Framework 3.5 disabled by default.
For more information about how to configure Features on Demand, go to the following Microsoft website:
How to obtain this update
Windows UpdateThis update is available from Windows Update.
Microsoft Download CenterThe following files are available for download from the Microsoft Download Center:
|All supported x86-based versions of Windows 8||Download the update package now.|
|All supported x64-based versions of Windows 8||Download the update package now.|
|All supported x64-based versions of Windows Server 2012||Download the update package now.|
PrerequisitesTo apply this update, you must be running Windows 8 or Windows Server 2012.
Registry informationTo apply this update, you do not have to make any changes to the registry.
Restart requirementYou do not have to restart the computer after you apply this update.
Update replacement informationThis update does not replace a previously released update.
Removal informationAfter you install this servicing stack update, you cannot uninstall it to revert to an earlier version of servicing stack update.
File informationThe global version of this update installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Note The files in the update package may be added to the %windir%\WinSxS\ folder instead of the %windir%\System32\ folder.
Windows 8 and Windows Server 2012 file information notes
- The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version Product Milestone Service branch 6.2.920 0.16 xxx Windows 8 and Windows Server 2012 RTM GDR
- GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
- The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows RT, Windows 8, and Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8
For all supported x64-based versions of Windows 8 and of Windows Server 2012
Additional file information
Additional file information for Windows RT, Windows 8, and Windows Server 2012
Additional files for all supported x86-based versions of Windows 8
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
ID d'article : 2771431 - Dernière mise à jour : 24 déc. 2015 - Révision : 1