Closed b-vest closed 2 years ago
There's now a second report of this https://forums.frontier.co.uk/threads/elite-dangerous-market-connector-edmc.548869/post-9861368 .
As noted in my reply there, the real puzzle is why EDMarketConnector.exe isn't exiting when WinSparkle.DLL calls the provided callback function.
There might, or might not, be a tweak I can do to the installer to ensure it doesn't do this. I checked when this issues was opened and couldn't see anything in the current installer configuration that explicitly asks for such.
Looking at https://www.itninja.com/blog/view/reallysuppress-a-msi-reboot this may well be a consequence of the original developer's decision to have the EDMC installers present no UI/options for customisation. The default in the absence of such being to reboot 'if needed'.
I'll see how to specify 'ReallySuppress' for this, if possible.
EDMarketConnector-debug.log.zip I uploaded the last logs until the auto restart of my PC, as requested. 7 of them, zipped.
EDMarketConnector-debug.log.zip I uploaded the last logs until the auto restart of my PC, as requested. 7 of them, zipped.
2022-06-09 15:09:25.724 UTC - DEBUG - 21132:30156:30156 <plugins>.EDMC-Canonn-6.
6.0.canonn.patrol.InfoLink.__configure_event:174: diff 0.131029
2022-06-09 15:09:25.725 UTC - DEBUG - 21132:30156:30156 <plugins>.EDMC-Canonn-6.
6.0.canonn.release.ReleaseLink.__configure_event:78: Release widget resize
2022-06-09 15:09:25.733 UTC - DEBUG - 21132:30156:30156 <plugins>.EDMC-Canonn-6.
6.0.canonn.release.ReleaseLink.__configure_event:78: Release widget resize
Yes, I scrolled through them for a bit and noticed the same, but I thought you'd look for some specific text that I couldn't find at a glance. Sorry.
Nope, literally no line that doesn't contain EDMC-Canonn
in those.
OK, tested with that installer tweak:
develop
, this means nothing asked the .exe to shutdown.That looks great, but I'd like to suggest something else: Is it possible to notify in advance that if we're to proceed with installation, a restart will be required and let us choose to abort the installation before starting? I don't know if msiexec offers such option.
That looks great, but I'd like to suggest something else: Is it possible to notify in advance that if we're to proceed with installation, a restart will be required and let us choose to abort the installation before starting? I don't know if msiexec offers such option.
Not without performing major work on how the installer works, which is out of scope for the time being. That 'stall' in the middle is presumably it specifically trying to overwrite the .exe, failing, waiting a while, trying again etc, and then finally giving up. i.e. it doesn't even know there's going to be a problem until it hits that part of the installation process, by which time it may well have already replaced many other files.
I'm not arguing, and I don't know what the process does. In my case I think it couldn't close the running program (I could still see it, dimmed, as stuck programs usually are). Your solution is great, and I'm happy for the time you took to solve it. The problem is marginal, anyway :)
This change is in the 5.4.1 installer.
Please check the Known Issues in case this has already been reported.
Please also check if the issue is covered in our Troubleshooting Guide. It might be something with a known work around, or where a third party (such as EDSM) is causing logging that is harmless.
Please complete the following information:
Describe the bug When the update completed Windows went straight to restarting.
To Reproduce Steps to reproduce the behavior: Update to latest version. I am not sure if it is reproducible. Windows Event logs does have the messages below.