I guess it can be confusing if you don't know how we're getting our ISO files. We've gotten random mega and magnet links from all over the web for our own language. We don't have a magical source of iso files, except maybe PaulDesmond Follow him around like a puppy dog and see if other people have asked him for things before nagging him though.
Something I don't like in Windows 8.1 Update : (not ISO) When I try to "clean disk" and the cleaner scan files then it stop when it came to "Windows Updates" and the processor is warming. It take couple minutes until everything ok.
They integrated an obsolete hotfix removal into that and it's going around scanning the files to see if any are superseded.
Out of curiosity i integrated the Windows8.1-KB2934018-x64 into Pro Index of Win 8.1 with Update and got this: Code: ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ IND MODIFIED LP ARC BUILD EDITION ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ [1] 09.04.2014 US x64 6.3.9600.17056 Windows 8.1 Pro [2] 18.03.2014 US x64 6.3.9600.17031 Windows 8.1
Don't confuse things, installed Windows still shows 17041 here, only the 'ServicePack' build string in the WIM Info changed.
Some files have the build 17056. but the registry value BuildLabEx has build 17041. In HAL (msinfo32) the build is 17031. So the main build remain 17031.
Store-Upgrade editions has the same name tag Code: 9600.17050.winblue_refresh.140317-1640_x86fre_client_coresinglelanguage_en-us-ir3_csla_x86frer_en-us_esd_8c1a97328023e9717962b81f8b2f1f73ae8a95df.esd however, after downloading, decrypting, applying the esd image, it has exactly the same KB's updates as the MSDN updated iso i.e. Spoiler Code: Package_for_KB2919355~31bf3856ad364e35~x86~~6.3.1.14 | Installed | Update | 2014/3/18 07:58 AM Package_for_KB2919442~31bf3856ad364e35~x86~~6.3.1.8 | Installed | Update | 2014/3/18 07:44 AM Package_for_KB2932046~31bf3856ad364e35~x86~~6.3.1.5 | Installed | Feature Pack | 2014/3/18 07:58 AM Package_for_KB2937220~31bf3856ad364e35~x86~~6.3.1.0 | Installed | Update | 2014/3/18 07:58 AM Package_for_KB2937592~31bf3856ad364e35~x86~~6.3.1.0 | Installed | Feature Pack | 2014/3/18 07:58 AM Package_for_KB2938439~31bf3856ad364e35~x86~~6.3.1.0 | Installed | Feature Pack | 2014/3/18 07:58 AM Package_for_KB2938772~31bf3856ad364e35~x86~~6.3.1.0 | Installed | Update | 2014/3/18 07:58 AM Package_for_KB2939471~31bf3856ad364e35~x86~~6.3.1.0 | Installed | Update | 2014/3/18 07:58 AM Package_for_KB2949621~31bf3856ad364e35~x86~~6.3.2.0 | Installed | Hotfix | 2014/3/18 07:58 AM i cannot even find a single manifest/component that has 9600.17050 version, so i wonder what does .17050 tag represent exactly? maybe they finds it a nice number Bottom line for some "confused" users, those refreshed Evaluation ISOs, Store ESDs are the same as MSDN's ISOs
I did the update (BAV0) last month and notice today that Windows Update shows KB2919355 as available but unchecked even it is marked as important. The size is only around 120MB. I went ahead with the re-update and all seems fine so far...
Anyone got this? Thanks in advance. Code: File Name: bg_windows_8.1_professional_vl_with_update_x86_dvd_4048624.iso Languages: Bulgarian SHA1:EA1A5218ACD3E82C5580FA04C1F69CE6B2925310 File Name: bg_windows_8.1_professional_vl_with_update_x64_dvd_4050280.iso Languages: Bulgarian SHA1:427E1775F25DA4A62358401F80E06E8B47A0B295 File Name: bg_windows_8.1_enterprise_with_update_x86_dvd_4050262.iso Languages: Bulgarian SHA1:4F269AB5152E3A2FDC0E77BDFE84721BEE6CB087