Windows 8.1 Aug Update Released (KB2975719)

By FaiKee
in Microsoft (Windows)

 Share

Recommended Posts

Veteran

FaiKee

Posted
Posted

Tks to @abbodi1406 of MDL : http://forums.mydigitallife.info/threads/55109-News-Discussions-On-Windows-Upcoming-Products-W8-1Update-x-W365-WThreshold-Win9/page200?p=938213&viewfull=1#post938213

 

X86 : http://www.microsoft.com/en-us/download/details.aspx?id=43746

 

X64 : http://www.microsoft.com/en-us/download/details.aspx?id=43753

Veteran

FaiKee

Posted
  • Author
Posted

Now Aug Update is out, we got a clearer picture of this Update:

 

For Update1 released in Apr, it is mandatory, and DISM reports a new base version 9600.17031 from the win8.1RTM base version 9600.16384, and anyone who still using 16384 as of to-day, sorry, no more WU support. Simply said : Update1 build 9600.17031 is the real win8.1RTM.

 

But for Aug Update KB2975719, it is optional, and DISM reports the same base version:

 

screen1702.jpg

 

screen1703.jpg

 

MS is always quite serious on their naming policies, so, the Aug Update couldn't be named Update2 because it is different from Update1.

 

From what I heard(take it as rumor), Project Threshold was started as a Update to transform Win8.1 into a so-called Win7SP2(LOL) and would probably be named Win8.2, But now the plan might change, MS might start to roll out the transform features in patch Tuesdays, in which case WinThreshold(Win8.2) might not be required, but I believe there is still not decided yet.

 

Win9 is another story, it is "3 screens and a cloud with Metro", it is still in early development so MS couldn't know if those "Win7SP2 transformations" could also work well in Win9, AFAIK(again, take as rumor), the 1st win9 Preview would appear in early 2015, RTM is expected in Fall 2015. :)

Veteran

FaiKee

Posted
  • Author
Posted

LOL :laugh:

 

http://support.microsoft.com/kb/2975719

 

Open the tab "More Information":

 

Known issues with this update
  • Known issue 1
    Microsoft is investigating behavior where fonts do not render correctly after any of the following updates are installed:
    2982791MS14-045: Description of the security update for kernel-mode drivers: August 12, 2014
    2970228Update to support the new currency symbol for the Russian ruble in Windows
    2975719August 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
    2975331August 2014 update rollup for Windows RT, Windows 8, and Windows Server 2012
    Status
    Microsoft has removed the download links to these updates while these issues are being investigated.

    Mitigations
    Open the Programs and Features item in Control Panel, and then click View installed updates. Find and then uninstall any of the following update that are currently installed:
    • KB2982791
    • KB2970228
    • KB2975719
    • KB2975331
  • Known issue 2
    Microsoft is investigating behavior where systems may crash with a 0x50 Stop error message (bugcheck) after any of the following updates are installed:
    2982791MS14-045: Description of the security update for kernel-mode drivers: August 12, 2014
    2970228Update to support the new currency symbol for the Russian ruble in Windows
    2975719August 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
    2975331August 2014 update rollup for Windows RT, Windows 8, and Windows Server 2012
    This condition may be persistent and prevent the system from starting correctly.

    Status
    Microsoft has removed the download links to these updates while these issues are being investigated.

    Mitigations
    For more information about how to resolve this, click the following article number to view the article in the Microsoft Knowledge Base. See the section heading "Known issue 3": 
    2982791MS14-045: Description of the security update for kernel-mode drivers: August 12, 2014
Grand Master

+Anarkii Subscriber²

Posted
  • Subscriber²
Posted

Comes as no surprise, I installed the update last week and it took my system into a boot-loop. Only way to fix it was to reinstall Windows from scratch. Restore and Refresh refused to work. So im glad they pulled it to fix the issue.

Grand Master

Syanide

Posted
Posted

I swear to god I am going insane with this, every time there's a Windows update they seem to reset my touchpad driver and the multitouch scroll in Metro apps/UI changes from top-to-bottom to left-to-right. Is there any way to prevent this from happening (or is there an option within Windows to change the scroll behavior)?

Explorer

arseny92

Posted
Posted

Comes as no surprise, I installed the update last week and it took my system into a boot-loop. Only way to fix it was to reinstall Windows from scratch. Restore and Refresh refused to work. So im glad they pulled it to fix the issue.

 

Such boot loops normally caused when you error out the POQ queue by too many pending update operations, and are mitigated when you dism image:d: /revertpendingactions from a WinPE/RE/SE command prompt, complete the operation, reboot and retry the installation.

 

I wonder why MS isn't more nuanced in its language in that KB?  Find and uninstall if you show one of the symptoms maybe?

 

Under what conditions do fonts not render properly?

 

When the font cache becomes corrupted and the system font suddenly changes by itself from Segoe UI to e.g. Marlett, Symbol or Web/Windings

Grand Master

+Anarkii Subscriber²

Posted
  • Subscriber²
Posted

Such boot loops normally caused when you error out the POQ queue by too many pending update operations, and are mitigated when you dism image:d: /revertpendingactions from a WinPE/RE/SE command prompt, complete the operation, reboot and retry the installation.

O.o

Can you dumb that down like 10 levels lol. I got no idea what any of that means. I understand the build up of pending updates but everything after the words POQ queue is like... "what?" :)

Explorer

arseny92

Posted
Posted

O.o

Can you dumb that down like 10 levels lol. I got no idea what any of that means. I understand the build up of pending updates but everything after the words POQ queue is like... "what?" :)

 

http://social.technet.microsoft.com/Forums/windows/en-US/a7c43c9f-e270-4e42-872b-f93b0ed9798d/sfc-has-ridiculously-high-number-of-poq-sections?forum=w7itproperf

http://social.technet.microsoft.com/Forums/windows/en-US/97bd33e5-e335-45eb-a84d-cf57fdf69987/help-fatal-error-c0000034-applying-update-operation-303-of-106925-00000?forum=w7itproinstall

http://social.technet.microsoft.com/Forums/windows/en-US/acc10c1f-e6be-40e1-9540-899c111a16a9/the-mechanics-of-update?forum=w7itprogeneral

 

 

When system get the updates, file and registry changes are primitive operations during this process, system would use primitive installer to take the component change list to generate the list of primitive operations, all primitive operations from all primitive installers together form the POQ (Primitive Operation Queue).

If POQ cannot be executed immediately, system pends the transaction and records the operations in pending.xml file.

There is another operation, advanced installers, which are those operations that for whatever reason cannot be modeled as a simple list of file and registry changes. Advanced  installer operations run as soon as possible after the POQ executed.

 

 Pending.xml is the POQ list of update operations to perform during reboot, and there is a limit on how long the queue can be, to be able to successfully be performed during the boot limited environment at the bootscreen and before logonUI. Things like memory commit charge (disk page file) are not available during the boot process, and CSI (Component Servicing Infrastructure) needs to rely solely on the amount of the available RAM of the system, and to comply with the fact that by default you can only use up to 2GB memory per single process, regardless if you have e.g. 64GB RAM installed.

 

Have a look at this post also for a brief explanation of servicing: http://blogs.technet.com/b/askperf/archive/2008/04/23/understanding-component-based-servicing.aspx .

 

Therefore it is a bad idea to queue too many updates for installation. You can either try the VBS script provided by one of the linked threads above (not recommended, because you will have missing components, i.e. some won't be fully updated), or revert the whole current pending.xml by booting to a recovery command prompt and using DISM /image:x: /cleanup-image /revertpendingactions (where x: substitute the Windows partition in, in the recovery console typically D:, since in this environment C: is assigned to system reserved boot partition), completing the revert operation, rebooting to a now pre-updated state system and retrying the updates, while stacking up lower update amounts to not cause the issue to re-occur.

  • FaiKee, zhangm and +Anarkii
  • Like 3
Grand Master

+Anarkii Subscriber²

Posted
  • Subscriber²
Posted

Thanks Macstar, I was one caught in the boot loop :(

And thanks for the explanation arseny92, very detailed explanation :D
As for all that, I didnt have any pending updates, I always update when its patch tuesday, its just that latest update something was stuffed in it which made the boot loop for me. 

This topic is now closed to further replies.
 Share
Go to topic listing