It used to be that the iso created by the tool was a known confirmed hash. I yesterday created 64-bit iso which came as: Code: CRC32: F2FDAC36 MD5: BD4E7D5C4A2CEB418E70D20B593193B8 SHA-1: 12911B0F8E25302FAF0211CEF9CE50C8D265C729 Google return nothing. But the iso worked fine for install Any ideas anybody? The original Code: X20-08980.img = en_windows_10_multiple_editions_x64_dvd_6846432.iso CRC32: B1A4699E MD5: 23E397A21A9E01F141C64B7E1260314A SHA-1: 60CCE9E9C6557335B4F7B18D02CFE2B438A8B3E2 would simply not install giving each time (USB clean install, iso upgrade) same idiotic error about temp folder not being allocated sebus
Thanks, then the original does not work (at least for me), will stick to the newly tool created sebus