New operating systems are never perfect from the start, and Windows 8 is certainly no exception.
Not only will early Win8 adopters and testers continue to see numerous updates, they should not be surprised when some of those patches fail.
Win8 stumbles at the gate with patching problem
Microsoft officially releases Windows 8 to the public tomorrow, Oct. 26. Getting comfortable with Windows 8 will give many of us enough angst; we don’t need a patching problem to add more. And yet that’s exactly what’s happening: a Win8 patching error has cropped up just as the OS is heading out the gate.
In the massive Oct. 11 Patch Watch column, I discussed KB 2756872, a near service pack–level update for Windows 8 that included a fix for Microsoft’s major security certificate–signing debacle. Unfortunately, numerous early Win8 adopters have run into difficulties installing KB 2756892. It stalls at “13%” and never completes the installation process, as reported by users in a long Microsoft Community Windows Answers forum.
This week, Microsoft released KB 2770816 to patch the patch, though the fix might not be 100 percent effective, either. KB 2770816 is useful (and will be offered) only if a Windows 8 machine has had Realtek Audio drivers installed by the user. However, posts in the aforementioned Answers forum suggest there might be other causes for KB 2756872 stalling, requiring additional patches.
In the past, I’ve recommended deploying a new operating system only after Microsoft has released its first service pack. I rescinded that rule with Windows 7, due to its relatively painless launch. Nevertheless, moving to a new OS is almost always bumpy, and Windows 8 will have its share of problems.
Some of these updates are necessary, others are not. For example, Microsoft updated Internet Explorer 10’s built-in Flash Player — always important — with KBs 2758994 and 2755801 (updated Oct. 23). On the other hand, KB 2607607 simply offers new Win8 language packs.