USB Installer needs hash checks before finishing to avoid corruption


1 comment

  • Forrest Smith

    Hi Talisha,


    What computers are you installing to?


    We actually do run verification after we image a USB, but there are a lot of computers out there with BIOS bugs that can corrupt a USB image during the live-boot process (see notes here about the Asus 1005HA, for example). Maybe something like that is the issue?


    You could test your theory (that the USB maker is causing the issues) by skipping the automated USB maker tool and using our older "Manual" steps like these. The Chrome Recovery Utility definitely does a verify step and is maintained by Google, so if you remake your USB using that and, after a while, see corruption then you can assume it's something besides the USB-maker.

Please sign in to leave a comment.