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

Unable to write ISO — elevate as administrator by default. #723

Open
JaredRichardWilliam opened this issue Aug 11, 2024 · 2 comments
Open

Comments

@JaredRichardWilliam
Copy link

JaredRichardWilliam commented Aug 11, 2024

Issue

I've installed https://github.com/FedoraQt/MediaWriter/releases/download/5.1.2/FedoraMediaWriter-win64-5.1.2.exe on Windows 11 Pro build 22631.3958. Like https://discussion.fedoraproject.org/t/fedora-media-writer-failure-windows-11/109897/15, it's unable to write to my USB-A storage device:

image

I wanted to get some logs, but

#!/usr/bin/env -S pwsh
& "$Env:SystemDrive\Program Files (x86)\Fedora Media Writer\mediawriter.exe"

spawns a new process independent of the shell.

Disk

I've solely tried the aforementioned storage device:

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          232 GB  1024 KB        *
  Disk 1    Online         1863 GB  1024 KB        *
* Disk 2    Online           14 GB    14 GB

DISKPART> select disk 2

Disk 2 is now the selected disk.

DISKPART>

States

I've tried it with and without a single-partition filesystem:

  1. DISKPART> detail disk
    
    SanDisk Cruzer Blade USB Device
    Disk ID: C74707FF
    Type   : USB
    Status : Online
    Path   : 0
    Target : 0
    LUN ID : 0
    Location Path : UNAVAILABLE
    Current Read-only State : No
    Read-only  : No
    Boot Disk  : No
    Pagefile Disk  : No
    Hibernation File Disk  : No
    Crashdump Disk  : No
    Clustered Disk  : No
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 4     E                       Removable       0 B  Unusable
    
    DISKPART>
    
  2. DISKPART> detail disk
    
    SanDisk Cruzer Blade USB Device
    Disk ID: C74707FF
    Type   : USB
    Status : Online
    Path   : 0
    Target : 0
    LUN ID : 0
    Location Path : UNAVAILABLE
    Current Read-only State : No
    Read-only  : No
    Boot Disk  : No
    Pagefile Disk  : No
    Hibernation File Disk  : No
    Crashdump Disk  : No
    Clustered Disk  : No
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 4     F   NEW VOLUME   FAT32  Removable     14 GB  Healthy
    
    DISKPART>
    

Responses

By the way, I might respond as @RokeJulianLockhart if need be — that is the actual author of this BR. I'm merely using my brother's account because it's his PC which is affected.

@JaredRichardWilliam
Copy link
Author

JaredRichardWilliam commented Aug 11, 2024

#723 (comment)

Elevation

I've ascertained how to remediate this:

#!/usr/bin/env -S pwsh
#Requires -RunAsAdministrator
& "$Env:SystemDrive\Program Files (x86)\Fedora Media Writer\mediawriter.exe"
  1. image

  2. image

It needs to be automatically elevated.

Automatic Remounture by Explorer

However, note that some buggy behaviour is experienced:

  1. Merely wait for the write to finish. Two black explorer.exe windows with attached formatting dialogs shall appear.

image

  1. If you click "Cancel":

image

It shouldn't be automatically remounted by explorer (especially during the verification process) because most users shall chose to wipe it, as Windows recommends.

@JaredRichardWilliam JaredRichardWilliam changed the title Unable to write ISO. Unable to write ISO — elevate as administrator by default. Aug 11, 2024
@RokeJulianLockhart
Copy link

RokeJulianLockhart commented Aug 11, 2024

#723 (comment)

...and Fedora-KDE-Live-x86_64-40-1.14.iso fails verification:

IMG_20240811_233548

Luckily, it boots and installs correctly otherwise.

Would be nice if dmesg (if that's what I'm looking at, with Plymouth disabled) were to state the key combination necessary to reboot from this state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants