How to Update the Viveport Client When Troubleshooting
When troubleshooting issues with the Viveport client, it is recommended that you start by first ensuring that the client is updated to the most recent version. This fixes most common errors currently encountered by Viveport users. If you are having difficulty launching titles, also attempt to disable your antivirus and firewalls as part of your troubleshooting process.
The current Viveport client is Version 1.1.4.
When posting on the community about issues with Viveport please list the following in your post: client version, OS, any antivirus/firewall software currently installed, which titles (if any) are affected, and as detailed of a report as you can provide describing your specific issue. Providing this information is helpful for our engineering team.
In order to update your Viveport client to the latest version, launch your current Viveport client, navigate to the “Settings” pane, and select the “Check for Updates” button under the “About” header. Then follow the on-screen instructions to ensure that you have the current version 1.1.4.
Note: If you're client predates version r1060, it is recommended that you uninstall Viveport, and reinstall the current version via this download link. As of November 27th, 2017, we will be dropping support for clients older than v. 1.0.8889 (r1060). In order to access your content, you'll be required to download and install a newer version of the PC client.
Re: How to Update the Viveport Client When Troubleshooting
I would share a personal experience though. I was stuck at r1024 for a while thinking it was the most recent. I finally got an email saying I needed to update. Every time I clicked "Check for Updates" it said I'm at the current version, which obviously isn't true. Only after allowing the client to stay open for a little while (a few minutes) and trying again, did it finally offer a software update (I have no network issues or hardware issues). I suspect that launching the client and immediately going for the "Check for Updates" was the issue. I imagine the "Check for Updates" button doesn't actually reach out and check for updates, but perhaps the client gets an update notification pushed to it after certain things have loaded (the store, etc.) and once that is there, the "Check for Updates" button will offer the update it was notified of. Pure speculation, but perhaps needs a rework to help keep users up to date.
TLDR: If you click check for updates and don't see an update when you should, wait a few minutes and try again.