Closed cturner6907 closed 10 years ago
Oops. Fixed in 1.4.5.248 (which I just uploaded to replace the old 1.4.5).
Really sorry about this. Please download 1.4.5 again, from http://rufus.akeo.ie/downloads/. It will fix the issue.
Hopefully not too many people will have downloaded that old 1.4.5 before it was replaced (but they should get an update notification to upgrade from 1.4.5.247 to 1.4.5.258 if they did).
Thanks for reporting that issue quickly.
perfect thanks! will give it a shot and let you know
248 works, thanks!
Hi guys.
I'm getting this error using both 1.4.5.428 and 1.4.6.440. My flashdrive is Kingston DataTraveler G3 16GB. The error occurs in both USB 2.0 and USB 3.0 ports.
I'm wanting to install Windows 8.1 Enterprise onto my Samsung 256GB SSD on ASUS F2A85-V Pro UEFI capable mainboard using AMD A10-6800K Black Edition processor.
What needs to be my next step to get this ISO onto my flashdrive?
Thanks. Cole
Can you please provide a full log? Also, are you using any kind of security solutions such as the ones mentioned here?
Hi Pete.
Sadly, I no longer have any of that information. After I got my USB to copy the ISO in UEFI using 1.4.6.440, I then cleared the partitions, formatted it and continued with the UEFI installation. I wish I would have thought to get that log for you, but I was immersed in research on getting my ISO ready to do a full wipe installation. :(
What I can tell you is that when I plugged the DataTraveler G3 into either a USB 2.0 or 3.0 Rufus 1.4.6.440 recognized it in Device. Next I selected MBR partition scheme for UEFI computer, File System to FAT32 and the Cluster size was 4096 bytes.
The check-boxes were:
SW_DVD5_SA_Win_Ent_8.1_64BIT_English_MLF_X18-96759.ISO
After clicking Start, a window popped up like it was going to do its thing. Some 20 or 30 seconds later an error appeared, and the flashdrive was unusable or even visible to the OS, all information about it was missing. I was able to recover the device following the commands shown in my post to eightforums.com.
Wish I could help more.
Cole
Sadly, I no longer have any of that information
What prevents you from trying to recreate your USB using Rufus as you did before? Do you no longer have access to that USB drive?
Also, I believe that your issue is the same as the one from #312. Considering that this one is officially closed, it may be best if we continue the discussion in #312.
Good day, Pete.
This is a reasonable request, and one I would make of a user were I still actively a hardware engineer or tech support.
For your request, I will do what I can today to see if I can replicate the issue, and keep detailed notes plus the log from your app in case it happens again.
I’d like to add that the DataTraveler G3 had been used for multiple jobs on many computers, most of which often had viruses that kept me constantly wiping, formatting and rebuilding it. The fact that I got it to cleanly wipe using the command-line so I could then use your rufus 1.4.6 won’t exactly replicate the original issue.
With that said, I’m now curious to see if I can replicate this to help further refining your highly useful application.
Also, I looked at #312 and feel it is quite different from my experience, but if you prefer me to add to this ticket, I will begin there after I perform my testing.
Regards,
-- Cole
(version 1.4.7.455)
Very interesting, I got the same message too. No matter what I tried.
In the end, I found a solution by using a different USB port! after you use RUFUS once, you will get the error message again, just put back to the first USB you tried then it should work again.. so the key is that.. .try different USB port first when you get that message.
hope this will help someone.
thanks
Using version 1.4.7.455 (latest at the time of post) and am getting the same errors previously posted. Here is the log:
Format operation started
Requesting disk access...
Caution: Opened drive \\.\PHYSICALDRIVE2 for write access
Will use 'F:' as volume mountpoint
I/O boundary checks disabled
Could not get exclusive access to device \\?\Volume{e5c8db2c-cf0d-11e3-8ac8-0026185429d3}: [0x00000005] Access is denied.
Could not lock volume
Re-mounted volume as 'F:' after error
Found USB device 'SanDisk Cruzer Glide USB Device' (0781:5575)
Found USB device 'Seagate Backup+ Desk USB Device' (0BC2:A0A4)
Device eliminated because it was detected as an USB Hard Drive (score 33 > 0)
If this device is not an USB Hard Drive, please e-mail the author of this application
NOTE: You can enable the listing of USB Hard Drives in 'Advanced Options' (after clicking the white triangle)
1 device found
Disk type: Fixed, Sector Size: 512 bytes
Cylinders: 15567, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x010288BB
Drive has an unknown Master Boot Record
Partition 1:
Type: NTFS (0x07)
Size: 119.2 GB (128043711488 bytes)
Start Sector: 2, Boot: Yes, Recognized: Yes
Found USB device 'SanDisk Cruzer Glide USB Device' (0781:5575)
Found USB device 'Seagate Backup+ Desk USB Device' (0BC2:A0A4)
Device eliminated because it was detected as an USB Hard Drive (score 33 > 0)
If this device is not an USB Hard Drive, please e-mail the author of this application
NOTE: You can enable the listing of USB Hard Drives in 'Advanced Options' (after clicking the white triangle)
1 device found
Disk type: Fixed, Sector Size: 512 bytes
Cylinders: 15567, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x010288BB
Drive has an unknown Master Boot Record
Partition 1:
Type: NTFS (0x07)
Size: 119.2 GB (128043711488 bytes)
Start Sector: 2, Boot: Yes, Recognized: Yes
Tried bobyang3 work around but to no avail.
If it fails that early, it looks like you are using some software that is keeping a lock on the target drive and preventing full access for Rufus. Are you using anything from this list?
If not, you will either have to figure out what software might be keeping a lock on your drive, or wait until I implement the feature requested in #312 (which, if not too heavy in terms of code, will probably be take months at best).
In reply to Bobyang3:
I was having the same issue with version 1.4.9.506 on 2 different PCs running Windows 7 x64, when ever I tried to Format a 32G Sandisk or a 4G Imation USB stick with an XP iso I would get this error: "Error: Could not open media. It may be in use by another process. Please re-plug the media and try again."
So I tried moving the USB stick to another port after the error, but found by accident that if you pull the USB stick out just as Rufus starts scanning the USB stick < 15s (before it brings up the error), and then plug it back in to the same USB port - first it spits out an error that the media is missing, but just click OK and then Rufus starts to Format the USB stick.
pbatard: I do not have any of that software from your list on either PC as well. However I do suspect there is software on there that is blocking the creation of autorun.ini files.
I had the " Error: Could not open media. It may be in use by another process. Please re-plug the media and try again." problem too. I used several versins of rufus but none worked. Then i used the 1.4.5 versions as suggested here. It also started to work but then suddenly it stopped and showed a message but i forgot the message. I have saved the log though. Here is the log :
Rufus version: 1.4.5.428
Syslinux versions: 4.07, 5.10
Windows version: Windows 7 SP1 32 bit
Locale ID: 0x0409
Found USB device 'UFD 3.0 Silicon-Power16G USB Device' (13FE:5500)
1 device found
Sector Size: 512 bytes
Cylinders: 1886, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x00000001
Drive has an unknown Master Boot Record
Partition 1:
Type: Small FAT16 (0x04)
Size: 14.4 GB (15514730496 bytes)
Start Sector: 0, Boot: No, Recognized: Yes
0 devices found
Found USB device 'UFD 3.0 Silicon-Power16G USB Device' (13FE:5500)
1 device found
Sector Size: 512 bytes
Cylinders: 1886, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x00000001
Drive has an unknown Master Boot Record
Partition 1:
Type: Small FAT16 (0x04)
Size: 14.4 GB (15514730496 bytes)
Start Sector: 0, Boot: No, Recognized: Yes
Scanning image...
Disc image is an UDF image
ISO label: 'J_CCSA_X64FRE_EN-US_DV5'
Size: 4421363712 bytes
Has a >64 chars filename: No
Has Symlinks: No
Has a >4GB file: No
ReactOS: No
Uses EFI: Yes
Uses Bootmgr: Yes
Uses WinPE: No
Uses isolinux: No
Using ISO: Win10_1511_1_English_x64.iso
Format operation started
Requesting disk access...
Caution: Opened drive \\.\PHYSICALDRIVE1 for write access
No drive letter was assigned...
Will use 'J:' as volume mountpoint
I/O boundary checks disabled
Analyzing existing boot records...
Drive has an unknown Master Boot Record
Drive has an unknown partition boot record
Deleting partitions...
Closing existing volume...
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Partitioning (MBR)...
Waiting for logical drive to reappear...
Formatting (NTFS)...
Using cluster size: 4096 bytes
Creating file system: Task 1/12 completed
Creating file system: Task 2/12 completed
Creating file system: Task 3/12 completed
Creating file system: Task 4/12 completed
Creating file system: Task 5/12 completed
Creating file system: Task 6/12 completed
Creating file system: Task 7/12 completed
Creating file system: Task 8/12 completed
Creating file system: Task 9/12 completed
Creating file system: Task 10/12 completed
Creating file system: Task 11/12 completed
Creating file system: Task 12/12 completed
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Set bootable USB partition as 0x80
Using Rufus MBR
Found volume GUID \\?\Volume{cb5c22c9-766a-11e5-8838-001ffb1991fd}\
Caution: Opened drive \\?\Volume{cb5c22c9-766a-11e5-8838-001ffb1991fd} for write access
Writing partition boot record...
Using Standard NTFS partition boot record
Confirmed new volume has an NTFS boot sector
Successfully remounted Volume{cb5c22c9-766a-11e5-8838-001ffb1991fd}\ on J:\
Copying ISO files...
Extracting files...
Disc image is an UDF image
Extracting: J:\autorun.inf (128 bytes)
Extracting: J:\boot\bcd (16.0 KB)
Extracting: J:\boot\boot.sdi (3.0 MB)
Extracting: J:\boot\bootfix.bin (1.0 KB)
Extracting: J:\boot\bootsect.exe (109.3 KB)
Extracting: J:\boot\en-us\bootsect.exe.mui (16.5 KB)
Error reading UDF file \boot\en-us\bootsect.exe.mui
Found USB device 'UFD 3.0 Silicon-Power16G USB Device' (13FE:5500)
1 device found
Sector Size: 512 bytes
Cylinders: 1886, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x0164CCF6
Drive has a Rufus Master Boot Record
Partition 1:
Type: NTFS (0x07)
Size: 14.4 GB (15513681920 bytes)
Start Sector: 2048, Boot: Yes, Recognized: Yes
Format operation started
Requesting disk access...
Caution: Opened drive \\.\PHYSICALDRIVE1 for write access
Will use 'J:' as volume mountpoint
I/O boundary checks disabled
Could not get exclusive access to device \\?\Volume{cb5c22c9-766a-11e5-8838-001ffb1991fd}: [0x00000005] Access is denied.
Could not lock volume
Re-mounted volume as 'J:' after error
Found USB device 'UFD 3.0 Silicon-Power16G USB Device' (13FE:5500)
1 device found
Sector Size: 512 bytes
Cylinders: 1886, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x0164CCF6
Drive has a Rufus Master Boot Record
Partition 1:
Type: NTFS (0x07)
Size: 14.4 GB (15513681920 bytes)
Start Sector: 2048, Boot: Yes, Recognized: Yes
Found USB device 'UFD 3.0 Silicon-Power16G USB Device' (13FE:5500)
1 device found
Sector Size: 512 bytes
Cylinders: 1886, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x0164CCF6
Drive has a Rufus Master Boot Record
Partition 1:
Type: NTFS (0x07)
Size: 14.4 GB (15513681920 bytes)
Start Sector: 2048, Boot: Yes, Recognized: Yes
Scanning image...
Disc image is an UDF image
ISO label: 'J_CCSA_X64FRE_EN-US_DV5'
Size: 4421363712 bytes
Has a >64 chars filename: No
Has Symlinks: No
Has a >4GB file: No
ReactOS: No
Uses EFI: Yes
Uses Bootmgr: Yes
Uses WinPE: No
Uses isolinux: No
Using ISO: Win10_1511_1_English_x64.iso
Then i again tried but it started to show the first error again. What can i do now ?
I checked for the SHA1 of the iso in rufus. Here is what i got in the result : MD5 : d51601aa9a9d3c5656fe1ac008d4d0e6 SHA1 : cf3011728abe3a17d4ff9083b053c9a844593bd9
The core of the issue is that you have another application that is blocking access to your USB. There isn't much I can do yo help you out with that unless you identify it. You may also try the Alt-, cheat mode, to see if that helps, but that's about the best I can suggest. And no, the fact that you once got it working with 1.4.x is unlikely to be significant. If the application that's blocking access decided to relinquish it for whatever reason, then you may find that any version of Rufus works, only to be denied access later on, regardless of the version.
So, again, it is up to you to identify which application is blocking access, and disable it.
Oh, and for the record, SHA1 cf3011728abe3a17d4ff9083b053c9a844593bd9
does not appear to match any official Microsoft Windows 10 ISO.
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.
I'm getting this error when trying to mount HBCD iso onto a usb stick:
Error: Could not open media. It may be in use by another process. Please re-plug the media and try again.
I've tried a few different sticks. Formatted the sticks using a variety of methods: diskpart fat32, diskpart ntfs etc. I've verified nothing is running or open from the sticks when running rufus. Using Rufus 1.4.5.427 on a win 8 x64 machine.
from the log, the error comes at this point:
here is the log: