Looking at your batch file, if a SteamVR update updates the .dll's, a re-install (re-running your batch file) will simply pave over the new .dll's, leaving the old real...dll's. It seems that you actually want to pave over the (old) real...dll's with the new ones, before you overwrite them with yours, but your initial check will skip that part if your client is already installed. I was going to re-write the batches for my own reasons, but saw this issue, which will eventually cause out-of-date .dll's for all users. Note that you can check to see if your client is already properly installed by looking at the size of the .dll's.
In light of this issue, anyone having troubles currently should try: delete all your client files, re-install/file-verification of SteamVR, re-install your client.
Looking at your batch file, if a SteamVR update updates the .dll's, a re-install (re-running your batch file) will simply pave over the new .dll's, leaving the old real...dll's. It seems that you actually want to pave over the (old) real...dll's with the new ones, before you overwrite them with yours, but your initial check will skip that part if your client is already installed. I was going to re-write the batches for my own reasons, but saw this issue, which will eventually cause out-of-date .dll's for all users. Note that you can check to see if your client is already properly installed by looking at the size of the .dll's.