Windows 8.1 Update Reaches Consumer Install Deadline
- By Kurt Mackie
- June 10, 2014
For individual Windows 8.1 users, Tuesday marked the installation deadline for Windows 8.1 Update.
The June 10 deadline to install the update was extended from Microsoft's original specification of May 13 for consumers. The deadline means that consumer Windows 8.1 users who did not install the update by June 10 will no longer receive future operating system security patches from Microsoft.
It should be noted that the Tuesday deadline does not apply to Windows 8 users, who have until Jan. 12, 2016 to move to Windows 8.1. Also, organizations have a longer leeway to install it, with a deadline of Aug. 12.
Windows 8.1 Update. mostly adds improvements benefiting keyboard and mouse users. It is somewhat different from a traditional update from Microsoft in that it changes the OS' features. In addition, the update sets a new service "baseline" for the OS. Future patches from Microsoft after June 10 will target Windows 8.1 Update, not Windows 8.1.
Users updating Windows 8.1 who have existing Windows Store Apps (formerly known as "Metro" apps) on the system will have to reinstall those apps. They won't necessarily have to install their Desktop apps, though. The update performs a precheck to see if the desktop apps will run on Windows 8.1 Update, and will suggest measures to take, if any, to get them ready.
The update takes 30 minutes to "several hours" to download, depending on the Internet connection, but it also requires a reboot, which can take from 20 minutes to an hour to complete, according to Microsoft's estimate. Microsoft recommends backing up a system's files and apps before applying the update, according to a help article.
The Windows 8.1 Update is described by Knowledge Base article KB 2919355. Microsoft required a "servicing-stack update" as a prerequisite for installing the update, which is described in Knowledge Base article KB 2919442.
Microsoft points out some known install issues that people may encounter in this help article. Users could be experience problems from missing or damaged files needed by Windows Update (error code 0x80073712), incompatible software drivers (error code 0x800F0923) or connection problems to the Windows Update servers (error code 0x800F0922).
Lots more problems (sometimes with solutions) can be found in Microsoft's help forum pages here.
Kurt Mackie is senior news producer for the 1105 Enterprise Computing Group.