Media Created property not showing-disappeared and cannot be set. Error 0xc00d3e8e

I would be nice if microsoft would fix all these file handling issues. It would seem they would make each version of windows an improvement over the last one, instead of making changes that can corrupt files or make them not useable or editable. Its a frustrating problem. It probable wont be fixed untill they decide to make a Windows 11 version (I’m sure it will be called something else). I tried using Windows 7 with these files and the file editing does work correctly. But then there’s other issues using 7... codecs, drivers and other stuff. Too bad microsoft went down the wrong path with windows 8, it could of been an awesome system using the best of 7 and the features of 10. Just a thought.

I would always recommend Windows 8.1 over 7 for better media type support, better security, etc.

It's irritating this is a regression bug: earlier versions of Windows 10 do not have the problem, but updates are mandatory and you can't opt out.

Regression bugs sometimes do not get fixed: Windows Vista allowed you to add ratings and comments to URL shortcuts, but this was broken in Windows 7 onwards and has never been fixed (you get a spurious permissions error when you try).

Another gotcha: you used to be able to search/filter image/media files in File Explorer, then select the results in the Search Pane, right click and update the metadata. So, if you spelled someone's name wrong, you could search an entire drive to find all affected files and right-click them in the Search pane to correct the tags.

That ability is broken from Windows 8 onwards: when you tag files from the search pane, the total length of all tags is restricted to a much lower limit than usual, so tags get silently truncated and/or deleted. This is a bug that can cause immense damage because you can bulk update tags, have them corrupted, then fail to notice your loss until after all your good backups have been overwritten with the corrupted files. Again, reported, but not fixed (although I haven't tested it recently).

Also, take care using Adobe products: Photoshop still has a serious metadata corruption bug that I reported in 2003 (as of 2017 when I quit my subscription after Affinity Photo became available on PC). I engaged in correspondence with a support person, provided sample files, was told it would be looked into, but nothing was done. I suspect other products such as Bridge may have the same problem (if they share the same code base), but I am not 100% certain.

The bug has the following characteristics (when updating metadata or saving a file after editing):

• Title field is copied into and overwrites Subject field.
• Fields containing Unicode characters are corrupted to ASCII "tofu". So, if your tags contain foreign language place names and personal names, they are destroyed.
• Tags are truncated to an arbitrary short length (I can't remember the length, might have been something like 32 or 64 characters). So, if you have hierarchical tags, they get truncated (destroyed).

I would hate going back to windows 7.... it doesn't have codecs for any .mp4 formats.  I have found that Adobe Bridge will change the dates to the correct date, but you have to enter it in the "origin date box".  It seems to work well.  As you can see I was able to enter the correct date for this .AVI file that can't be done on windows 10 in its current state.  This file had the origin date of 08/2018 before I edited it.  Nero has a photo viewer programs in its suite, but its based on Windows File Explorer, so it can't change any dates either.  The disadvantage of using Adobe Bridge is you have to do each file individually... a real pain in the rear when you have 1000's of pictures to work on!

I am also having the problem and have yet to find a work around.  I did try copying the files to a windows 7 PC, and seemed to be able to edit the data, but when I copied them back the media created date was back to showing 02/06/2036, and windows was using that date in its sort.

Yes, that is my experience as well and I should have been clearer about that in my previous post.

Windows 7/8 will allow you to put the correct date in, but Windows 10 will still read the date incorrectly, either displaying the wrong date (for me it is usually the current date) or a blank field.

The point about using Windows 7/8 as a workaround is you can set the date, repair corrupted date information and/or confirm that the dates in your collection have not been lost (this saves you going on a wild goose chase trying to correct dates that look broken but are not).

When you return the file to Windows 10, the date is still there and it remains correct, but you cannot see it or use it in File Explorer. So, you cannot use it for searches until the bug in Windows 10 is fixed, but at least you have created and maintained valid data.

Third party software should still be able to use the date correctly, but I have not yet found any third party software that can set it.

I have reported the problem on Feedback Hub, but there is no indication that they are "looking into it".

I am hoping to get a reply soon from the author of MP3tag: I have explained the issue, asked if MP3tag supports writing the Created Date field (by setting up a currently undocumented user-defined field) or whether it will be implemented at some point in the future.

This is very disappointing, because so many developers refuse to take metadata seriously despite it being a mission critical requirement.

I am also having the problem and have yet to find a work around.  I did try copying the files to a windows 7 PC, and seemed to be able to edit the data, but when I copied them back the media created date was back to showing 02/06/2036, and windows was using that date in its sort.