jamtart6 replied on

Thanks, I have just re-named my 64 bit version of MFMP4SRCSNK.DLL 

I cannot find the Media Player directory and when I look in troubleshooter, I can only right click and run or left click which opens a new dialog box that wants to trouble shoot for me - is that what I need to click? I have Windows Media Player Library, Windows Media Player DVD and Windows Media Player Settings as options. 

Be the first person to mark this helpful

Abuse history


Win7ine replied on

Use the Windows Media Player Library Troubleshooter
Be the first person to mark this helpful

Abuse history


RobertGr replied on
The automatic updates from Microsoft today (14Feb2015) seem to have solved the problem.  It took a while, but thank-you Microsoft.
Be the first person to mark this helpful

Abuse history


Win7ine replied on

The automatic updates from Microsoft today (14Feb2015) seem to have solved the problem.  It took a while, but thank-you Microsoft.

It certainly is NOT! RESOLVED for me. I have renamed both mfmp4srcsnk.dll.old in System32 and SYSWOW64 to their working names and immediately get Explorer to crash when listing *.MOV

Log Name:      Application
Source:        Application Error
Date:          14/02/2015 12:07:05
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Computer-Name
Description:
Faulting application name: Explorer.EXE, version: 6.3.9600.17415, time stamp: 0x54503a3a
Faulting module name: mfmp4srcsnk.dll, version: 12.0.9600.17483, time stamp: 0x545c1ca3
Exception code: 0xc0000094
Fault offset: 0x00000000000aaedf
Faulting process ID: 0x1218
Faulting application start time: 0x01d0484c80a589e1
Faulting application path: C:\WINDOWS\Explorer.EXE
Faulting module path: C:\WINDOWS\System32\mfmp4srcsnk.dll
Report ID: fdac1aef-b441-11e4-8626-00224d98bc6d
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-14T12:07:05.000000000Z" />
    <EventRecordID>209188</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Computer-Name</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Explorer.EXE</Data>
    <Data>6.3.9600.17415</Data>
    <Data>54503a3a</Data>
    <Data>mfmp4srcsnk.dll</Data>
    <Data>12.0.9600.17483</Data>
    <Data>545c1ca3</Data>
    <Data>c0000094</Data>
    <Data>00000000000aaedf</Data>
    <Data>1218</Data>
    <Data>01d0484c80a589e1</Data>
    <Data>C:\WINDOWS\Explorer.EXE</Data>
    <Data>C:\WINDOWS\System32\mfmp4srcsnk.dll</Data>
    <Data>fdac1aef-b441-11e4-8626-00224d98bc6d</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

1 person found this helpful

Abuse history


kirisute replied on

for those that have no wish to run command prompts:

download this:

http://www.nirsoft.net/utils/shexview.html

run the program and browse down the list til you find MF MPEG4 Property Handler.

scroll across and check the file name is correct.

right click the listing and choose DISABLE SELECTED ITEMS

that's it..job done!

no need to rename or anything. and you can easily turn it back on again if need be.

5 people found this helpful

Abuse history


MikeJSh replied on

A great simple solution this solved the problem for me . Many thanks.
Be the first person to mark this helpful

Abuse history


SCGHSCGH replied on

The automatic updates from Microsoft today (14Feb2015) seem to have solved the problem.  It took a while, but thank-you Microsoft.

Definitely still a problem for me.  Can you please tell us which updates you have installed and if you have installed the optional updates?

For now, I am continuing with the work-around of renaming the file as .old.  However - the work-around still doesn't allow editing of the .mov files (crashes Movie Maker & Adobe Premier), and doesn't show the thumnails in for .mov files (so I have to watch each file to see what it is).

Be the first person to mark this helpful

Abuse history


Davidrt333 replied on

The automatic updates from Microsoft today (14Feb2015) seem to have solved the problem.  It took a while, but thank-you Microsoft.

Definitely still a problem for me.  Can you please tell us which updates you have installed and if you have installed the optional updates?

For now, I am continuing with the work-around of renaming the file as .old.  However - the work-around still doesn't allow editing of the .mov files (crashes Movie Maker & Adobe Premier), and doesn't show the thumnails in for .mov files (so I have to watch each file to see what it is).

For moviemaker try converting to a MP4 , we use formatfactory.

Also try changing default prog for .mov file to use VLC assuming you have VLC installed which may fix thumbnail.

You can also use an earlier version of the .dll file

see the other forum

https://social.technet.microsoft.com/Forums/en-US/abab222f-51b9-4068-af98-47339c0bb5f2/windows-81-file-explorer-crashes-repeatedly-with-iphone-movies-mov-files?forum=w8itproinstall

Be the first person to mark this helpful

Abuse history


Marc51 replied on

I'm still having this problem too.  As soon as I hover over the MOV file, explorer crashes.  Isn't Microsoft going to release an update to fix this?  I don't understand how they wouldn't address this since their update is causing this.
Be the first person to mark this helpful

Abuse history


Davidrt333 replied on

I'm still having this problem too.  As soon as I hover over the MOV file, explorer crashes.  Isn't Microsoft going to release an update to fix this?  I don't understand how they wouldn't address this since their update is causing this.

I agree ! It looks like we will have to fork out £85 to raise this as a support case. In a large

organisation we cannot keep going round changing individual PCS nor do we want to push out scripts.

I assume this forum was set up by MICROSOFT and being monitored by themselves (I have referred this to them) so they could at least acknowledge they are working behind the scenes to bring out a patch.

Be the first person to mark this helpful

Abuse history