#15 cloc 1.62 will not run on Windows 10 Pro x64

[Anonymous]

I just upgraded to Windows 10 Pro x64

cloc will no longer run. Popup error says:
cloc.exe- application Error
The application was unable to start correctly (0xcc0000142).

The Windows event log shows:

Faulting application name: cloc.exe, version: 0.0.0.0, time stamp: 0x51806f9e
Faulting module name: perl516.dll, version: 0.0.0.0, time stamp: 0x513f2741
Exception code: 0xc0000005
Fault offset: 0x00001427
Faulting process id: 0x1450
Faulting application start time: 0x01d1383b3a8dd1c3
Faulting application path: C:\Users\Judy\AppData\Local\Temp\par-4a756479\cache-1406671975\cloc.exe
Faulting module path: C:\Users\Judy\AppData\Local\Temp\par-4a756479\cache-1406671975\perl516.dll
Report Id: 97f391e8-401a-463d-ac93-ddb71cdabca6
Faulting package full name:
Faulting package-relative application ID:

My system is Windows 10 Professional (x64) (build 10586)

My previous system was Windows 7 Pro x64 SP1
This same executable for cloc worked fine.

My cloc was a download frm sourceforge 5/24/2015
original name of exe as downloaded was:
cloc-1.62.exe

I saw the note on sourceforge for v1.64 regarding possible malware,
so I do not want to try that

Windows 10 is nice and everything else is working fine on it.

Judy W

[Al Danial]

Windows 10... this may take a while to resolve since I don't have access to such a machine to build binaries on. Is there any chance you could put a Perl interpreter on your compter? That way you could run the cloc source code instead of relying on a binary. The "portable" version of Strawberry Perl can be installed without admin rights. And, once you have that, you can build your own binaries.

btw, the 1.64 exe is replaced with one I regenerated.

Finally, cloc now lives on github, at https://github.com/AlDanial/cloc and issues posted there will get my attention quicker.

[Anonymous]

Thank you for the response. However I won't need to install Perl.

I ran cloc again this morning to see if I could get some more error detail etc, and the sucker worked!

I had rebooted since the failure, but had not done any system work or config work or installs or anything.
So .... just a gremlin....?

I like the cloc app -- thanks for it!

[Al Danial]

re the 1.64 executable, if 1.62 didn't work on Windows 10, then 1.64 won't either. Both were built on the same Windows box.

[Al Danial]

Goood feedback, thanks. I'm relieve to know my existing method of making exes will work for Windows 10.