pbatard
commented
7 months ago Thanks for the report and especially the log from DebugView.
What I am seeing from your log seems to indicate that either your image is corrupted or your Windows installation is preventing Rufus to access some data that it needs to function properly:
00000085 7.73979521 [8832] Could not access image: [0x0000000D] The data is invalid.
00000086 7.74172258 [8832] Could not acquire WIM index The first thing I would do then is post the SHA-256 of the image you are using here so that it can be validated, because, while you say that "The file has been downloaded from Microsoft's official website (...). The image does not seem tampered" it is always possible for downloads to become corrupted, so I would really like you to perform the operation indicated in the checklist at:
- [ ] If using an image, I clicked on the
(✓)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.
Also, you are stating that the application simply closes rather than crashes? Do you get any prompt to send data to Microsoft when that happens (as you would with an application crash)? Because if you do, and since it's the AppStore version, I can ultimately access that data so I might be able to have a closer look at what really happens.
I would also suggest, since you are using the AppStore version, to try with the standalone Rufus application, which you can download from https://rufus.ie to see if you experience the same issue. For the record, I tested Rufus by force triggering the Could not access image / Could not acquire WIM index errors, but I was still able to proceed successfully without a crash or the application closing, so this looks like an environmental/image issue rather than a Rufus bug.
abhi-deshpande
github-actions[bot]
<!-- 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.Issue description