Get Windows 8.1.1 through Windows Update RIGHT NOW! (Windows Update/Direct MSU links)

By | March 6, 2014

MDL user “seaa” posted a registry trick that makes the 8.1.1 update show up in Windows Update. Here’s how it works.

WARNING: DO NOT ATTEMPT this if you don’t know what you’re doing, you might brick your current Windows 8.1 installation!!!

Through Windows Update

Update: people are reporting that Microsoft patched this registry hack, please try the direct links below.

In regedit, navigate to “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\” and create a new key called “SHWindowsPoolS14″ (or download and run this .reg file), now reboot your PC and check for new updates. You should see “Update for Windows 8.1 for x64-based Systems (KB2919442) – (S14 Prerequisite v01.0008)“, this is the first in a series of updates that will update your PC to Windows 8.1.1 (or whatever it’s called).

Screenshot (6)Install that one (and any other updates that show up) and check for new updates again after it has installed (you may have to reboot). Now the next update will show up: KB2919355.

Screenshot (8)Install that one too, reboot, check for new updates and install those too!

Installation instructions

Download, unzip and install the MSUs in the following order:

  1. KB2919442
  2. KB2939087*
  3. KB2919355
  4. KB2932046
  5. KB2938439*
  6. KB2937592

It’s important to follow this order exactly! (Minor variations are possible, but just stick to this order, please)

Reboot every time you are asked to do so!

(Updates with a * aren’t part of the Spring Update according to the leaked ADK, but they do show up after the registry hack. Install them, or don’t, but I do recommend you do…)

How is this even possible??

Nobody knows for sure, but I think the registry key is an internal flag used by Microsoft employees who are “dogfeeding” (updating as soon as a new build is available for testing, almost every day) the Windows 8.1 Update. When they enable this key Windows Update will search for updates on an internal, confidential, update server, that way they will easily get the latest updates for testing and they can test if updating works properly. (A similar registry tweak was used during Vista development) Another possibility is that this key was created to specifically test 8.1.1 RTM deployement. We might never know for sure…