T-Clock Broken In Windows 10 Fall Creators Update (FIXED)

[Dypsis]

I get an error message that T-Clock cannot MSVCR100.dll even though I have it. I get the following message.

The code execution cannot proceed because MSVCR100.dll was not found.
Reinstalling the program may fix this problem.

I tried copying MSVCR100.dll to the T-Clock folder, but then I get the following message.

The application was unable to start correctly (0xc000007b).
Click OK to close the application.

I tried installing Microsoft Visual C++ Redistributable for Visual Studio 2017 x86 and x64, but with the same result.

[Curt]

If your system is running 64-bit Windows, also copy the file to C:\Windows\SysWOW64.

-maybe

[Dypsis]

If your system is running 64-bit Windows, also copy the file to C:\Windows\SysWOW64.

-maybe

-Curt (October 20, 2017, 01:57 AM)

Yes, my system is 64-bit.
Copy what file to C:\Windows\SysWOW64?

If you mean MSVCR100.dll, then it is already there.

[highend01]

Which T-Clock version are you using, the one from the x64 or the one from the Win32 folder
and did you really copy the correct x86/x64 version of the msvcr100.dll into that folder /
have the correct bitness version of the Visual C++ package installed?

[Shades]

With a piece of freeware, called: Dependency Walker, you can quickly find out what goes wrong with the loading of a certain dll. Like: 'Is the dll in the expected location?'  or  'Do you use the correct version of the dll?' 

For a non-programmer, the interface might be confusing to look at, but once you get used to it, it can be rather helpful.

[WhiteTigX]

Well... I've got all dependencies put together on the Github page: https://github.com/W...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.

[wraith808]

I do highly recommend against manually placing any DLL file into system folders!

-WhiteTigX (October 20, 2017, 10:30 AM)

Agreed!

[Dypsis]

Thanks guys.

The Windows 10 Fall Creators Update must have broken something with Microsoft Visual C++ 2010 Redistributable.

So, I downloaded both x86 and x64 versions of Microsoft Visual C++ 2010 SP1 Redistributable Package and the installer offered to do a repair.
T-Clock is now working. 

Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)



By the way...
What is the static build?

[WhiteTigX]

By the way...
What is the static build?

-Dypsis (October 20, 2017, 04:55 PM)

the one with _static in its name... I plan on making this the default^^
Basically it's statically compiled/linked, which means that all dependencies are "integrated" and thus no need for any Redistributable Package. The downside is usually higher load times and memory usage.. but in my measurements, it actually used less memory^^ Maybe because it's also using GCC instead of MSVC