Windows Update Issues: 5 Broken Updates from 2013
The State of Windows Updates in 2013
A noticeable decline in quality control was observed with Windows Update throughout 2013. This appeared to coincide with Microsoft’s increased efforts to accelerate the release of software updates.
Several buggy and faulty Windows Updates were distributed to users during the year, raising concerns about the testing process.
Surface Pro 2 Firmware Issue
The culmination of this trend occurred with the release of a defective firmware update specifically for the Surface Pro 2 device.
Following the release of this problematic update, Microsoft personnel reportedly began a scheduled break, resulting in a delay of over a month before a resolution was implemented.
This incident underscored a challenging year for Microsoft regarding the reliability of its update mechanisms.
The extended period without a fix further amplified user frustration and highlighted the potential consequences of prioritizing speed over thorough testing.
Surface Pro 2 December Firmware Update
A firmware update for the Surface Pro 2 PC was issued by Microsoft on December 10, 2013. Microsoft routinely releases these firmware updates on a monthly schedule. Typically, these updates are delivered through Windows Update and are often installed automatically during the regular update process.
The release notes for this particular firmware update suggested improvements to battery life and power conservation features. However, the update had the unintended consequence of diminishing battery performance for many users. Numerous Surface Pro 2 owners reported a significant reduction in battery life and a malfunctioning sleep function following the installation.
Due to the nature of this update – a UEFI firmware update akin to a BIOS update – a standard uninstall process was unavailable. Users were unable to revert to a previous, stable state. Microsoft withdrew the update on December 18th, more than a week after its initial release.
The company stated the removal was to “ensure the best experience for our customers during the holiday season.” They indicated that work was underway to provide a revised update package following the holidays. While Microsoft aimed to prevent new Surface Pro 2 purchasers from encountering these issues, existing customers were left without a solution throughout the holiday period.
A new firmware update is now scheduled for release on January 14, 2014. This represents a delay of over a month from the initial deployment of the problematic firmware. The extended timeframe has been attributed to Microsoft employees being on holiday leave.
Some view Microsoft’s monthly firmware updates as evidence of strong support for Surface hardware. However, this incident casts doubt on that notion, suggesting that the frequent release of such updates may not always be beneficial. The practice contrasts with that of most PC manufacturers.
Fortunately, the update installation failed silently for a number of users. Circumventing this error necessitates a complex workaround involving disabling a Windows service and deleting a specific system file.
Image
The image illustrates issues related to Windows Updates.
Addressing Mouse Lag in Windows 8.1 Games
Mouse lag in PC games on Windows 8.1 became a concern for many players following the operating system's release. While Windows 8.1 refined several aspects of its predecessor, Windows 8, it inadvertently introduced latency issues affecting mouse input.
This issue stemmed from alterations in the system's handling of mouse functionality. Consequently, a noticeable delay was experienced by gamers in a variety of titles.
Microsoft's Solution: A Registry-Based Fix
To resolve the increased mouse lag, Microsoft released an update. This update implemented a compatibility setting designed to mitigate the problem.
However, the solution requires users to manually adjust the Windows Registry. Specifically, gamers must create compatibility keys for each game individually experiencing the lag.
- This involves navigating to specific registry locations.
- The process necessitates creating new keys and values.
- Each affected game requires its own unique compatibility configuration.
The update doesn't automatically apply the fix; it provides the tools for users to implement it themselves. This manual intervention is necessary to restore optimal mouse responsiveness within games.
Related: Troubleshooting PC Game Mouse Lag on Windows 8.1
KB2823324 and Resulting System Crashes
KB2823324, a Windows update, was found to be a significant cause of blue screens of death (BSOD) upon system restart for numerous Windows 7 users. Microsoft subsequently withdrew the patch due to the widespread issues it created.
The problems appeared to be triggered by the presence of specific third-party applications on affected computers. These included Kaspersky Antivirus software and the G-Buster browser security extension, which is popular in Brazil.
To address the boot failures caused by the faulty update, Microsoft developed and released a repair disc. This disc enabled users to restore functionality to Windows installations that were unable to start normally.
Details of the Issue
The update's incompatibility with certain software led to critical system errors. This resulted in the infamous blue screen, halting the boot process.
Affected users experienced instability immediately after applying the KB2823324 patch and attempting to reboot their systems.
The repair disc provided a method for recovering from the update-induced boot failures, offering a solution for those unable to access their Windows 7 operating systems.
- Update Identifier: KB2823324
- Operating System: Windows 7
- Primary Symptom: Blue Screen of Death (BSOD) on reboot
- Affected Software: Kaspersky Antivirus, G-Buster
KB2803821 Introduced Issues with WMV and Steam Games
The Windows update designated KB2803821, released for Windows 7, Windows Vista, and Windows XP, resulted in compatibility issues for applications relying on Microsoft’s Windows Media Video (WMV) support.
Specifically, several Steam games experienced malfunctions, including broken cut scenes and introductory movies.
Beyond gaming, the update negatively impacted numerous other software programs, affecting both the playback and encoding of WMV files.
Programs confirmed to be affected included industry-standard applications such as Adobe After Effects, Adobe Photoshop, and Adobe Premiere Pro.
Camtasia Studio was also among the software packages experiencing difficulties following the installation of KB2803821.
Users encountering these problems were often required to independently research the issue and manually remove the update to restore functionality.
The malfunction presented in an unusual manner, often displaying videos that only rendered correctly on one half of the screen, leaving the remaining portion black.
KB2821895 Causes System File Checker Issues and Elevated CPU Load
A problematic update, identified as KB2821895 for Windows 8, introduced significant issues concerning the functionality of the System File Checker.
Specifically, the standard sfc /scannow command – utilized for scanning and repairing Windows system files – began exhibiting erratic behavior following the update’s installation.
Users reported that executing sfc /scannow would result in a prolonged freeze, lasting approximately ten minutes, before ultimately displaying reports of corrupted files and prompting a system reboot for repair.
However, the reported file corruption is inaccurate. Repeated execution of the same command post-reboot consistently identifies the same files as corrupted.
Furthermore, this flawed process could initiate automatically in the background, leading to unexpectedly high CPU usage without any discernible user activity.
As a resolution, Microsoft advises utilizing the DISM /online /cleanup-image /restorehealth command for users experiencing these difficulties.
Alternative Repair Method
The DISM command offers a viable alternative for addressing the issues caused by KB2821895.
This command focuses on restoring the health of the Windows image, effectively circumventing the problems encountered with the System File Checker.
Evaluating the Reliability of Windows Update
The issues highlighted represent only a fraction of the difficulties encountered this year with Windows updates. Several other updates have resulted in malfunctions within Microsoft Outlook and the Exchange server; notably, Microsoft acknowledged releasing an Exchange patch prior to adequate testing procedures.
Multiple problematic patches were deployed during "Patch Tuesday" across numerous months. Despite these concerns, maintaining current Windows Updates remains advisable for all Windows users.
However, improvements in Microsoft's quality assurance testing processes are crucial. Fortunately, updates causing issues can generally be uninstalled post-implementation – barring instances of system crashes, which are infrequent.
Users with Microsoft Surface devices should consider delaying the installation of the newest firmware updates for a period of several weeks. Unlike standard updates, these firmware versions cannot be removed.
The Need for Enhanced Quality Control
A proactive approach of waiting before installation is preferable to enduring extended delays while Microsoft addresses device malfunctions. The company's ambition to accelerate software updates appears to be compromising stability.
More rigorous quality assurance is essential. In situations involving severely flawed updates, such as the Surface Pro 2 firmware incident, a dedicated, all-hands-on-deck response is warranted to expedite resolution.
Image attribution: ToddABishop via Flickr, Michael Ocampo via Flickr.