Glad you got a result Katep don't.
Must second your appraisal of "Windows" mind boggling support in resolving this matter - I remain unaware of any official wisdom regarding the spontaneous murdering of MOVs.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
When I attempt to open some .MOV files instead of starting up Apple QuickTime Player (which is set as default program for this file type) 10 to 15 seconds Windows closes the folder containing the .MOV file without any explanation. Further attempts result in the same outcome. If I right-click and Delete the .MOV file quickly within a few seconds of opening the folder, Windows does remove it to the Recycle Bin. However, when I then try to Empty the Recycle Bin, Windows suddenly closes it without any explanation. Re-opening the Recycle Bin shows that the .MOV file is still listed. Attempting to Delete it has the same outcome.
This only occurs with some of my .MOV files; others work as expected. I haven't been able to distinguish any key differences between those that work and those that manifest this problem.
I am running a fully updated version on my Dell Inspiron 660S desktop PC and have the latest version of Norton Internet Security installed.
I have run a full system scan with Norton and no issues have been detected other than a small number of Tracking Cookies which Norton has removed.
Does any one have any thoughts on what may be the cause?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Glad you got a result Katep don't.
Must second your appraisal of "Windows" mind boggling support in resolving this matter - I remain unaware of any official wisdom regarding the spontaneous murdering of MOVs.
Ok everyone with this problem.....
i have done a factory reset on my husbands old pc and reinstalled windows 8. Windows 8 is fully updated and guess what. I CAN VIEW MOV FILES AGAIN. I am not going to reinstall 8.1 as I am certain this was the problem. The next update I do will be to windows 10
Yaaaaaayyyyyyy. Let there be fireworks and much rejoicing in the land.
It it has only taken one new Apple Mac for the husband to release a spare pc and three days to sort out once I started.
Thank you you windows for your kind and urgent assistance with this problem that cost me a fortune and stopped me pursuing my business for a month. I have no words for your kindnesses.
Hi leadhillsmike
i have not tried this as such, but I have tried viewing in list format instead of thumbnail and it still crashes.
I will try this tomorrow if I get a chance, however even if it does work,I cannot see it helping with the edit process as that programme needs to generate thumbs so you can see what you are editing.
The husbands Apple has arrived and is settling in nicely so I may have a crack at doing the factory reset on his old one and see what happens next,
You're not alone in that, Norwegian Blue. A poster on the Technet thread observed a November patch Tuesday resurgence of the issue - thinks it's apparent here too.
From what I have gathered so far, the issue is connected with the handling of metadata when Explorer scans files, generates thumbnails - no Microsoft confirmation of that, that I'm aware of though. Seems to me that which patch Tuesday sends the damage (August to November) may be down to MOV versions/variations - this has affected multiple versions of iTunes, Quicktime and similarly iPhones and pads of different ages; all at different times apparently.
One thing I did not try - curse my soul as I really should have thought of this before I took off the updates - go into control panel/ system/ advanced system settings/ performance, and uncheck show thumbnails. Might have been informative if it was enough to stop the crashes/errors and allow associated playback of MOVs. Can't test this now, as the laptop has gone back to client. Have you tried that Katep_don't?
I'd be inclined given the November link, to remove, one at a time, the November patches until hopefully, the error disappears - or take the lot off and if the error's cleared, put them back one by one, to identify the culprit. Bit of a slog and time consuming, but may deliver results; or considerable frustration. If removing the November stuff doesn't work - take of the two earlier updates too, to see if that finally clears it.
Just realised that the detail in the error box is a bit fuzzy and so hard to read so I've transcribed it below:
The exception Integer division by zero.
(0xc0000094) occurred in the application at location
0xb10baedf.
Click on OK to terminate the program
Hope this helps Microsoft to get to the root of this long-standing problem.
Thanks, Tony