Hi Will,
our start-up script relies on the yak.exe that comes with Rhino, rather than the the self-contained yak.exe from https://files.mcneel.com/
You seem to have the fix in 8SR16 RC3, so that should work for us.
We are rewriting our auto-update script to rely on PackageManger, rather than yak.exe. PM appears to be a lot more robust. Our updater is now going to copy the latest local yak packages from our network drive to c:/tmp, and point
Rhino.Options.PackageManager.Sources
to that location. Hopefully, this should also avoid situations such as this one:
Thank you for getting this fixed.
-Axel