One Step Closer to the Final Build of the Windows 10 Anniversary Update

One Step Closer to the Final Build of the Windows 10 Anniversary Update

This past week we looked closely at Windows 10 Build 14393 when it was released and the remaining known issues in this build to determine if it was the final code Microsoft would be releasing publicly on 02 August as the Windows 10 Anniversary Update.

When they moved build 14393 to the Slow Ring about 24 hours later and cleared up two of the remaining known issues, the odds of 14393 being the official Anniversary Update increased significantly.

Then, on Friday afternoon, Microsoft issued the first cumulative update for Windows 10 build 14393 on PCs and Mobile devices and this gives us the best proof yet that this current testing build will be the final version for the Windows 10 Anniversary Update.

By issuing just a cumulative update (KB3176925) of 6.2MB instead of an entirely new testing build, Microsoft is just patching the specific elements of the operating system that need to be fixed. If the Windows 10 Anniversary Update was going to be a build different than 14393 then they would have been more likely to issue a full build update to address these bugs.

The following items are listed in the Windows 10 Feedback Hub as fixed in this cumulative update:

  • We have fixed an issue where keyboard input on some Windows tablet devices would not rotate to landscape normally.
  • We have fixed an issue that results in Windows Updates being delayed on systems with Connected Standby.
  • We have fixed a problem with text input with Korean Input Method Editor (IME) in some Store apps.
  • We fixed an issue causing Store apps to stop launching due to a licensing issue.
  • We have fixed an issue with apps that synchronize using DDE for inter-process communication.

So the likelihood of Windows 10 Build 14393, now 14393.3 after the cumulative update is applied, being released as the Anniversary Update is pretty close to a sure thing.

There is one more thing to add that is a possibility with the build numbering. Microsoft could decide to bump the build number to something different before release, say 14400, just to give the build a nice round number. That would let them start from a clean build designation just like they did with 10240 the original Windows 10 release and 10586 the November Update.

Windows Insiders can grab this patch from Windows Update on their PC and Mobile devices running build 14393.

But, wait...there's probably more so be sure to follow me on Twitter and Google+.

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.