error "Not a valid Win32 FileTime"

lvanzell posted this 27 May 2014

I installed Time-Lapse Tool on a Windows 8 64-bit computer. The installation completed without issue. When I run the tool, it opens normally, but after about 20-30 seconds, I get an error "Not a valid Win32 FileTime. Parameter name: fileTime". I used the button "Post to Developers". Can someone help?

Here is a screenshot of the error: Win32 FileTime Error

Last edited 27 May 2014

4 Posts
8 Comments
Order By: Standard | Newest | Votes
TimeLapseTool posted this 28 May 2014

Thank you for your feedback! We aware about this bug and it was fixed recently, When do you report it? Could you check which version of the Tool you are running? You can see program version in about box. to open about box just click on time-lapse tool log at the bottom left corner.

Best regards,

Time-Lapse Tool team

153 Posts
lvanzell posted this 28 May 2014

I am using version 2.0.1201

4 Posts
TimeLapseTool posted this 28 May 2014

Thank you for information! We are working to fix the issue.

In the meantime you could avoid this error by ejecting one of your drive with non-NTFS or non-FAT filesystem (probably DVD-ROM disk in the drive). You could copy these files to hard-drive before starting the program.

Best regards,

Time-Lapse Tool team

153 Posts
lvanzell posted this 28 May 2014

I have no drives with non-NTFS or non-FAT filesystems - all connected drives are NTFS, and there is nothing in the DVD-ROM drive. Your suggestion is not a solution.

4 Posts
TimeLapseTool posted this 28 May 2014

Card-reader or USB stick maybe?

153 Posts
lvanzell posted this 28 May 2014

There was an older, external card reader connected. I disconnected it and then the TimeLapse Tool worked a bit longer. I was able to open a sequence of images and try out some settings. But when I clicked on Directional Blur, I got the same "Not a valid Win32 FileTime" error. Total time the TimeLapse Tool worked before crashing: 3 minutes.

This is getting old very quickly. It is strange to me that this program can be affected by card readers or USB sticks or non-FAT or non-NTFS filesystems.

4 Posts
TimeLapseTool posted this 29 May 2014

Non-NTFS or FAT filesystem is the only one of possible reasons. Another possible reason is a incorrect timestamp value of one of the file (maybe drive filesystem has errors). Anyway we are working on fix to handle such situations.

153 Posts
TimeLapseTool posted this 29 May 2014

Could you give a try to updated version from http://timelapsetool.com/Home/Download? It should handle such cases gracefully now.

153 Posts