Bug 2432305

Summary: Installation failed: The installer cannot continue due to a critical error: Installation of the system failed: Installing software 95%
Product: [Fedora] Fedora Reporter: sweetman3895
Component: anacondaAssignee: Martin Kolman <mkolman>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 43CC: akankovs, alpha, anaconda-maint, kkoukiou, mkolman, w
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-02-03 13:24:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Recomended attachment none

Description sweetman3895 2026-01-23 05:33:15 UTC 
Error details  
org.fedoraproject.Anaconda.PayloadInstallationError: Failed to install image: process '['rsync', '-pogAXtlHrDx', '--stats', '--info=flist2,name,progress2', '--no-inc-recursive', '--exclude', '/dev/', '--exclude', '/proc/', '--exclude', '/tmp/*', '--exclude', '/sys/', '--exclude', '/run/', '--exclude', '/boot/*rescue*', '--exclude', '/boot/loader/', '--exclude', '/boot/efi/', '--exclude', '/etc/machine-id', '--exclude', '/etc/machine-info', '/run/install/sources/mount-0000-live_os_image/', '/mnt/sysroot']' exited with status 23

Reproducible: Always

Steps to Reproduce:
1.Used Fedora Media Writer on MacOS (non-arm64 build 5.2.9)
2.Downloaded Fedora Workstation 43 from installer
3.Followed the installer process and keep hitting the same issue and the smae 95% mark
Comment 1 sweetman3895 2026-01-23 05:35:27 UTC 
Created attachment 2123459 [details]
Recomended attachment
Comment 2 sweetman3895 2026-01-23 05:37:06 UTC 
Might be user error. I have windows installed on that drive and it might be whats causing the issue. Will wipe the drive and try again.
Comment 3 Adam Kaňkovský 2026-02-03 13:24:12 UTC 

*** This bug has been marked as a duplicate of bug 2412427 ***