In C (and all C-like languages) the
keyword means "stop what you are doing and go around the nearest loop again".
Any code after the line containing the
instruction will never be executed - and most compilers generate either a warning or an error to tell you the "unreachable code" has been detected: ignore these at your peril! If it's a warning, it's serious, the compiler does know more than you (particularly when you are just beginning) and you should treat warnings as errors.
If it's an error, then it will prevent an executable file being produced, so whatever you execute after that compilation will not include any changes since your last sucessfull, error-free compile.
So in your code, count is never increased:
files[*total][SIZE - 1] = 0;
For the rest of you problem, you only check for a directory and count it if a parameter value is less than what I presume is a constant value - and since we have no idea what either of those are, we can't help.
So, it's going to be up to you.
Fortunately, you have a tool available to you which will help you find out what is going on: the debugger. How you use it depends on your compiler system, but a quick Google for the name of your IDE and "debugger" should give you the info you need.
Put a breakpoint on the first line in the function, and run your code through the debugger. Then look at your code, and at your data and work out what should happen manually. Then single step each line checking that what you expected to happen is exactly what did. When it isn't, that's when you have a problem, and you can back-track (or run it again and look more closely) to find out why.
Sorry, but we can't do that for you - time for you to learn a new (and very, very useful) skill: debugging!