[bcurran3]

It appears that Launcher64.exe v1.0 has a bug. 

After running the launcher and closing it via the Windows X button or Launcher64's - EXIT - button, it remains resident. It's not visible, but it's still resident. Running Launcher64 additional times will create more phantom instances of it.

How to duplicate:
- Run Launcher64 and close it
- In PowerShell run get-process -name launcher* and you'll see the instances
- In Task Manager scroll to find Portable Launcher and you'll see the instances
- Repeat above and you'll see a +1 instance

I'm attaching two example screen clippings of PowerShell and Task Manager after running and closing Launcher64 three times.

NOTE: This is on Microsoft Windows [Version 10.0.22621.900] and could be different under different builds.

[Shark007]

Launcher64.exe has no GUI.
Due to your report, I do see an error in my logic.

When Launcher64.exe is working correctly, it checks for and removes conflicts,
Then it launches Settings64_portable.exe

Because you had used the path \Program Files\Shark007 for your portable files,
It was attempting to remove a previous 'Installer' installation, but the app would hang trying to remove itself.
I removed the improper identification of an installer release being present at that location and rely on the registry now.

New in the current release, (this option was not present in past releases)
If the commandline silent is used, it will perform a silent update of all files.

The updated file will be in the next 'full' release as this will not be dealt with in an online update.

[bcurran3]

I can confirm Launcher64 v1.2.1.0 is running Settings64_portable and closing correctly for me.

I have not tried using it for an upgrade yet.

[bcurran3]

Could you please confirm that the best way to script an upgrade would be to simply run "Launcher64 silent" after the next release?

[Shark007]

There is no best way.
There are three ways with identical outcomes.

Launcher64.exe silent
AutoUpdate.exe silent (This one contains all the important logic)
Settings64_portable.exe silent

[bcurran3]

Thanks. I'm getting weird mixed results.

My script runs "AutoUpdate.exe silent" (v5.4.0.0) followed by "Settings64_portable users".

On one machine it upgraded fine. A second machine it failed to upgrade and still shows v16.5.3 in Launcher64. I deleted c:\program files\shark007 (where the archive is extracted) and ran the script again. On the second pass it succeeded. Exit codes of 0 for both commands each run of the script. Weird.

Possibly my environment or a fluke. Should fix itself either way on a 2nd pass/next upgrade.

NOTE: Script does some pre-cleanup via:

Code:

if (Test-Path "${env:ProgramFiles(x86)}\Shark007") { Remove-Item -Recurse -Force "${env:ProgramFiles(x86)}\Shark007" }
if ((Test-Path "$env:ProgramFiles\Shark007") -and (!(Test-Path "$env:ProgramFiles\Shark007\ADVANCED_64bitCodecs"))) { Remove-Item -Recurse -Force "$env:ProgramFiles\Shark007" | Out-Null }

and only runs AutoUpdate when found:

Code:

if (Test-Path "$env:ProgramFiles\Shark007\ADVANCED_64bitCodecs\Tools\AutoUpdate.exe"){
Write-Host "  ** Running AutoUpdate." -Foreground Magenta
Start-ChocolateyProcessAsAdmin -Statements "silent" -ExeToRun "$env:ProgramFiles\Shark007\ADVANCED_64bitCodecs\Tools\AutoUpdate.exe" -WorkingDirectory "$env:ProgramFiles\Shark007\ADVANCED_64bitCodecs\Tools"
return
}

Not really relevant, but throwing it out there for the bigger picture.

 5.4.0.0Settings64_portable Settings64_portablein

[Shark007]

Stop doing the pre cleanup.
Use 'Launcher64 silent' because that App will do the pre clean up you're doing including the registry

[bcurran3]

Ran script on third kid's Guinea pig's machine and scripted silent upgrade of v16.5 -> v17.0 went fine.

Another observation is that post upgrade the Shark007 Codecs Windows Start Menu folder is still present with the Uninstall 32bit Advanced and Uninstall x64Components icons still present as well as the 32Bit Settings Application and 64Bit Settings Application icons in the Windows Start Menu "root." 

I'm pretty sure current install is still making the 64Bit Settings Application icon but you might want to consider checking for and removing the others when present.

[bcurran3]

Stop doing the pre cleanup.
Use 'Launcher64 silent' because that App will do the pre clean up you're doing including the registry

Thanks. Will do. Will also switch to "Launcher64 silent" as opposed to "AutoUpdate silent"

[bcurran3]

I believe my script is ready for prime time now:
https://community.chocolatey.org/package...ecs/17.0.0

I'm open to any suggestions, comments, or developer change requests.