What I do know is that the process is still broken and the potential cause of the issue which I mentioned in the 2nd of the 2 potential causes I listed remains unchanged (update-info.json "isAdminRightsRequired" value is still euqal to false, and as I stated the first time, you need admin permissions to install an application to the program files directory, which is where ipfs desktop is installed when you install it for all users). Interestingly, while both were the same size, (83,195 kb), I noticed that the hash values were different, so they are not the same file? I don't know. I did notice that there were 2 executable files in the directory though (I don't recall if there were last time): one named "updater.exe" and one that was the actual install file for the program (IPFS-Desktop-Setup-0.12.0.exe). Program was uninstalled, not re-installed, and the installation files were located in the %USERPROFILE%\Appdata\local\ipfs-desktop-updater.
MICROSOFT AUTOUPDATE NOT WORKING UPDATE
Not sure why this was closed before verifying that it worked, because, when I initiated the auto update to ipfs-desktop 12.0, the exact same issue occurred once again. We are missing allowElevation and packElevateHelper: the default values should be ok, but we should add explicit values to the config, just to be safe. PackElevateHelper = true Boolean - Whether to pack the elevate executable (required for electron-updater if per-machine installer used or can be used in the future). If false, user will have to restart installer with elevated permissions. If oneClick is false and perMachine is false (default): install mode installer page.ĪllowElevation = true Boolean - assisted installer only.If oneClick is false and perMachine is true: no install mode installer page, always install per-machine.If oneClick is true (default): Whether to install per all users (per-machine).Or whether installation always per all users (per-machine). PerMachine = false Boolean - Whether to show install mode installer page (choice per-machine or per-user) for assisted installer. IPFS auto-update functionality would automatically re-install the application successfully with the same configurations as the previous install
Wait for the auto-update functionality dialog box to appear and initiate the process.Install ipfs-desktop version 0.11.2 or 0.11.1 and configure the installation so that the application is available to all users.I am confident that this is the cause of the failed installation, as, when I navigated to %USERNAME%\appdata\local\ipfs-desktop-updater\pending and opened the update-info.json file, I saw the following: If the installer takes into account the install settings from the previous installation (in other words, installs the new version for all users if the previous install was configured to be installed for all users), then the reason that it might be failing is because the process may lack the elevated permissions needed to write to the Program Files directory. The process initiating that auto-update functionality may not have the elevated permissions that it needs to write to the Program files directory.
If this turns out to be the case, while technically still successfully installing the application (which is why I emphasized "correctly"), my IPFS-desktop Desktop icon can no longer find its source executable, and I just end up downloading the installer and reinstalling the application manually anyway, defeating the auto update functionality entirely. As you may know, this is not the default configuration for the installer (the default being to install IPFS-desktop only for the current user), so what MAY be happening is that IPFS-desktop is uninstalling the old version located in Program files (the folder to install app for all users), but then installing the new version in app data (only install for current user).
0 kommentar(er)
