phimseto wrote: ↑May 16th, 2017, 5:58 pm
Hi Walt, (also hello from my intro thread, too...saw your note, haven't had a chance to reply)...that error looks and sounds like a Steam platform error, which means that I need to direct you to their attention. Sorry we cannot help you, but hope you get it squared away soon!
Before I did that, though, were I in your shoes, I would also first try I would also verifying the files and rebooting Steam and/or my PC.
Update: After an entire afternoon spent troubleshooting yesterday, I tried something I wish I had done first--I downloaded the game to my wife's 15063.296 build of Windows10x64 (the commercially released "Creator's Update")--and what do you know--it fired up perfectly!
I'm 99% sure at this point that the problem lies within the Insider's builds Microsoft has published since then--I am now on build 16199 (installed yesterday) Insider's of Win10x64--and I cannot run the file. I even copied the game executable from the wife's machine and brought it over to my machine and replaced the original game executable--and no go! So the cause is not file corruption.
So....although the problem is one I have never seen before nor had happen before, I'm sure it is on *my end* and that the current Windows Insider builds are to blame for the faux incompatibility...I have reported this to Steam and also to Microsoft in the Insider's Feedback application! This one has been a doozy. Having said all of this, if anyone who reads this is running 16199 and Tides 1.1.0--please let me know...so I can move back to square one...!
Also wanted to add that in the "known issues" section for build 16199, I read the following:
Games such as Civilization VI may fail to launch on this build.
Of course, as luck would have it I don't have Civ VI, but I'll make the wild leap that Tides is "a game such as Civ VI" in some respect, somehow...

I have no clue as to what Microsoft means by that phrase...! (I must love beta-testing...! Hopefully, that doesn't mean I'm a sadomasochist...!)