Because these Core(s) SKU are mostly OEM related, and updating it is up to them MS already instructed and supplied OEM's to install GA updates before delivering there devices
Thanks. But the Windows update ISOs are personalized, while the ISOs from MS Retail Store and on DVD are the same version for everyone. Some posted the ISO torrents on TPB, but where to get official hashes for Windows 8.1 Retail Core (productID.288401200) and Pro (productID.288401500) with integrated Rollup1?
I guess there is no way to get official hashes for Retail channel whatsoever, these are supposed to be sold in a store, physically, burned onto a disc. They are not supposed to be downloadable, thus there is no iso to be hashed.
MSDN Release is completely different from what you are downloading from the Store update. There won't be any kind of verification is required. Also i doubt that in MSDN there will be a new release for Windows 8.1 (multiple editions) though the time will tell the answer. Let's see
I need to download this: bg_windows_8_1_enterprise_n_x64_dvd_2971837.iso 3.4 GB bg_windows_8_1_enterprise_n_x86_dvd_2971840.iso 2.6 GB bg_windows_8_1_enterprise_x64_dvd_2971860.iso 3.5 GB bg_windows_8_1_enterprise_x86_dvd_2972254.iso 2.7 GB bg_windows_8_1_pro_n_vl_x64_dvd_2971927.iso 3.4 GB bg_windows_8_1_pro_n_vl_x86_dvd_2972704.iso 2.6 GB bg_windows_8_1_pro_vl_x64_dvd_2971899.iso 3.5 GB bg_windows_8_1_pro_vl_x86_dvd_2972619.iso 2.7 GB Who help me there?
French version 64bits fr_windows_8_1_pro_vl_x64_dvd_2971970.iso (3.62 Go) mega.co.nz/#!SN0lnbhB!aFhUAElBsAV1ivzlI3xIDxE6S9cdpb_jcwXmem9ibGQ
Done sfc /scannow & disabled AV. Still same error.. Pls help me to resolve.. C:\windows\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.