Skip to content
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

Cannot mount GUID volume #1351

Closed
MrCoconut opened this issue Jul 30, 2019 · 26 comments

Comments

@MrCoconut
Copy link

commented Jul 30, 2019

Checklist

  • I looked at https://github.com/pbatard/rufus/wiki/FAQ to see if my question has already been answered. And there is no specific question regarding "GUID" things.
  • I performed a search in the issue tracker for similar issues using keywords relevant to my problem, such as the error message I got from the log. Yeah, but issue #476 ended with "I think I have an idea what's going on. Will add a possible fix for this with the 2.3 release." And I'm using Rufus 3.6.
  • I clicked the 'Log' button or pressed Ctrl-L in Rufus, and copy/pasted the log into the line that says <FULL LOG> below. Yeah, please see it.
  • The log I am copying is the FULL log, starting with the line Rufus version: x.y.z - I have NOT removed any part of it.

Additionally (if applicable):

  • I ran a bad blocks check, by clicking Show advanced format options then Check device for bad blocks, and confirmed that my USB is not defective.
  • I also tried one or more of the following:
    • Using a different USB drive. Rufus run successfully on my USB drive with the same setting and Windows ISO, but it's far to slow to run a Windows To Go. The performance was unacceptable.
    • Plugging the USB into a different port.
    • Running Rufus on a different computer.
  • 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.

Issue description

Hi, all. I continuously experienced error message "cannot mount GUID volume" everytime when trying to construct a Windows To Go drive on my SSD. It appers right after status "writing MBR". I successfully made a WTG on my USB drive prior to this so I don't think the ISO is to be blame and I run a bad block check but the SSD was alright. I tried several times with the SSD repluged into another port, Windows virtual machine restarted and the error message never disappers.

Log

Rufus x86 v3.6.1551
Windows version: Windows 10 64-bit (Build 18362)
Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06
Grub versions: 0.4.6a, 2.04
System locale ID: 0x0804 (zh-CN)
Will use default UI locale 0x0804
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'zh-CN'
Found USB 3.0 device 'ASMT 2115 USB Device' (174C:1153)
Device eliminated because it was detected as a Hard Drive (score 6 > 0)
If this device is not a Hard Drive, please e-mail the author of this application
NOTE: You can enable the listing of Hard Drives under 'advanced drive properties'
Found non-USB removable device 'VMware Virtual SATA Hard Drive' => Eliminated
0 devices found
Found USB 3.0 device 'ASMT 2115 USB Device' (174C:1153)
Found non-USB removable device 'VMware Virtual SATA Hard Drive' => Eliminated
1 device found
Disk type: FIXED, Disk size: 512 GB, Sector size: 512 bytes
Cylinders: 60801, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 3
Disk GUID: {3E2828D5-F849-456A-BC8A-ADE2D0B4390F}
Max parts: 128, Start Offset: 17408, Usable = 500107827712 bytes
Partition 1:
  Type: {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}
  Name: 'EFI System Partition'
  ID: {3396DF70-B553-4A11-833E-F5324060A9D5}
  Size: 300 MB (314592768 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Partition 2:
  Type: {E3C9E316-0B5C-4DB8-817D-F92DF00215AE}
  Name: 'Microsoft Reserved Partition'
  ID: {346F1B95-4C19-4CBD-A48A-934855E87109}
  Size: 128 MB (134217728 bytes)
  Start Sector: 616487, Attributes: 0x0000000000000000
Partition 3:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Main Data Partition'
  ID: {02CCB867-4F44-4934-99B5-4C3EB82AF735}
  Size: 465.3 GB (499657986048 bytes)
  Start Sector: 878631, Attributes: 0x0000000000000000
Scanning image...
ISO analysis:
  Image is an UDF image
Disk image analysis:
  Image does not have an x86 Master Boot Record
ISO label: 'CCCOMA_X64FRE_ZH-CN_DV9'
  Size: 4.6 GB (Projected)
  Uses: EFI
  Uses: Bootmgr (BIOS and UEFI)
  Uses: Install.wim (version 0.13.1)
Using image: Win10_1903_V1_Chinese(Simplified)_x64.iso (4.6 GB)
WIM extraction method(s) supported: 7-Zip, wimgapi.dll
WIM apply method supported: wimgapi.dll
Opening: \\.\CDROM1/sources/install.wim:[0] (API)
Extracting: C:\Users\yezid\AppData\Local\Temp\Ruf1B2B.tmp (From [1].xml)
Closing: \\.\CDROM1/sources/install.wim
Will use 'Windows 10 专业版' (Build: 18362, Index 4) for Windows To Go

Format operation started
Requesting disk access...
Will use 'E:' as volume mountpoint
Deleting partitions...
Deleting ALL partition(s) from disk '\\?\PhysicalDrive1':
● Partition 1 (offset: 1048576, size: 300 MB)
● Partition 2 (offset: 315641344, size: 128 MB)
● Partition 3 (offset: 449859072, size: 465.3 GB)
Opened \\.\PhysicalDrive1 for exclusive write access
No logical drive found (unpartitioned?)
Drive does not appear to be partitioned
Analyzing existing boot records...
Drive has a Zeroed Master Boot Record
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Deleting partitions...
Partitioning (GPT)...
● Creating EFI System Partition Partition (offset: 1048576, size: 300 MB)
● Creating Microsoft Reserved Partition Partition (offset: 315641344, size: 128 MB)
● Creating Main Data Partition (offset: 449859072, size: 465.3 GB)
Waiting for logical drive to reappear...
Closed Windows format prompt
Timeout while waiting for logical drive
Logical drive was not found!
Formatting (NTFS)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Writing Master Boot Record...
Using Rufus protective MBR
Found volume \\?\GLOBALROOT\Device\HarddiskVolume9\
Could not remount \\?\GLOBALROOT\Device\HarddiskVolume9\ as E: [0x00000012] 没有更多文件。
\\?\Volume{7df4b5a6-0659-4163-b585-bc5c71d47127}\ is already mounted as E:
Re-mounted volume as E: after error

Found USB 3.0 device 'ASMT 2115 USB Device' (174C:1153)
Found non-USB removable device 'VMware Virtual SATA Hard Drive' => Eliminated
1 device found
Disk type: FIXED, Disk size: 512 GB, Sector size: 512 bytes
Cylinders: 60801, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 3
Disk GUID: {81E6E4BB-BDDE-4DBE-89C9-8117F5FB92B2}
Max parts: 128, Start Offset: 17408, Usable = 500107827712 bytes
Partition 1:
  Type: {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}
  Name: 'EFI System Partition'
  ID: {7354A864-CC76-427C-A694-3F87146E6AD4}
  Size: 300 MB (314592768 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Partition 2:
  Type: {E3C9E316-0B5C-4DB8-817D-F92DF00215AE}
  Name: 'Microsoft Reserved Partition'
  ID: {52D00507-CFBE-41B5-B8B9-B1164FEB3754}
  Size: 128 MB (134217728 bytes)
  Start Sector: 616487, Attributes: 0x0000000000000000
Partition 3:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Main Data Partition'
  ID: {7DF4B5A6-0659-4163-B585-BC5C71D47127}
  Size: 465.3 GB (499657986048 bytes)
  Start Sector: 878631, Attributes: 0x0000000000000000
@MrCoconut

This comment has been minimized.

Copy link
Author

commented Jul 30, 2019

Translation:没有更多文件。-> No more files.

@Heinzable

This comment has been minimized.

Copy link

commented Jul 30, 2019

Indeed, same issue.
Previous version (3.5) works fine.
I also noticed that it says "Improve(?) Windows To Go support by following Microsoft's recommended partition order" in the changelog.

@pbatard

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2019

Please run more tests with 3.5. Be mindful that a single test with 3.5 is not enough to determine if there was a regression.

Also, did any of you enable VDS (Alt-V) by any chance? If so please disable it an try again, as this feature is very experimental.

@pbatard

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2019

Also, I see that you are getting:

Timeout while waiting for logical drive
Logical drive was not found!

This is not usual and indicates that Windows is interfering with the normal flow of operation. When that happens, you may want to cycle the USB port with Alt-C as this issue tends to indicate that Windows is trying to use an old cached partition table, instead of the actual one, and the only way I have found to force Windows to forget the old table is through port cycling (I have tried many, many API calls that Microsoft say are supposed to refresh the layout, which is actually part of the reason why there is a new VDS mode in Rufus, but none actually work)...

@Heinzable

This comment has been minimized.

Copy link

commented Jul 30, 2019

I've tested v3.3 - 3.5, all of which worked immediately. Tried it with v3.6 multiple times (and the usual stuff such as rebooting, trying different USB ports, formating the drive in Disk Management, even deleting the partition table, low level format) but it never got past that point.

Always said
Timeout while waiting for logical drive Logical drive was not found!

And no, I didn't hit ALT-V.
Can you elaborate on the ALT-C fix? When should it be pressed?

@Heinzable

This comment has been minimized.

Copy link

commented Jul 30, 2019

Just tried it with hitting ALT-C before pressing "Start". Worked twice in a row.
Thank you!

@frh

This comment has been minimized.

Copy link

commented Jul 30, 2019

I'm experiencing what appears to be the same issue, although ALT-C doesn't fix it. My log also has the same "Timeout while waiting for logical drive" and "Logical drive was not found!" messages. Using Rufus 3.5 instead of 3.6 works. This is a SATA SSD in a Ugreen USB enclosure. Rufus is running in a Windows 10 VM on KVM using USB passthrough for the target disk. Let me know if I can help by testing in any way.

@pbatard

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2019

I see a lot of people using VM's there... Please be mindful that I can only support real hardware, as there is no telling how virtualization can interfere with either of Rufus or Windows behaviour. For instance I strongly suspect that the reason Alt-C doesn't work on a VM is because no actual USB port reset takes place (it's probably filtered by the VM application). In that case, please try to physically unplug and replug the drive.

@frh

This comment has been minimized.

Copy link

commented Jul 30, 2019

I can understand if you reckon that the VM aspect will make this problem out of scope. I very much appreciate Rufus nonetheless.
I tried physically replugging the drive, but it made no difference. It consistently works every time with 3.5 and fails with 3.6 with everything I've tried so far on my setup.

@MrCoconut

This comment has been minimized.

Copy link
Author

commented Jul 31, 2019

Sincerely thank everyone in this thread. It turned out that rolling back to v3.5 was the solution for me. I did not accidentally turn on VHS, and Alt + C did not fix the problem. _(:з」∠)_
I know that running such a system-mode intensive task in a VMWare virtual machine is not a good idea, but that's the only viable option for me anyway... Thank you @pbatard for your hardwork and quick response.

@MrCoconut MrCoconut closed this Jul 31, 2019

@pbatard pbatard referenced this issue Aug 1, 2019
7 of 10 tasks complete
@ckrzen

This comment has been minimized.

Copy link

commented Aug 1, 2019

Just wanted to add that I hit this just now and the only solution, after trying all mentioned methods above, was to revert to 3.5.

Let me know if I can add any debug logs for things not yet tried.

@pbatard

This comment has been minimized.

Copy link
Owner

commented Aug 1, 2019

(Full) logs are ALWAYS welcome. I'm afraid a "me too" without a log doesn't tell me much. Also please indicate if you are running Rufus on real hardware or on a VM.

@frh

This comment has been minimized.

Copy link

commented Aug 1, 2019

Here's the log from my Windows To Go attempt in 3.6, running in a KVM VM with USB passthrough:

Rufus x86 v3.6.1551 (Portable)
Windows version: Windows 10 64-bit (Build 17763)
Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06
Grub versions: 0.4.6a, 2.04
System locale ID: 0x0409 (en-US)
Will use default UI locale 0x0409
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'en-US'
Notice: The ISO download feature has been deactivated because 'Check for updates' is disabled in your settings.
Found UAS (USB 2.0) device 'Samsung SSD 840 EVO 120G SCSI Disk Device' (174C:55AA)
NOTE: This device is an USB 3.0 device operating at lower speed...
No logical drive found (unpartitioned?)
Device eliminated because it was detected as a Hard Drive (score 8 > 0)
If this device is not a Hard Drive, please e-mail the author of this application
NOTE: You can enable the listing of Hard Drives under 'advanced drive properties'
0 devices found
Found UAS (USB 2.0) device 'Samsung SSD 840 EVO 120G SCSI Disk Device' (174C:55AA)
NOTE: This device is an USB 3.0 device operating at lower speed...
No logical drive found (unpartitioned?)
1 device found
No volume information for drive 0x81
Disk type: FIXED, Disk size: 120 GB, Sector size: 512 bytes
Cylinders: 14593, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 0
Disk ID: 0x00000000
Drive does not have an x86 Master Boot Record
Scanning image...
ISO analysis:
  Image is an UDF image
Disk image analysis:
  Image does not have an x86 Master Boot Record
ISO label: 'CES_X64FREV_EN-US_DV5'
  Size: 3.8 GB (Projected)
  Uses: EFI
  Uses: Bootmgr (BIOS and UEFI)
  Uses: Install.wim (version 0.13.1)
Using image: en_windows_10_enterprise_ltsc_2019_x64_dvd_be3c8ffb.iso (3.8 GB)
WIM extraction method(s) supported: wimgapi.dll
WIM apply method supported: wimgapi.dll
Opening: \\.\CDROM1/sources/install.wim:[0] (API)
Extracting: C:\Users\asdf\AppData\Local\Temp\Ruf3F4D.tmp (From [1].xml)
Closing: \\.\CDROM1/sources/install.wim
Will use 'Windows 10 Enterprise LTSC' (Build: 17763, Index 1) for Windows To Go

Format operation started
Requesting disk access...
No drive letter was assigned...
Will use 'E:' as volume mountpoint
Deleting partitions...
Notice: Could not delete partitions: [0x00000000] The operation completed successfully.
Opened \\.\PhysicalDrive1 for exclusive write access
No logical drive found (unpartitioned?)
Drive does not appear to be partitioned
Analyzing existing boot records...
Drive does not have an x86 Master Boot Record
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Deleting partitions...
Partitioning (GPT)...
● Creating EFI System Partition Partition (offset: 1048576, size: 300 MB)
● Creating Microsoft Reserved Partition Partition (offset: 315641344, size: 128 MB)
● Creating Main Data Partition (offset: 449859072, size: 111.4 GB)
Waiting for logical drive to reappear...
Closed Windows format prompt
Timeout while waiting for logical drive
Logical drive was not found!
Formatting (NTFS)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Writing Master Boot Record...
Using Rufus protective MBR
Found volume \\?\GLOBALROOT\Device\HarddiskVolume7\
Could not remount \\?\GLOBALROOT\Device\HarddiskVolume7\ as E: [0x00000012] There are no more files.
\\?\Volume{ac7063d0-1ae1-4380-a622-386e93fa30be}\ is already mounted as E:
Re-mounted volume as E: after error

Found UAS (USB 2.0) device 'Samsung SSD 840 EVO 120G SCSI Disk Device' (174C:55AA)
NOTE: This device is an USB 3.0 device operating at lower speed...
1 device found
Disk type: FIXED, Disk size: 120 GB, Sector size: 512 bytes
Cylinders: 14593, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 3
Disk GUID: {4975EDDA-E72E-4F07-860D-D91B8A3AA074}
Max parts: 128, Start Offset: 17408, Usable = 120034089472 bytes
Partition 1:
  Type: {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}
  Name: 'EFI System Partition'
  ID: {3F67603A-7199-4B0D-8C51-A014017C81EA}
  Size: 300 MB (314592768 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Partition 2:
  Type: {E3C9E316-0B5C-4DB8-817D-F92DF00215AE}
  Name: 'Microsoft Reserved Partition'
  ID: {B3B469D8-E3E3-4797-85F8-D53727E35FE1}
  Size: 128 MB (134217728 bytes)
  Start Sector: 616487, Attributes: 0x0000000000000000
Partition 3:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Main Data Partition'
  ID: {AC7063D0-1AE1-4380-A622-386E93FA30BE}
  Size: 111.4 GB (119584247808 bytes)
  Start Sector: 878631, Attributes: 0x0000000000000000
@pbatard

This comment has been minimized.

Copy link
Owner

commented Aug 1, 2019

Thanks!

@frh

This comment has been minimized.

Copy link

commented Aug 1, 2019

Out of curiosity I tried the same thing with a virtual USB disk in the VM, and the result was the same. I don't know if this will be useful in any way, but here's the log from that:

Rufus log
Rufus x86 v3.6.1551 (Portable)
Windows version: Windows 10 64-bit (Build 17763)
Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06
Grub versions: 0.4.6a, 2.04
System locale ID: 0x0409 (en-US)
Will use default UI locale 0x0409
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'en-US'
Notice: The ISO download feature has been deactivated because 'Check for updates' is disabled in your settings.
Found USB 3.0 device 'QEMU QEMU HARDDISK USB Device' (46F4:0001)
No logical drive found (unpartitioned?)
1 device found
No volume information for drive 0x81
Disk type: FIXED, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3916, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 0
Disk ID: 0x00000000
Drive does not have an x86 Master Boot Record
Found USB 3.0 device 'QEMU QEMU HARDDISK USB Device' (46F4:0001)
No logical drive found (unpartitioned?)
1 device found
No volume information for drive 0x81
Disk type: FIXED, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3916, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 0
Disk ID: 0x00000000
Drive does not have an x86 Master Boot Record
Scanning image...
ISO analysis:
  Image is an UDF image
Disk image analysis:
  Image does not have an x86 Master Boot Record
ISO label: 'CES_X64FREV_EN-US_DV5'
  Size: 3.8 GB (Projected)
  Uses: EFI
  Uses: Bootmgr (BIOS and UEFI)
  Uses: Install.wim (version 0.13.1)
Using image: en_windows_10_enterprise_ltsc_2019_x64_dvd_be3c8ffb.iso (3.8 GB)
WIM extraction method(s) supported: wimgapi.dll
WIM apply method supported: wimgapi.dll
Opening: \\.\CDROM1/sources/install.wim:[0] (API)
Extracting: C:\Users\asdf\AppData\Local\Temp\RufBADB.tmp (From [1].xml)
Closing: \\.\CDROM1/sources/install.wim
Will use 'Windows 10 Enterprise LTSC' (Build: 17763, Index 1) for Windows To Go

Format operation started
Requesting disk access...
No drive letter was assigned...
Will use 'E:' as volume mountpoint
Deleting partitions...
Notice: Could not delete partitions: [0x00000000] The operation completed successfully.
Opened \\.\PhysicalDrive1 for exclusive write access
No logical drive found (unpartitioned?)
Drive does not appear to be partitioned
Analyzing existing boot records...
Drive does not have an x86 Master Boot Record
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Deleting partitions...
Partitioning (GPT)...
● Creating EFI System Partition Partition (offset: 1048576, size: 300 MB)
● Creating Microsoft Reserved Partition Partition (offset: 315641344, size: 128 MB)
● Creating Main Data Partition (offset: 449859072, size: 29.6 GB)
Waiting for logical drive to reappear...
Closed Windows format prompt
Timeout while waiting for logical drive
Logical drive was not found!
Formatting (NTFS)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Writing Master Boot Record...
Using Rufus protective MBR
Found volume \\?\GLOBALROOT\Device\HarddiskVolume7\
Could not remount \\?\GLOBALROOT\Device\HarddiskVolume7\ as E: [0x00000012] There are no more files.
\\?\Volume{80bc6b37-dc5e-457c-b2c5-28dca0a89b35}\ is already mounted as E:
Re-mounted volume as E: after error

Found USB 3.0 device 'QEMU QEMU HARDDISK USB Device' (46F4:0001)
1 device found
Disk type: FIXED, Disk size: 32 GB, Sector size: 512 bytes
Cylinders: 3916, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 3
Disk GUID: {FD5FF4AB-7820-4E14-9A04-4BA1413C5226}
Max parts: 128, Start Offset: 17408, Usable = 32212220416 bytes
Partition 1:
  Type: {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}
  Name: 'EFI System Partition'
  ID: {29C32787-FC4B-4495-851E-8950C2548488}
  Size: 300 MB (314592768 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Partition 2:
  Type: {E3C9E316-0B5C-4DB8-817D-F92DF00215AE}
  Name: 'Microsoft Reserved Partition'
  ID: {3043F520-97B4-4805-B917-DCA25793ED1A}
  Size: 128 MB (134217728 bytes)
  Start Sector: 616487, Attributes: 0x0000000000000000
Partition 3:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Main Data Partition'
  ID: {80BC6B37-DC5E-457C-B2C5-28DCA0A89B35}
  Size: 29.6 GB (31762378752 bytes)
  Start Sector: 878631, Attributes: 0x0000000000000000

I also tried with MBR instead of GPT, and when I do that it seems to work.

@ckrzen

This comment has been minimized.

Copy link

commented Aug 2, 2019

(Full) logs are ALWAYS welcome. I'm afraid a "me too" without a log doesn't tell me much. Also please indicate if you are running Rufus on real hardware or on a VM.

Running 3.6 on bare-metal(HDD) and attaching full-log with screenshot.

rufus-3.6_fail.log
Rufus x86 v3.6.1551
Windows version: Windows 10 64-bit (Build 18362)
Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06
Grub versions: 0.4.6a, 2.04
System locale ID: 0x0409 (en-US)
Will use default UI locale 0x0409
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'en-US'
Found USB 3.0 device 'Patriot Memory USB Device' (13FE:6000)
Found USB 2.0 device 'Generic- SD/MMC/MS PRO USB Device' (0BDA:0153)
Device eliminated because it appears to contain no media
1 device found
Disk type: Removable, Disk size: 128 GB, Sector size: 512 bytes
Cylinders: 15077, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 1
Disk GUID: {D279B860-455D-4BBD-A74C-30097EB47492}
Max parts: 128, Start Offset: 17408, Usable = 124017146368 bytes
Partition 1:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Main Data Partition'
  ID: {01287DC6-0A3E-4E33-B8D6-0BCDF16D46B3}
  Size: 115.5 GB (124016115200 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Scanning image...
ISO analysis:
  Image is an UDF image
Disk image analysis:
  Image does not have an x86 Master Boot Record
ISO label: 'CCCOMA_X64FRE_EN-US_DV9'
  Size: 4.6 GB (Projected)
  Uses: EFI
  Uses: Bootmgr (BIOS and UEFI)
  Uses: Install.wim (version 0.13.1)
Using image: Win10_1903_x64.iso (4.6 GB)
Checking for Rufus updates...
Checking release channel...
No new release version found.
WIM extraction method(s) supported: wimgapi.dll
WIM apply method supported: wimgapi.dll
Opening: \\.\CDROM1/sources/install.wim:[0] (API)
Extracting: C:\Users\Chris\AppData\Local\Temp\RufA20A.tmp (From [1].xml)
Closing: \\.\CDROM1/sources/install.wim
Will use 'Windows 10 Home' (Build: 18362, Index 1) for Windows To Go

Format operation started
Requesting disk access...
Will use 'D:' as volume mountpoint
Deleting partitions...
Deleting ALL partition(s) from disk '\\?\PhysicalDrive1':
● Partition 1 (offset: 1048576, size: 115.5 GB)
Opened \\.\PhysicalDrive1 for exclusive write access
Analyzing existing boot records...
Drive has a Zeroed Master Boot Record
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Deleting partitions...
Partitioning (GPT)...
● Creating EFI System Partition Partition (offset: 1048576, size: 300 MB)
● Creating Microsoft Reserved Partition Partition (offset: 315641344, size: 128 MB)
● Creating Main Data Partition (offset: 449859072, size: 115.1 GB)
Closing existing volume...
Waiting for logical drive to reappear...
Closed Windows format prompt
Closed Windows format prompt
Timeout while waiting for logical drive
Logical drive was not found!
Formatting (NTFS)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Writing Master Boot Record...
Using Rufus protective MBR
Found volume \\?\GLOBALROOT\Device\HarddiskVolume10\
Could not remount \\?\GLOBALROOT\Device\HarddiskVolume10\ as D: [0x00000012] There are no more files.
\\?\Volume{abaeec03-b52e-11e9-a943-a0afbde05483}\ is already mounted as G: instead of D: - Will now use this target instead...
Re-mounted volume as G: after error

Found USB 3.0 device 'Patriot Memory USB Device' (13FE:6000)
Found USB 2.0 device 'Generic- SD/MMC/MS PRO USB Device' (0BDA:0153)
Device eliminated because it appears to contain no media
1 device found
Disk type: Removable, Disk size: 128 GB, Sector size: 512 bytes
Cylinders: 15077, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 3
Disk GUID: {08CB48B2-D60D-4899-B5C1-23572AFBC519}
Max parts: 128, Start Offset: 17408, Usable = 124017146368 bytes
Partition 1:
  Type: {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}
  Name: 'EFI System Partition'
  ID: {1735E07D-A648-4035-BADA-3AD8C1C163C4}
  Size: 300 MB (314592768 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Partition 2:
  Type: {E3C9E316-0B5C-4DB8-817D-F92DF00215AE}
  Name: 'Microsoft Reserved Partition'
  ID: {5BD046FB-A13A-4050-92AD-4EE67FAC504B}
  Size: 128 MB (134217728 bytes)
  Start Sector: 616487, Attributes: 0x0000000000000000
Partition 3:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Main Data Partition'
  ID: {A7E25CF3-445B-4198-8C6B-B7C911DE2CCA}
  Size: 115.1 GB (123567304704 bytes)
  Start Sector: 878631, Attributes: 0x0000000000000000

Rufus-3 6_fail

@ckrzen

This comment has been minimized.

Copy link

commented Aug 2, 2019

I can also confirm that this seem to only happen when using "GPT" partitioning for the WTG target. Selecting "MBR" allows the process to progress past the GPT fail point.

@pbatard

This comment has been minimized.

Copy link
Owner

commented Aug 2, 2019

Thanks for the report. Did cycling the port (Alt-C) help in any way at all?

@ckrzen

This comment has been minimized.

Copy link

commented Aug 2, 2019

@pbatard pbatard reopened this Aug 2, 2019

@pbatard

This comment has been minimized.

Copy link
Owner

commented Aug 2, 2019

Okay. I'm going to reopen this issue since it appears to affect a lot of people. Will see what I can do to try to get this fixed for 3.7.

@pbatard pbatard self-assigned this Aug 2, 2019

@pbatard pbatard added this to the 3.7 milestone Aug 2, 2019

@pbatard pbatard added this to In progress in Rufus Next Aug 6, 2019

@ForestJohnson

This comment has been minimized.

Copy link

commented Aug 10, 2019

Thank you for this wonderful software!! This happened to me on windows 10 update 1903 (no virtualization) with rufus 3.6.1551, Alt-C did not make any difference, but rolling back to rufus 3.5 fixed the problem.

WIM extraction method(s) supported: wimgapi.dll
WIM apply method supported: wimgapi.dll
Opening: \\.\CDROM1/sources/install.esd:[0] (API)
Extracting: C:\Users\forest\AppData\Local\Temp\Ruf332.tmp (From [1].xml)
Closing: \\.\CDROM1/sources/install.esd
Will use 'Windows 10 Home' (Build: 18362, Index 1) for Windows To Go

Format operation started
Requesting disk access...
Will use 'E:' as volume mountpoint
Deleting partitions...
Deleting ALL partition(s) from disk '\\?\PhysicalDrive2':
● Partition 1 (offset: 1048576, size: 300 MB)
● Partition 2 (offset: 315641344, size: 128 MB)
● Partition 3 (offset: 449859072, size: 931.1 GB)
Opened \\.\PhysicalDrive2 for exclusive write access
No logical drive found (unpartitioned?)
Drive does not appear to be partitioned
Analyzing existing boot records...
Drive has a Zeroed Master Boot Record
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Deleting partitions...
Partitioning (GPT)...
● Creating EFI System Partition Partition (offset: 1048576, size: 300 MB)
● Creating Microsoft Reserved Partition Partition (offset: 315641344, size: 128 MB)
● Creating Main Data Partition (offset: 449859072, size: 931.1 GB)
Waiting for logical drive to reappear...
Closed Windows format prompt
Timeout while waiting for logical drive
Logical drive was not found!
Formatting (NTFS)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Writing Master Boot Record...
Using Rufus protective MBR
Found volume \\?\GLOBALROOT\Device\HarddiskVolume40\
Could not remount \\?\GLOBALROOT\Device\HarddiskVolume40\ as E: [0x00000012] There are no more files.
\\?\Volume{5e18a454-f877-4c31-a96c-89a93ac8914a}\ is already mounted as E:
Re-mounted volume as E: after error

Found USB 3.0 device 'WD My Passport 0748 USB Device' (1058:0748)
1 device found
Disk type: FIXED, Disk size: 1TB, Sector size: 512 bytes
Cylinders: 121597, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 3
Disk GUID: {224D27E3-98AB-4CA4-AD5E-B19C0A3E3429}
Max parts: 128, Start Offset: 17408, Usable = 1000170551808 bytes
Partition 1:
  Type: {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}
  Name: 'EFI System Partition'
  ID: {2A690BAA-16CE-4CC2-9CFF-DDD29E261E5D}
  Size: 300 MB (314592768 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Partition 2:
  Type: {E3C9E316-0B5C-4DB8-817D-F92DF00215AE}
  Name: 'Microsoft Reserved Partition'
  ID: {E4D1069D-FBB0-4234-8749-E0070F2971E2}
  Size: 128 MB (134217728 bytes)
  Start Sector: 616487, Attributes: 0x0000000000000000
Partition 3:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Main Data Partition'
  ID: {5E18A454-F877-4C31-A96C-89A93AC8914A}
  Size: 931.1 GB (999720710144 bytes)
  Start Sector: 878631, Attributes: 0x0000000000000000

@pbatard

This comment has been minimized.

Copy link
Owner

commented Aug 10, 2019

Yeah, the problem (which can be verified with diskpart as well as the Disk Manager UI) is that Windows sometimes seems to "forget" to allocate a proper volume ID to all the partitions after you repartition a drive.

In our case, we'll get the ESP (partition 1) and MSR (partition 2) with an effective accessible volume, but not partition 3, which is the main NTFS partition where we apply the WIM image.

In other words, instead of getting the partitions enumerated like this:

GOT \\?\Volume{7ebca266-b883-11e9-9a1e-88d7f6e01c0c}\ @1048576
GOT \\?\Volume{7ebca267-b883-11e9-9a1e-88d7f6e01c0c}\ @315641344
GOT \\?\Volume{7ebca268-b883-11e9-9a1e-88d7f6e01c0c}\ @449859072

where the value behind the @ represents the offset of each partition, you only ever get this:

GOT \\?\Volume{7ebca266-b883-11e9-9a1e-88d7f6e01c0c}\ @1048576
GOT \\?\Volume{7ebca267-b883-11e9-9a1e-88d7f6e01c0c}\ @315641344

where Windows "forgets" to assign a volume GUID to the 3rd partition.

This is the reason why I advise a USB port reset, as a proper reset should force Windows to rescan the partition layout and assign an ID to the 3rd partition. However, it appears that, in their great wisdom, Microsoft have neutered USB port reset in Windows 1903, because it doesn't seem to produce the usual disconnection one sees with previous versions of Windows (device refresh from reset is way too fast!). And none of the APIs I tried to force a partition layout refresh seem to help either (and, believe me, I've tried all of the ones that Microsoft makes available). So my recommendation now is to yank out the USB drive and then plug it back to see if that helps (which may or may not work, since Windows appears to do its hardest to cache a partition layout, instead of properly refreshing it when it should).

Now, those with a keen eye might notice that the first longword in the GUID of each partition is incremented (7ebca266, 7ebca267, 7ebca268) whereas the rest of the GUID of the same, so you might be tempted to think that, even if Windows does not report the GUID, Rufus could still "guess" it, but I'm afraid it's the other way round: The fact that Windows doesn't report a volume GUID for the 3rd partition is because it can't be accessed, at all. So even if we can logically guess the Volume ID to use, we still won't be able to do anything with the partition, since none of the Windows APIs will allow us to access it (and I'm afraid that, no, using a different ID to access the volume, such as \\?\GLOBALROOT\Device\HarddiskVolume##, which is supposed to be equivalent to a GUID volume, doesn't help either).

So, provided the issue is that Windows only manages to sort its volume GUIDs for the first 2 partitions, I think I might revert to what I was doing in 3.5, which is have the partitions in MSR, Data and ESP order, rather than ESP, MSR, Data as was changed in 3.6. This might make things less compatible with some poorly designed UEFI systems (that aren't specs compliant if they expect the ESP as the first partition), but hopefully it will sort things out until Microsoft really gets its shit together with regards to their ABSOLUTELY ABYSMAL handling of multiple partitions...

@xemex

This comment has been minimized.

Copy link

commented Aug 10, 2019

Thanks for the insight in the root cause.
I have just tried unplugging the device and observed no difference.

Note: I am using build Windows 18362, not 1903 and yet having same problems (on a bare metal).
MBR partitioning works just fine.

Rufus x86 v3.6.1551
Windows version: Windows 10 64-bit (Build 18362)
Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06
Grub versions: 0.4.6a, 2.04
System locale ID: 0x0409 (en-US)
Will use default UI locale 0x0409
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'en-US'
Found USB 2.0 device 'TOSHIBA MQ01ABF050 USB Device' (18A5:0408)
NOTE: This device is an USB 3.0 device operating at lower speed...
Device eliminated because it was detected as a Hard Drive (score 6 > 0)
If this device is not a Hard Drive, please e-mail the author of this application
NOTE: You can enable the listing of Hard Drives under 'advanced drive properties'
0 devices found
Found USB 2.0 device 'TOSHIBA MQ01ABF050 USB Device' (18A5:0408)
NOTE: This device is an USB 3.0 device operating at lower speed...
1 device found
Disk type: FIXED, Disk size: 512 GB, Sector size: 512 bytes
Cylinders: 60801, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 3
Disk GUID: {52E14D01-14E5-4D6A-AEBF-A6EED68C7ADD}
Max parts: 128, Start Offset: 17408, Usable = 500107825664 bytes
Partition 1:
  Type: {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}
  Name: 'EFI System Partition'
  ID: {0E2B4BB4-B158-4F44-81AD-9F04B548D9D4}
  Size: 300 MB (314592768 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Partition 2:
  Type: {E3C9E316-0B5C-4DB8-817D-F92DF00215AE}
  Name: 'Microsoft Reserved Partition'
  ID: {40750DBE-9C9B-4264-BEFB-3BDE5B1E51D5}
  Size: 128 MB (134217728 bytes)
  Start Sector: 616487, Attributes: 0x0000000000000000
Partition 3:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Main Data Partition'
  ID: {E8479485-C77B-47CE-8321-B253B4999D89}
  Size: 465.3 GB (499657984000 bytes)
  Start Sector: 878631, Attributes: 0x0000000000000000
Scanning image...
ISO analysis:
  Image is an UDF image
Disk image analysis:
  Image does not have an x86 Master Boot Record
ISO label: 'CENA_X64FREE_EN-US_DV9'
  Size: 4.1 GB (Projected)
  Uses: EFI
  Uses: Bootmgr (BIOS and UEFI)
  Uses: Install.wim (version 0.13.1)
Using image: 18362.30.190401-1528.19h1_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso (4.1 GB)
WIM extraction method(s) supported: 7-Zip, wimgapi.dll
WIM apply method supported: wimgapi.dll
Opening: \\.\CDROM1/sources/install.wim:[0] (API)
Extracting: C:\Users\Przemek\AppData\Local\Temp\Ruf3DF2.tmp (From [1].xml)
Closing: \\.\CDROM1/sources/install.wim
Will use 'Windows 10 Enterprise Evaluation' (Build: 18362, Index 1) for Windows To Go

Format operation started
Requesting disk access...
Will use 'G:' as volume mountpoint
Deleting partitions...
Deleting ALL partition(s) from disk '\\?\PhysicalDrive4':
● Partition 1 (offset: 1048576, size: 300 MB)
● Partition 2 (offset: 315641344, size: 128 MB)
● Partition 3 (offset: 449859072, size: 465.3 GB)
Opened \\.\PhysicalDrive4 for exclusive write access
No logical drive found (unpartitioned?)
Drive does not appear to be partitioned
Analyzing existing boot records...
Drive has a Zeroed Master Boot Record
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Deleting partitions...
Partitioning (GPT)...
● Creating EFI System Partition Partition (offset: 1048576, size: 300 MB)
● Creating Microsoft Reserved Partition Partition (offset: 315641344, size: 128 MB)
● Creating Main Data Partition (offset: 449859072, size: 465.3 GB)
Waiting for logical drive to reappear...
Closed Windows format prompt
Timeout while waiting for logical drive
Logical drive was not found!
Formatting (NTFS)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Writing Master Boot Record...
Using Rufus protective MBR
Found volume \\?\GLOBALROOT\Device\HarddiskVolume45\
Could not remount \\?\GLOBALROOT\Device\HarddiskVolume45\ as G: [0x00000012] There are no more files.
\\?\Volume{159487f0-4445-4b0f-9187-69112318783d}\ is already mounted as G:
Re-mounted volume as G: after error

Found USB 2.0 device 'TOSHIBA MQ01ABF050 USB Device' (18A5:0408)
NOTE: This device is an USB 3.0 device operating at lower speed...
1 device found
Disk type: FIXED, Disk size: 512 GB, Sector size: 512 bytes
Cylinders: 60801, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 3
Disk GUID: {EB536DEA-6E59-408B-9718-B709773E2DF9}
Max parts: 128, Start Offset: 17408, Usable = 500107825664 bytes
Partition 1:
  Type: {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}
  Name: 'EFI System Partition'
  ID: {4A33CC25-FA18-46E9-8D50-8E57F0FB956E}
  Size: 300 MB (314592768 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Partition 2:
  Type: {E3C9E316-0B5C-4DB8-817D-F92DF00215AE}
  Name: 'Microsoft Reserved Partition'
  ID: {F34C1D5D-5AC5-4833-9187-C82F7EDEA28D}
  Size: 128 MB (134217728 bytes)
  Start Sector: 616487, Attributes: 0x0000000000000000
Partition 3:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Main Data Partition'
  ID: {159487F0-4445-4B0F-9187-69112318783D}
  Size: 465.3 GB (499657984000 bytes)
  Start Sector: 878631, Attributes: 0x0000000000000000
@pbatard

This comment has been minimized.

Copy link
Owner

commented Aug 13, 2019

Confirmed that moving the ESP back to being the last partition should make Rufus perform as it did in 3.5. I will push the fix shortly and it will be part of Rufus 3.7 (which I may release earlier than planned as there are now quite a few fixes that would probably be better pushed sooner rather than later).

@pbatard pbatard closed this in 936bd9b Aug 13, 2019

@pbatard pbatard referenced this issue Aug 13, 2019

@pbatard pbatard moved this from In progress to Done in Rufus Next Aug 19, 2019

@pbatard

This comment has been minimized.

Copy link
Owner

commented Aug 26, 2019

Note, for those who have been facing this issue, I have just released a BETA for the upcoming Rufus 3.7, which you can download from HERE.

If you feel like testing and confirm that this fixes the issues you were experiencing with 3.6, please do so!

@frh

This comment has been minimized.

Copy link

commented Sep 4, 2019

I tested with 3.7 beta in the same environment as before (Windows 10 VM running in KVM with USB passthrough for the target disk). I can confirm that the problem appears to be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
7 participants
You can’t perform that action at this time.