Downloading macOS Tahoe stuck at 10%

[ICreateMusic]

Operating System

Windows

OS Version / Distro

Windows 11 25H2

Machine Type

Desktop

Target macOS Version

macOS Tahoe 26

config.plist

No

Logs

Screenshots

Issue Description

Downloading macOS Tahoe stuck at 10%

[LarryFlynt2]

Had the same issue on my Surface Pro 6. It goes to start, but I don't think the download actually started though. I left it running for probably close to 14 hours, and it never budged from that initial 10% starting point.

[armouredqar]

Same problem - confirm. Separately I had suggested providing facility to use an already downloaded version AND opportunity for user to download themselves (and point to that downloaded version).
Response was not needed because CDN (? so let me try on my own) and version automatically uses downloaded versions (after success). Vicious circle, if it won't download properly.

[riftaway7-code]

the progress bar's kinda lying to you honestly, it jumps to 10% the second download starts and just sits there til it's fully done, no real progress tracking happening. that said 14hrs with zero output isn't normal, that's an actual hang. the recovery download has no timeout at all so if apple's cdn stalls it just sits there forever with no error. adding a timeout + real progress bar. for now if it's been stuck a while with no network activity, just cancel and retry

[riftaway7-code]

found the actual hang. the recovery download had zero timeout anywhere so if apple's cdn stalled it just sat there forever with no error. v1.4.2 adds a timeout, it'll fail with a retryable error after 2 min of silence instead of hanging: https://github.com/riftaway7-code/hackmate/releases/tag/v1.4.2

also fixed the ssl cert error that a couple people in the other thread were hitting on the same download step, might've been part of what you two ran into too. redownload and try again

[riftaway7-code]

found it, real bug not a hang. macrecovery.py reports download progress with a carriage return for in-place refresh, not a newline, and the packaged exe's progress reader only forwarded output to the ui on newlines. so it was actually downloading the whole time, the ui just never got the memo and sat frozen at 10% until the download finished. fixed on main (commit 6bc2f59), will be in the next release.