Emulator

What version are you trying to update from?

Does it happen for you with https://dl.dolphin-emu.org/builds/59/9a/dolphin-master-5.0-17756-x64.7z ?

If it still happens with that build, take a procmon trace and link it

godisgovernment wrote:

If it still happens with that build, take a procmon trace and link it

Same problem. Same message, when updating to version 17762
Procmon trace ?

take a capture with this tool while trying to update dolphin https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
upload the saved trace to some external site like google drive, it will be large.

godisgovernment wrote:

take a capture with this tool while trying to update dolphin https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
upload the saved trace to some external site like google drive, it will be large.

Ok, I'll wait for the next update! Thanks

no, don't wait. just run a slightly older build, like the link from above: https://dl.dolphin-emu.org/builds/59/9a/dolphin-master-5.0-17756-x64.7z

godisgovernment wrote:

no, don't wait. just run a slightly older build, like the link from above: https://dl.dolphin-emu.org/builds/59/9a/dolphin-master-5.0-17756-x64.7z

Here is:

Please delete the link afterwards :)

Thanks, I've downloaded the file so you can remove it from your share.

Cricri: can you try some things:
1) check if you see "this file came from another computer" in properties of dolphin folder(s) or updater.exe files: https://www.systoolsgroup.com/updates/wp-content/uploads/2015/04/image1.png
2) try to add dolphin directory to Defender exclusion list https://support.microsoft.com/en-us/windows/add-an-exclusion-to-windows-security-811816c0-4dfd-af4a-47e4-c301afe13b26

3) try to (temporarily) disable Defender "real-time protection".

The problem seems to be that Defender keeps a handle to Updater.exe open when we try to rename it. Just want to make sure this is the real issue.

godisgovernment wrote:

3) try to (temporarily) disable Defender "real-time protection".

The problem seems to be that Defender keeps a handle to Updater.exe open when we try to rename it. Just want to make sure this is the real issue.

After doing some tests on the old folder, deleting the updater.exe.bak file, I no longer had the problem.

Did those tests include changing defender settings? or just deleting that file?

godisgovernment wrote:

Did those tests include changing defender settings? or just deleting that file?

Only file deleted

Thanks. this is hopefully fixed by https://github.com/dolphin-emu/dolphin/pull/11231 . once that PR is merged (and there's some commit afterward to generate an update), let us know if it's fixed.

godisgovernment wrote:

Thanks. this is hopefully fixed by https://github.com/dolphin-emu/dolphin/pull/11231 . once that PR is merged (and there's some commit afterward to generate an update), let us know if it's fixed.

I just got a new update, same problem. In fact, you would otherwise have to remove the update.bak file each time for it to work.

can you try this:
1) download+extract https://dl.dolphin-emu.org/builds/60/4f/dolphin-master-5.0-17768-x64.7z
2) copy (duplicate) Updater.exe to Updater.exe.bak to simulate the problem
3) run dolphin.exe and let it update to the latest dev build from 5.0-17768

godisgovernment wrote:

can you try this:
1) download+extract https://dl.dolphin-emu.org/builds/60/4f/dolphin-master-5.0-17768-x64.7z
2) copy (duplicate) Updater.exe to Updater.exe.bak to simulate the problem
3) run dolphin.exe and let it update to the latest dev build from 5.0-17768

The 771 and the one before it passed by themselves without error. But I had also installed on another PC to do tests, the 771 I had the same error but I don't know from which version, one had passed, that of morning. Maybe next time there won't be any more.

please try the exact steps I've listed.

godisgovernment wrote:

please try the exact steps I've listed.

So, I did this manipulation on the 2nd PC where it also crashed, and the update went from 768 to 771 without error.

Thanks for checking, I think this can be marked as fixed now