Emulator Issues #13121
closed
[Regression] Updater always fail with "Could not fetch current manifest. Aborting" since 5.0-17693 on Windows
0%
Description
Game Name?
N/A
Game ID?
N/A
MD5 Hash?
N/A
What's the problem? Describe what went wrong.
Starting with Dolphin 5.0-17693 on Windows, updater always error out with "A fatal error occurred and the updater cannot continue: Could not fetch current manifest. Aborting."
What steps will reproduce the problem?
- Download Dolphin 5.0-17693 or newer (make sure to go at least one version older than the latest available build, otherwise there won't be any updates to apply).
- Select the Dev update track in Dolphin's auto-update settings.
- Either close and reopen Dolphin, or go to Help => Check for updates.
- New update popup will show up. Click "Install Update".
- Updater will fail with "Could not fetch current manifest. Aborting." error.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Yes. Tested on 5.0-18042.
Is the issue present in the latest stable version?
No.
If the issue isn't present in the latest stable version, which is the first broken version?
The problem started with 5.0-17693 (the merge of PR #1189). The updater works fine on 5.0-17691 or older.
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible.
N/A
What are your PC specifications?
Intel Core i7-11800H
NVIDIA GeForce RTX 3060 Laptop
Windows 11 Pro (Insider Preview)
Is there anything else that can help developers narrow down the issue?
- I'm aware the updater now checks the installed VC++ Runtime version, but I don't think that's the problem. For reference I have the most recent version (at the time this issue was opened) of VC++ 2015-2022 installed: 14.34.31931
- I've confirmed the directory where Dolphin is installed is writable (both by regular users as well as administrators)
- I tried executing both Dolphin and the Updater with elevated privileges, but nothing changed
- With the aid of Process Explorer I checked the command line passed to the updater in 5.0-17693 (first broken version) and 5.0-17691 (last working version) but didn't notice anything wrong apart from the new "--binary-to-restart" parameter, which seemed correct anyway
Updated by mbc07 about 2 years ago
Tried to reproduce this on Windows 10, and something different happens: updater will error out with "failed to apply update" during the "checking platform" step (latest VC++ 2015-2022 already installed). Regardless, upon ignoring the error and relaunching Dolphin, it'll be running the most recent version, despite the updater error.
Will try checking the behavior with the stable build of Windows 11 next, to see if anything changes (I'm currently running the most recent Insider Preview build from the dev channel)...
Updated by mbc07 about 2 years ago
Ok, this issue can be closed. The problem was on my side.
Dolphin 5.0-17691 and earlier renamed the updater to "Updater.2.exe" before running it, while Dolphin 5.0-17693 and newer run "Updater.exe" directly. I'm not sure when (nor how) it happened but "Updater.exe" was blocked via a firewall rule, and, unsurprisingly, couldn't access the network to download the manifests, nor anything else. After deleting that rule, everything works fine now...
Updated by