-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Corrupted Windows Image on Rebuilt Install ISO #89
Comments
There is a workaround for this. If the To do this, just extract
Place all the new swm files in a folder on the desktop named Then the following process for editing the ISO:
|
Sorry, I know you opened this a very long time ago and I never responded. I was finally able to get my hands on a copy of a Windows ISO, and I was able to add in an |
I'm no longer able to reproduce the issue. |
OK, thanks for the confirmation! I have put a bunch of fixes in since May, so hopefully one of those did it for you. Feel free to reopen if you see this again. |
I hope this is a different problem from #45 since that one is marked as fixed. I have run into a very similar problem. For a Windows ISO where I am trying to inject the
autounattend.xml
at the root of the Windows ISO: theinstall.wim
file is getting corrupted for some reason. I have opened both files in a hex editor and I can see that rather than being truncated, it appears that the first chunk of the file up to a certain offset is being repeated over and over up to the expected size in the new file.I extracted the file from the new ISO and in the hex editor, I picked out a few bytes at the end of the file:
Searching for those bytes, I find them repeated over and over:
Here is the code snippet that I'm using to make the new ISO:
SHA256 hash of the original ISO:
b842a801bf1dedf3acbfd909f91fb2a741eef20fda133daa1878e46a07ec9237
SHA256 of the original
install.wim
:6806be51af9783affe2710314328d158f6d4058033ba888216f6bef0766c84e7
SHA256 of the resulting
install.win
:74480bdab0309f683bfa6708fe2556c220855ae82ac1cbafba8f1f72aeba4361
The text was updated successfully, but these errors were encountered: