pbatard
commented
1 year ago
Extracting: D
Your log is truncated, so we're missing critical data to try to identify the issue. Especially, I'm not seeing any error message.
For the record, Search for conflicting processes was interrupted due to timeout is NOT an error. Rufus runs a search for potential conflicting process is parallels during its operations, but because we don't want to make the user wait on that process forever, there is a 10 seconds timeout. So it is perfectly normal to see this notice, which does not mean anything except that, during the 10 seconds it was searching for conflicting processed, Rufus was not able to identify any.
Could not get Disk Extents: [0x00000001] Incorrect function.
This is more interesting, though mostly a benign warning if you were able to continue.
Again, I am not seeing any errors that require addressing here.
Please bear in mind that, since the log is for me, the developer, I try to report as much information as possible (including perfectly normal timeouts so that I can know if it's possible that there might still have been a conflicting process, that wasn't reported because of the timeout), as well as what might be slightly out of the ordinary. However, you should be VERY WEARY of interpreting the log yourself and jumping to the erroneous conclusion that benign messages are errors. For instance your last message is also a mere notice to indicate that, because the file systems that can be used for the flash drive cannot use symbolic links, Rufus will of course not be able to replicate them, and to alert users to the fact that, if they experience an issue during boot, it could potentially be cause by this. But again, this is not an error.
All in all, what I seeing here is what I would qualify as an hypochondriac report, i.e., you are looking for issues and errors, that you are trying to insist need "fixing" when there are absolutely none, and all of these messages are 100% benign.
The only test that matters are:
- Was Rufus able to create the USB to the end? (i.e. progress bar went to 100% and wasn't interrupted with an explicit user message)?
- Can you boot the USB and does it appear to work properly.
Unless either of these happens, which doesn't seem to be the case, then none of the messages you've picked, and that you wrongly assume are error reports, matter in the slightest.
As such, I will close this issue.
PS, which regards to your "not everyone has multiple computers BTW" remark, I know, that's why the checklist says: Additionally (if applicable):, which means that, if it wasn't applicable, you should just have let it unchecked.
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