IF you use the file manager,/copy utility, TERACOPY which works seamlessly with Win !0 file manager, when you transfer files (copy or move) ........... THE DATES WILL NOT CHANGE.
THAT IS A COMPLETE SOLUTION
Greg, Tamara presented a solution to solve the problem without needing anything extra. I can't speak for someone else, but it looks like she was solving the problem in the simplest way possible, without requiring any third-party tools and not asking a question.
The info she provided is absolutely correct and the same one others here, including me, have provided. I find this whole thread silly at this point. Pretty clear people are posting their complaints without reading the thread, because the solution has already been provided: People are looking at the WRONG FIELD. "Date Created" (or sometimes shown as "Created on" or just "Created") is the wrong field. As long as you use the "Date Taken" field, everything works fine. Depending on the tool used to copy or move a file, the Created field may reflect the date it was placed on the new drive (e.g., OneDrive) or not. It is up to the copying tool to determine that. The Date Taken field, on the other hand, ALWAYS reflects the date the picture was taken. Sort by that and everything is golden.
This brings me back to why I started this thread months ago. The Date Taken field does not always reflect the date on which a given photo was actually taken. Some (but not all) pictures in OneDrive default to a Date Taken of January 1, 1970 (1/1/70). This seems to be completely random, or at least I have not recognized any pattern as to why this may appear on one photo, but not another. I surmise that there is an issue in OneDrive code. Does anyone else have this issue and / or see that given date (1/1/70) associated with any of your collection?