According to M$ website, KB2897917-x64 is for Windows 8.0 and NOT for 8.1... In my opinion, it should NOT be LISTed or offered for 8.1...
Fixed, thanks The KB article has not been updated yet, but if you hit "Hotfix Download Available" button you will see that it's available for W 8.1 too
KB2897917 is also listed by Komm as required for 8.1 x64-I installed it both online and integrated offlline. ...not for me-only once.
The current abbodi1406 Windows 8.1 Update List states that KB2968599 has been superseded (by KB2978002), but WHDownloader indicates that KB2968599 is still needed for Windows 8.1-x64... Yea or Nay ???
According to Komm's changelog it is stiil needed to satisfy M$ update only, but, is nevertheless superseeded. If I recall correctly abbod1406 does not care to keep track of these that way; superseeded is superseeded, period. I just hide those that show up in M$ update now.
M$ Update has released a REPLACEMENT version of Windows8.1-KB2975719-x64 as of 2-Sep-2014… WHDownloader currently displays the original version of 5-Aug-2014… When downloaded using WHDownloader, will the original or the REPLACEMENT version be downloaded???
Thanks for this info... Yesterday I used WHDownloader to reacquire the REPLACEMENT version of Windows8.1-KB2975719-x64 and it is 55.1 MB's vs the ORIGINAL version which is 169 MB's... Somehow this does not ADD up... LOL
Thanks for poiting out 2977219-v2 2976897 is still the same released before and it's included in rollup 2975719
The M$ Aug 2014 "Patch / Update Tuesday" Windows 8.1 Updates <AND> it's many sequels remind me of the Comedy Skit Who's on First? by Abbott and Costello
it's not included in rollup 2975719, it added after 2014-08-14 to ms14-045 76897 files for 8.1: Dwmcore.dll 6.3.9600.17041 1,764,864 06-Mar-2014 06:09 x86 Microsoft-windows-desktopwindowmanager-compositor.ptxml Not applicable 4,069 21-Aug-2013 23:39 Not applicable D3d11.dll 6.3.9600.17041 1,779,800 06-Mar-2014 11:13 x86 Dxgi.dll 6.3.9600.17201 406,400 13-Jun-2014 00:10 x86 Cdd.dll 6.3.9600.17041 179,200 06-Mar-2014 10:34 x86 Dxgkrnl.sys 6.3.9600.17210 1,326,936 13-Jun-2014 00:10 x86 Dxgmms1.sys 6.3.9600.17041 321,880 06-Mar-2014 10:43 x86 Lddmcore.ptxml Not applicable 7,208 06-Mar-2014 01:37 Not For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2 Collapse this tableExpand this table File name File version File size Date Time Platform Dwmcore.dll 6.3.9600.17200 2,133,504 06-Jun-2014 11:34 x64 Microsoft-windows-desktopwindowmanager-compositor.ptxml Not applicable 4,069 22-Aug-2013 06:44 Not applicable D3d11.dll 6.3.9600.17041 2,141,912 06-Mar-2014 12:53 x64 Dxgi.dll 6.3.9600.17201 517,528 13-Jun-2014 01:15 x64 Cdd.dll 6.3.9600.17041 212,992 06-Mar-2014 12:39 x64 Dxgkrnl.sys 6.3.9600.17210 1,557,848 13-Jun-2014 01:14 x64 Dxgmms1.sys 6.3.9600.17041 379,224 06-Mar-2014 12:51 x64 Lddmcore.ptxml Not applicable 7,208 06-Mar-2014 01:36 Not applicable Dwmcore.dll 6.3.9600.17041 1,764,864 06-Mar-2014 06:09 x86 Microsoft-windows-desktopwindowmanager-compositor.ptxml Not applicable 4,069 21-Aug-2013 23:39 Not applicable D3d11.dll 6.3.9600.17041 1,779,800 06-Mar-2014 11:13 x86 Dxgi.dll 6.3.9600.17201 406,400 13-Jun-2014 00:10 x86
Parsix: thanks for checking on updates, but what Abbodi said is correct. KB2976897 contains ver .17210 of: windows-d..wmanager-compositor windows-directx-direct3d11 windows-directx-dxgi windows-lddmcore The same version of those components are contained in the Aug rollup (KB2975719). Not only that- KB2979265 contains .17224 version of those components, so KB2976897 is definitely not needed.
Hi, I have questions abou WinPE. Currently I have a VL image with Update 1 already in it. I'm using WHDownloader's list (Baseline, General, Security, Hotfix) of updates to keep it fresh. I have no problem integrating them into install.wim (1 index). I also integrate Baseline into boot.wim (both indexes), then ResetBase it. It's fine up to this point. However if I add patches from General (doesn't matter if I ResetBase again), Setup becomes corrupted (missing device driver...). So what's the deal with boot.wim? Why can't I add more patches after Baseline from folders General, Security or Hotfix? Or I shouldn't?
Why in the first place do you want to add updates to boot.wim? it's just for setup anyway, after you update boot.wim and while it's mounted, you need to copy at least setup.exe file from sources directory to sources directory in the ISO
I've thought that if an msu is applicable to WinPE, why not apply it? Anyho, I completely forgot that maybe setup.exe inconsistency may cause this, so your hint worked wonderfully, thanks!I only needed setup.exe, not much else is present in my image anyway
Thanks Alphawaves / abbodi1406 for fixing the following from my previous Post #1721 @Alphawaves; Is it feasible to have WHDownloader be able to identify and move OUTDATED M$ Updates that are UPDATED in addition to those that are Superseded and / or No longer Needed e.g. outlfltr2010-kb982726 for Office 2010-x86 ??? The problem is that when an older version of the same KB was previously downloaded and retained, WHDownloader doesn’t replace it with the NEWer version… Maybe WHDownloader can compare the DATEs and FILE size differences then MOVE the outdated version to the appropriate OLD folder… I realized this was occurring upon a careful comparison of downloaded M$ Updates with the current “Office2010” (2014/08/12) abbodi1406 list…
The Outlook Email filter update is one of those that retains it's KB number and doesn't get a new version in its file name, the same occurs in Office 2013. There could be some minor inconsistencies by comparing dates, but I guess if at least the month and year is compared it should be okay since they are a monthly update.