There's a bug with dir, imfinfo and probably some other functions when they encounter a file with a modification date outside of a certain range.
In your case, it looks like you have a file with a modification date older than 1970. It's a perfectly valid file and matlab shouldn't choke on it but it does. I wasn't aware it occurred as well in 2014A, I thought it only appeared in 2014B because of their new datetime type. I've reported the bug to Mathworks. Whether it'll be fix anytime soon is unknown. Probably not, it's not even appeared in their bug database.
You have several workaround:
- Find the offending file(s) with windows explorer and edit it to change its modification time to now
- Use system(dir) (windows) system(ls) (unix) and parse the output yourself
- Use .Net (windows) System.IO.Directory methods, e.g. to get all files in a directory:
files = cell(System.IO.Directory.GetFiles(foldername));