Cannot mount GUID volume #1016
Comments
|
Thanks for the report. You're actually the first person I can remember who reports that they are using Obviously then, I need to review the assumption that So now, we can explain the behaviour: Means Rufus was not able to detect the drive letter assigned to your drive (because it only checks drive letters starting at Means that. because was not able to detect a drive letter assigned (because it it didn't pick I think I have a good idea of how to fix these 2 issues. |
|
I'm pretty sure the problem is now fixed, so this issue will be automatically closed as I push the next commit. |
|
Lol for real….i always thought that window would assign double letter after the singles w was used up, but that’s not the case due to I could not mount 4 virtual drives with poweriso, no more letters I guess, everything worked fine after I drop 2 of the virtual drives and allowed rufus to mount on Z, windows assigned drive A to the usb flash drive.
Yea I hate win 10 it sure is pretty but it has wreaked havoc on my network, I spent weeks researching it and fixing win 10 for MS and they didn’t pay me crap….lol I sent them a bill for 23567$ my time spent fixing it. So I was goning back to win7 and dual booting linux Ubuntu, trying to get away from MS completely. As for Rufus it worked fine loading my ntlite slipstream win7, booted perfect thru usb boot and loaded win7
Dl test rufus will check it out soon or later…lol…”TIME IF ONLY I HAD MORE”
Thank you
sdled
|
|
Still face the issue!!!! v. 3.14.1430 |
|
Are you using If not, then this is not the same issue and you shouldn't piggy back on a closed issue, that was opened for a completely different problem, as it is impossible for me to help you since the problem described here was indeed fixed, and of course I can't "guess" what your actual issue is. At the very least you need to provide a full log from Rufus. |
|
@pbatard I tried the tool on win 7. after several attempts with errors iso on flash was created. May be my win 7 issue. |
|
Again, can't do anything unless you provide a full log with the error. |
|
I did not copy the error log. |
|
You can always retry what you were doing. Also, it seems you were still getting the error even after I explicitly asked you for the log, so I don't understand why you didn't provide one. Bottom line: If you can't provide a log that shows the error then I can't do anything for you on your issue. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
Checklist
Logbutton in Rufus and copy/pasted the log into the line that says<FULL LOG>below.Rufus version: x.y.z- I have NOT removed any part of it.Additionally (if applicable):
#button (at the bottom of the Rufus interface), 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
as per description in Cannot mount GUID volume #476 the problem in my cannot mount condition was due to power iso virtual drive was using drive letter assigned to usb device by rufus...eg... usb drive A changed to drive Z by rufus at which time drive Z was assigned by power iso virtual drive...thus by changing poweriso virtual drive to 2 drives, instead of 4 drives, opened up the z drive for rufus and all is well, but why would rufus change the mount location of usb on drive A to drive Z
Log
The text was updated successfully, but these errors were encountered: