[CoolJosh3k]

What gets me is how this suddenly started and I read no reports of anyone else recently having this happen too.
Thanks for the info about that library file, I will look into it. Perhaps it got corrupted twice or something crazy?

[Potato Uno]

Start over from scratch with a brand new download of steamcmd and everything. That should download the proper library files.

[CoolJosh3k]

I already did that.

[CoolJosh3k]

Deleted steamclient.dll and used steamcmd to update and grab a new copy. Same problem still exists.
Is there a favoured alternate location to grab dedicated server files from?

[Potato Uno]

Try running the server on your own personal PC and see if the loadout appears.

Then zip the whole build and copy that over to the server box and try running it.

(I'm just talking out of my ass at this point.)

[CoolJosh3k]

Actually, I could copy over the steamclient.dll from my client. It also runs Windows at the moment.

[asherkin]

I still think the problem is that Steam was installed on the machine at some point.

[Potato Uno]

Originally Posted by asherkin I still think the problem is that Steam was installed on the machine at some point.

I'm also thinking this, especially if srcds works on his home PC and not on his server.

The last ditch resort is to reinstall the server OS and set everything up again (but only do it as a very last resort).

Actually OP.... How about you install the steam client on your server machine, log into it with your steam account, and then try loading the server? (And if that didn't work, go into the steam client beta and try again.)

[VoiDeD]

Or, more sanely, actually diagnose where steamclient is being loaded from with any of a million tools like procexp.

[CoolJosh3k]

Well I will be darned!
For some reason, it has started loading steamclient.dll from the Steam Client install, instead of the Dedicated Server install. Must have been some recent update.

I will pass this onto Eric in the TF Team, plus make a note of it on Reddit incase it helps others there.