I had the same error earlier, I can confirm this fix works. My best guess is that the new update updates the apex content but not the core game content on the experimental ports, meaning the apex content has an argo dependancy but the base game content doesn't. Either way, this can be fixed using the legacyports beta branch, even though the wiki says it is for windows-experimental port compatibility.