Well... I've got all dependencies put together on the Github page: https://github.com/White-Tiger/T-Clock#requirements
You might also just use the static build...

I do highly recommend against manually placing any DLL file into system folders! Especially random "MSVCR100.dll" you've downloaded from the WWW... (which I suspect... otherwise I'd wonder where you got that from)
T-Clock also "only" offers one portable build... by which I'm saying that copying the VC++ Runtime to T-Clock can't work... there are files that are 32bit and others that are 64bit.. but the dependencies use the very same filename for both, 32bit and 64bit.
The second error actually suggests that you've put a 32bit MSVCR100 there.. a 64bit app is unable to load that though.

In the Miscellaneous menu, there is an option: Restore Previous Calendar (!! Global Win 10 Setting !!)

What is it supposed to do?
[...]

-Dypsis (May 24, 2017, 10:32 PM)

Since the Anniversary update? Nothing... before that.. It restored the good-old Windows Calendar you used to know pre-Win10

[...]
Then there was that damn nifty system calendar in 10 that - got moved from where it had been for years... - I never could figure out how to launch back when. How the hell White Tiger found the damn thing I'm not sure...but he did shortly after taking over the project.

-Stoic Joker (May 24, 2017, 06:27 AM)

Actually.. "before" since that's the "main" reason by which you forced me to fork T-Clock^^ And in fact.. I've used Google to "figure" it out :P But the old way got also broken by Windows 10's Anniversary update... which is why there's some ugly workaround now.

@topic well... I have to get my hands on a Creators update first.. my private PC is on the slow-ring just because those updates tend to break a lot of apps (even introduced memory leaks / Windows crashes) and my Windows partitions usually tend to be small... with about 2-3 GB free which is rarely enough for Windows to do a "major" upgrade and thus I'm stuck in an upgrade loop... (installing changes.... reverting changes...). This is also true for my VMs... and besides that... an upgrade also takes >30 minutes (probably an hour and more especially when reverting... since it'll take twice as much in those cases)

Is it the Creators update that's supposed to improve (fix) the update mechanism?

P.S. somehow.. I've never received an mail notification about this topic's creation...

Well.. one might first unckeck: "Start T-Clock when Windows starts"
And maybe delete the settings in the registry: