iphone videos transferred to W10 no longer have thumbnail images nor video properties.

Things are getting from bad to worse. Just upgraded to iOS 18.2 and suddenly any videos transferred to Windows 10 no longer have thumbnail images nor video properties. Videos transferred before iOS18.2 do show thumbnail images and video properties... Any ideas how to solve this?

Airdop to MacBook shows thumbnail and properties. Copy via network to Windows 10 computer and they disappear. So iOS 18.2 is doing something to the videos so that thumbnails and properties can not be seen in Windows 10. Another "great" iOS upgrade as if Apple is intentionally pushing me towards another platform.

iPhone 15 Pro Max

Posted on Dec 24, 2024 8:12 PM

Reply
Question marked as Top-ranking reply

Posted on Dec 25, 2024 12:50 AM

You can remove that tag from all .mov movies in that folder with a command like:


exiftool -m -P -overwrite_original -api LargeFileSupport=1 -ext mov '-Keys:FullFrameRatePlaybackIntent=' .


But first do a test and see if it helps. That tag seems to take effect to movies with ≈85 fps or more in Sequoia QuickTime Player but its mere presence seems to currently confuse Windows. You can add that tag back with:


exiftool -m -P -overwrite_original -api LargeFileSupport=1 '-Keys:FullFrameRatePlaybackIntent=1' movie.mov


You can check the related tags with:


exiftool -a -G1 -s -n -fileOrder5 FileName -FullFrameRatePlaybackIntent -VideoFrameRate .


Or check almost all tags with:


exiftool -a -G1 -s -n -fileOrder5 FileName -api QuickTimeUTC=1 .


exiftool can be downloaded freely for various operating systems from (I have used MacOS package .pkg because it is easiest to install):


https://exiftool.org/

Similar questions

9 replies
Question marked as Top-ranking reply

Dec 25, 2024 12:50 AM in response to GranAlcazar

You can remove that tag from all .mov movies in that folder with a command like:


exiftool -m -P -overwrite_original -api LargeFileSupport=1 -ext mov '-Keys:FullFrameRatePlaybackIntent=' .


But first do a test and see if it helps. That tag seems to take effect to movies with ≈85 fps or more in Sequoia QuickTime Player but its mere presence seems to currently confuse Windows. You can add that tag back with:


exiftool -m -P -overwrite_original -api LargeFileSupport=1 '-Keys:FullFrameRatePlaybackIntent=1' movie.mov


You can check the related tags with:


exiftool -a -G1 -s -n -fileOrder5 FileName -FullFrameRatePlaybackIntent -VideoFrameRate .


Or check almost all tags with:


exiftool -a -G1 -s -n -fileOrder5 FileName -api QuickTimeUTC=1 .


exiftool can be downloaded freely for various operating systems from (I have used MacOS package .pkg because it is easiest to install):


https://exiftool.org/

Dec 25, 2024 1:03 AM in response to Matti Haveri

Before your message I downloaded exiftool for windows and after copying the videos in the same directory as exiftool.exe, typing this in the command line

exiftool -m -P -overwrite_original -Keys:FullFrameRatePlaybackIntent= *.MOV

proccessed all the videos

now I can see the metadata and thumbnails in Windows 10


The previous error was caused by having '-Keys:FullFrameRatePlaybackIntent=' with quotes in the command line instead of -Keys:FullFrameRatePlaybackIntent= without quotes. The quotes have to be removed.


Thanks for the suggestion!

Dec 25, 2024 1:41 AM in response to Matti Haveri

Indeed, as per my most recent message, removing the quotes did the job and changing the file name to wildcard * processes all the files in the directory. I further automated things by saving the "exiftool -m -P -overwrite_original -Keys:FullFrameRatePlaybackIntent= *.MOV" command (without quotes) with a text editor as convert.bat in the same directory. So now I have to just click on convert.bat without having to go to the command line. Very happy I got this resolved and thanx again for your help, prevented my Christmas day from being ruined through frustration.

Dec 25, 2024 1:05 AM in response to GranAlcazar

GranAlcazar wrote:

In addition to my earlier message I installed exiftool for windows but when I type this in the command line
exiftool -m -P -overwrite_original '-Keys:FullFrameRatePlaybackIntent=' output.mov
I get
Error : File not found - '-Keys:FullFrameRatePlaybackIntent='

Oh, just remove all those single quotes because that command does not need quotes at all:


exiftool -m -P -overwrite_original -api LargeFileSupport=1 -ext mov -Keys:FullFrameRatePlaybackIntent= .


(Mac and Linux use single quotes ' but Windows uses double quotes " . Some commands might need both mixed in a certain way. Some word processors are eager to use and replace curly quotes ” which do not work.)


And on Windows use CMD shell because PowerShell has issues with some commands.


https://exiftool.org/forum/index.php?topic=8137.0

Dec 25, 2024 12:19 AM in response to Matti Haveri

Thank you. That sounds like a reasonable explanation. Would that apply to a regular 60fps video?


It does not look straightforward to remove those tags. Are those commands to be executed via the mac command tool and can it be done on a range of videos instead of one by one? I tried the command line but it does not work. Are you referring to the EXIFTool in the app store which is 9.99 Euro?

Dec 25, 2024 3:59 AM in response to GranAlcazar

Sometimes it might be dangerous to use wildcards so I used "-ext mov" in the command so only .mov files in that folder are processed and files with other suffixes are left intact (or use "ext mov -ext mp4" to process those two file types. "--ext mp4" would mean that all files except .mp4 are processed). The period "." at the end of the command means "this folder" so the user does not need to give file names. At least on the Mac Terminal it works that way and your command does essentially the same.


I used quotes when initially testing this and forgot to remove them when done. Anyway I am glad you got it working.

Dec 26, 2024 6:46 AM in response to Matti Haveri

Your tip was golden because, as usual, when searching online for a solution you only find tips on how to fix general thumbnails problems, things you already know, not for this specific problem.

Agree, wildcards should always be used with caution. In my case, since I used a wildcard on the name and not on the extension (*.MOV) files with other suffixes are not affected.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

iphone videos transferred to W10 no longer have thumbnail images nor video properties.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.