pbatard
commented
1 month ago - Please don't copy paste the log into a Word document. It's absolutely dreadful to try to work with it, and I had to update your post to make it a lot more palatable. You can just zip the log file and attach that if it's too long.
Could not apply image: [0x00000570] The file or directory is corrupted and unreadable.makes it pretty clear that theinstall.esdfrom your ISO image (which appears to be a custom Windows ISO, as any official ISO, such as the one that you can download through Rufus, would use aninstall.wim) is corrupted.- If the content of a
.esdis corrupted, Rufus will have no trouble creating an installer, since it copies the.esdwholesale. Contrary to what you assume, Rufus does not validate that a.esdor.wimcontains proper data when it creates a standard Windows installation media. In fact, the file could be all zeroes or complete garbage, and Rufus would not show any error. On the other hand, when creating a Windows To Go media, it needs to actually extract the content from the.esdso if that.esdis corrupted, you will see an error there, but not on regular media creation.
If you want to create a Windows To Go media, please make sure that you work with an official retail Windows ISO, such as the ones that Rufus can download (see below) and in case of any issue, make sure you validate the SHA-1 of that ISO (which you won't be able to do with an unofficial or MCT ISO).
As it appears to be a corrupted ISO problem, I will close this issue. But feel free to open a new one if you still see a problem when using an official retail ISO.
vince897
<!-- PLEASE READ THIS CAREFULLY:
You MUST read and complete the steps from the checklist below, by placing an x into each [ ] (so that it shows '[x]', NOT '[ x]' or '[x ]'), BEFORE clicking on 'Submit new issue'.
Failure to perform these steps, WHICH ARE ONLY THERE TO HELP YOU, will usually result in your issue being dismissed without notice.
If you are reporting an issue when trying to run Rufus, or when trying to boot a media created by Rufus, you MUST provide a log, period. Please do not assume that the developer(s) will be able to "guess" the specifics of your environment, what image you used, what type of media you used it with or the many many other critical parameters that the log provides data for. To investigate an issue, a log from Rufus is ALWAYS required.
If you still choose not to provide a log when reporting a problem, you agree that your issue will be closed without any further investigation.
YOU HAVE BEEN WARNED. -->
Checklist
<FULL LOG>below.Rufus version: x.y.z- I have NOT removed any part of it.Additionally (if applicable):
(✓)button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.I tried several copies of Rufus 4.5p and several copies of Windows 11 ISO andRufus failed to complete to obtain a Windows To Go file. To determine if my ISO file and Rufus were error free I ran Rufus for the Standard Windows Installation and it completed. I assume this verifies my ISO file and the version of Rufus 4.5p I am using.
The full Log is attached here.
Log