Yes is same ESD where date on file create modified is 03/24/2017, but my friend confirm on email this from new version on Media Creation Tool.
Using Symantec SEP? If so, it'll only be patched later this month after 1703 GA, until then, it causes that error to pop constantly.
What do you mean? They work here but my internet speed is not that fast otherwise i would compare them myself
Adguard's links also work Compared the iso's: Code: --------------------------- Checksum information --------------------------- Name: Windows10_InsiderPreview_Client_x64_en-us_15063.iso Size: 4334315520 bytes (4133 MB) CRC32: 7ACC10A5 CRC64: 99212C5562C870F0 SHA256: B842A801BF1DEDF3ACBFD909F91FB2A741EEF20FDA133DAA1878E46A07EC9237 SHA1: CE8005A659E8DF7FE9B080352CB1C313C3E9ADCE BLAKE2sp: 81A25AE345635C793DF51FC7E20C0EEB289F12D03584ACFFB73F237915229770 --------------------------- OK --------------------------- Code: --------------------------- Checksum information --------------------------- Name: Win10_1703_English_x64.iso Size: 4334315520 bytes (4133 MB) CRC32: 7ACC10A5 CRC64: 99212C5562C870F0 SHA256: B842A801BF1DEDF3ACBFD909F91FB2A741EEF20FDA133DAA1878E46A07EC9237 SHA1: CE8005A659E8DF7FE9B080352CB1C313C3E9ADCE BLAKE2sp: 81A25AE345635C793DF51FC7E20C0EEB289F12D03584ACFFB73F237915229770 --------------------------- OK --------------------------- Both ISO's are exactly the same, as expected