5/3/03 - FrooniumDrive - Usually, failure to register a DLL means that there is either a missing dependency (like msvcrt.dll) or an out-of-date dependency.

Here's some things to try:

1. First, try to manually register the dll's in question. For each of the unregistered files, go to the command line, and type (using wmm2ae.dll for this example): regsvr32 "C:\Program Files\Movie Maker\wmm2ae.dll"

If this succeeds, then you should be good to go. If it doesn't, then...

2. Try to determine what dependency is out of whack. Grab a copy of "depends" (http://www.dependencywalker.com/), and open one of the DLLs that doesn't register. When you examine the results, you will probably find that one of the dependacies is either missing or "old". If you can't find a suitable copy of the problem file, post back and someone on the group will send you a copy :)

Dependency Walker

Summary

Movie Maker 2, version 2.0.3312.0, uses about 50 to 80 dynamically linked modules, depending on the computer and what activities are being performed. The first set of modules below, in alphabetical order, are those that are in the Movie Maker folders or are linked to by MovieMk2.exe. The info about issues and resolutions comes from all posts on microsoft.public.windowsxp.moviemaker since the beta release.

After the first list, there is another shorter one listing modules associated with Movie Maker or mentioned in postings, but not seen as being active when Movie Maker is running.

Modules Actively Used by Movie Maker

ADVAPI32.DLL (statically linked also) - Windows/System32 folder - 8/29/02 - 558,080 size - Advanced Windows 32 Base API (WARNING - don't touch this DLL)

2/16/03 - Murph - I tried renaming advapi32.dll to advapi32.dll_. What resulted was a complete inability to access C drive. When I do a normal boot, it just recycles the boot over and over. If I boot from floppy or the Windows XP® CD, it does not recognize C:. Since I can't get to c:, I can't rename the file back again. I have the sinking feeling that I have days of work ahead to spend reinstalling my system, but humor me... is there anything I could try to get C: back again? And just out of curiousity, what likely happened when I renamed the file? > 2/16/03 - John De Angelis - No, advapi32 is a required system file - don't do anything to it! If you see that your version is older, then I would assume that you're missing a service pack.

APPHELP.DLL (opened when opening a project) - Application Compatibility Client Library

ATL.DLL - ATL Module for Windows NT (Unicode) - version 3.0.9435.0 - in c:\Windows\System32 - 74,810 bytes dated 8/29/02 (note - also have other copies of different versions of ATL.DLL in other folders)

3/4/03 - Mark Hions - the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{44EC053A-400F-11D0-9DCD-00A0C90391D3}\InProcServer32\(default) was pointing to ATL.DLL but in the wrong folder. I changed the string to point to D:\WINDOWS\SYSTEM32\ATL.DLL and crossed my fingers. This time, the install of WMM worked flawlessly! I can now use all titles, and I've even discovered more transitions than before (the film aging and frame rotation effects I've never seen before today).

3/1/03 - Laserman - I was seeing the same MM2 crashing when working with transitions. A few days ago I added a second video card and monitor for multi-monitor support and the crashes have stopped. My crashes were ATI.dll related

1/12/03 - Gern Blenston - Holy cow, that actually worked!!! I looked and there was some dll, I think it was atl.dll, and it was looking for it in an old directory of a program I removed; DiskAlert. I found out that it was also in the system32 dir so I pointed it there, reinstalled Movie Maker 2 and it's there!

AVIFIL32.DLL (statically linked also) - Microsoft AVI File support library

BROWSEUI.DLL (opened when opening project) - Shell Browser UI Library

CFGMGR32.DLL (on desktop, not laptop) - Configuration Manager Forwarder DLL

CLBCATQ.DLL - ??

COMCTL32.DLL (statically linked also) - User Experience Controls Library - SP1 and MM2.0 - 921,088 bytes dated 8/29/2002 (> SP2 - Common Controls Library - version 5.82.2900.2180 of 8/4/04 - 611,328 bytes ) - It's what Windows uses to generate Dialog Boxes, List boxes etc.

3/21/05 (forum) - I was using MM one day, then I switched to detail view and when I import a video It freezes for a while, and then drops me an error message and MM closes. So everytime when I try to open MM again, it reloads the detail view and the video that i've imported... so it freezes again and shows again that message. So I have to do something: 1- delete properties that make MM reload my videos and switch back to icon view. 2- fix the error that make MM fail... I try to remove the videos from the source directory and nothing changes. > Move the collection database file out of the picture.... > Great! it works... but if i may... what can I do with that error? It happened with any element shown in Detailed view: collection, video effects, transitions... the error displayed is

EventType : BEX P1 : moviemk.exe P2 : 2.0.3312.0 P3 : 3e038613 P4 : comctl32.dll P5 : 6.0.2900.2180 P6 : 41252bd1 P7 : 0006c82c

9/1/04 - Andrew - Ever since I installed SP2 MM2 keeps closing for no reason (.... and his error message had essentially the same info as Brian's before SP2).

5/28/04 - Brian - Every time I try and open MM the program shuts down immediately and I get the message: EventType : BEX P1 : moviemk.exe P2 : 2.0.3312.0 P3 : 3e038613 P4 : comctl32.dll P5 : 6.0.2900.2082 P6 : 4034271d P7 : 0006c832 P8 : c0000409 P9 : 00000000

COMDLG32.DLL (statically linked also) - Common Dialogs DLL

COMRES.DLL - ??

CRYPT32.DLL (statically linked also) - Crypto AP32

CSCDLL.DLL (opened when opening project) - Offline Network Agent

CSCUI.DLL (opened when opening project) - Client Side Caching UI

DAVCLNT.DLL (opened when JPG files imported/previewed/added to timeline) - Web DAV Client DLL

DCIMAN32.DLL (opened when JPG files imported/previewed/added to timeline) - DCI Manager

DDRAW.DLL (opened when JPG files imported/previewed/added to timeline) - Microsoft DirectDraw

DDRAWEX.DLL (opened when JPG files imported/previewed/added to timeline) - Direct Draw Ex

DEVENUM.DLL - Device enumeration

DRPROV.DLL (opened when JPG files imported/previewed/added to timeline) - Microsoft Terminal Server Network Provider

DSOUND.DLL (opened when JPG files imported/previewed/added to timeline) - DirectSound

DXTMSFT.DLL (opened when JPG files imported/previewed/added to timeline) - DirectX Media -- Image DirectX Transforms

DXTRANS.DLL (opened when JPG files imported/previewed/added to timeline) - DirectX Media -- DirectX Transform Core - in C:\Windows\System 32 - 194,560 bytes dated 8/29/02

2/7/03 - Brian Ahern - I got another crash with DXTRANS.DLL but this only occured once, and happened at around 40% of the way through the save.

EDIE.DLL Edie Support Library from Real Solutions - this may be opened to support DLL Explorer, being used to see which modules are open.

GDI32.DLL (statically linked also) - GDI Client DLL

GDIPLUS.DLL (statically linked also) - GDI Client DLL

2/3/04 - Jim Boyd - I have downloaded Movie Maker 2 but cannot get it to run, every time I launch it I get an error message 'Error signature. App Name: Moviemk.exe App Ver:2.0.3312.0 ModName:gdiplus.dll ModVer:5.1.3010.0 Offset:000f635a.

HHCTRL.OCX - Microsoft HEML Help Control

IDLEMON.DLL - Idle Monitor DLL

KERNEL32.DLL (statically linked also) - Windows NT BASE API Client DLL

KSUSER.DLL (opened when JPG files imported/previewed/added to timeline) - User CSA Library

LINKINFO.DLL - Windows Volume Tracking

MIDIMAP.DLL - Microsoft MIDI Mapper

MLANG.DLL - Multi Language Support DLL

MOVIEMK.EXE - Movie Maker main executable

9/25/03 - Carl Kresge - When I exit Movie Maker, I get the following error message: Microsoft Visual C++ Runtime Library Runtime Error! Program: C:\Program Files\Movie Maker\moviemk.exe - R6025 - pure virtual function call

MPR.DLL (opened when JPG files imported/previewed/added to timeline) - Multiple Provider Router DLL

MSACM32.DLL - Microsoft ACM Audio Filter

MSACM32.DRV - Microsoft Sound Mapper

MSADP32.ACM - Microsoft ADPCM CODEC for MSACM

MSASN1.DLL - ASN.1 Runtime APIs

MSCTF.DLL - MSCTF Server DLL (on desktop, not laptop)

MSDMO.DLL - DMO Runtime

MSGINA.DLL (opened when JPG files imported/previewed/added to timeline) - Windows NT Logon GINA DLL

MSIMG32.DLL (statically linked also) - GDIEXT Client DLL

MSLBUI.DLL - LangageBar Add In (on desktop, not laptop)

MSVCRT.DLL (statically linked also) - Windows NT CRT DLL - version 7.0.2600.1106 - C:\WINDOWS\SYSTEM32 - 323,072 bytes, 8/29/02 - (note, have other copies of different versions in acrobat reader folder, Lotus fast view, CPlusPlus runtime, Cpmmectix Album Maker, etc. - lots of places)

1/9/03 - Richard Cue - running Windows XP® Pro. I ran into the problem with MM2 complaining about Microsoft Visual C++ Runtime library. Since I have Visual Studio .Net installed on my machine, I thought that perhaps by upgrading to the latest version of VS .Net this would correct the problem (I assume the problem is related to MSVCRT.DLL and so I hoped a new version would be installed with VS .Net Beta-003 > 1/9/03 - Kristen Whalen - This is exactly what I needed :) Let me setup a machine and see if I can reproduce your issue. > 1/14/03 - Richard Cue - Hi Kristen, Any progress on trying to resolve this. > 1/14/03 - Kristen Whalen - I've contacted Ron offline to get some specific information regarding his crash -- I'll post back if we manage to track down the source of the issue. > 1/16/03 - Ron - Still waiting to be contacted "offline" - same problem persists - HELP PLEASE

10/24/03 - Walter Cannon's weblog says: "... I found the problem, and it had nothing to do with office 2003, although something must of changed with the final versions of Movie Maker and Producer. The problem was with dxtmsft3.dll which is a dx3d transformation. I had this dll on the p4 machine that I upgraded from a windows Me platform but it wasn't included on the new 2.8 g HP Pavilion which came native with XP. Microsoft or HP must leave it out of the install. Anyway, unregistering this dll fixed the exception I was getting in msvcrt.dll. As far as I can tell I don't seem to loose any functionality not having this DLL. Now since XP was installed on this system since Microsoft released it, something in the environment changed. If I had to guess I think the new Microsoft Plus media update changes the way Movie Maker and Producer handle fx extensions. The way I found this was to use the profiling tool depency walker and ran the same test on both p4 systems. In the process, I also found Microsoft has a free download of windows XP debugging tools. So ends the saga.

MSVFW32.DLL - Microsoft Video for Windows DLL

MSXML3.DLL - MSXML 3.0 SP 3

MYDOCS.DLL - My Documents Folder UI

NETAPI32.DLL - Net Win32 API DLL

NETRAP.DLL (opened when JPG files imported/previewed/added to timeline) - Net Remote Admin Protocol DLL

NETUI0.DLL (opened when JPG files imported/previewed/added to timeline) - NT LM UI Common Code - GUI Classes

NETUI1.DLL (opened when JPG files imported/previewed/added to timeline) - NT LM UI Common Code - Networking classes

NTDLL.DLL - NT Layer DLL - version 5.1.2600.1106 - C:\WINDOWS\SYSTEM32 - 668,672 bytes, 8/29/02

9/17/03 - Choo.comonrad - Movie Maker hangs on me about 2 out of every 5 times that I select a clip in the video bar or after I finish adjusting its volume. It gives me a dialogue box that says it needs to close with the following error message: "AppName: moviemk.exe AppVer: 2.0.3312.0, ModName: ntdll.dll, ModVer: 5.1.2600.1217 Offset: 00081bf" > 10/14/03 - Dieter - I have the exact same error message. Same behavior etc...

4/2/03 - Rich Bell - If I rapidly click on clips within a collection, I get the following error: Faulting application moviemk.exe, version 2.0.3312.0, faulting module ntdll.dll, version 5.1.2600.1106, fault address 0x00001baa. If I pause for several seconds between clicks, it doesn't error. (Windows XP® SP1, NVidia TI4400 video card, Audigy sound card, AMD 1800 processor, 512 MB RAM)

3/18/03 - Rob - 'stuttering audio' when printing back to DV tape? (no dropouts but hick-ups) - MM2 crashes while rendering (just before writing to tape or disk) - I Enabled the Codecs (Cyberlink & Cmedia) but got no improvement... (The file to be processed is reasonably short (6 minutes) with not too many edits) - I get the following message: AppName: moviemk.exe AppVer: 2.0.3312.0 - ModName: ntdll.dll - ModVer: 5.1.2600.1106 - Offset: 00001d26 > PapaJohn - See Kristin's 11/13/02 response to the previous instance > Rob - Although there is no satisfactory solution there is a way to work around the problem. The cause is the cmedia driver that still is no good. In order to render to Tape or HD, 'remove all audio material that was added on top of the original DV source'. I have to find out if I can add audio with other apps or with a file that contains no edits in MM2. (I will let you know). > 3/20/03 - Rob - I disabled the codecs I could find (Cyberlink) by renaming them. I don't know how to unregister the codecs. The C-media codec was no longer on the system (...) after i updated the drivers yesterday. This gave no improvement. I'd be happy to try anything else...

11/13/02 - Rob - the clips play fine, but when I place them on the storyboard/timeline and play, the program quits and the message "Windows Movie Maker has encountered a problem and needs to close. > 11/13/02 - Kristin Whalen - This usually occurs when you are importing, previewing or publishing source content that uses the driver from C-Media (cmaudio.ax). Check out the following KBarticle, and see if it helps: http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q317358

NTLANMAN.DLL - (opened when JPG files imported/previewed/added to timeline) - Microsoft Lan Manager

NTSHRUI.DLL - Shell extensions for sharing

NTVDM.DLL - Microsoft Lan Manager

NTVDM.EXE

NTVDMD.DLL

ODBC32.DLL (opened when JPG files imported/previewed/added to timeline) - Microsoft Data Access - ODBC Driver Manager

ODBCINT.DLL (opened when JPG files imported/previewed/added to timeline) - Microsoft Data Access - ODBC Resources

OLE32.DLL (statically linked also) - Microsoft OLE for Windows

OLEAUT32.DLL (statically linked also) - Microsoft OLE 3.50 for Windows NT(TM) and Windows 95(TM) Operating Systems

PixelanBonusPack.dll

PixelanCoolFxPack.dll

PixelanPipFxPack.dll

PixelanSoftFxPack.dll

QASF.DLL (opened when saving a file to disk in WMV format, but not to DV-AVI) - DirectShow ASF Support - the file is in the c:\Windows\system32 folder, with a date/size of 12/11/2002 - 241,664 - version 9.0.0.2980.

The version on both of my laptops, one running the Home edition and the other running the MCE version - each with SP2 installed - is 10.0.0.3646, 221,184 in size and dated 8/11/04. My desktop with Home edition has the same version. >> the laptop is now up to version 10.0.0.3650 of 10/11/04 (same size).

8/19/03 - stuart - While trying to capture a movie with MM2, I received an error that said MM2 had to close. When I looked in the event viewer, the report it said Faulting module qasf.dll version 9.0. I also noticed I could not manually capture any video. The size of the file would stay at 3Kb, but the minutes would pass.

QCAP.DLL - DirectShow Runtime - opened when JPG files imported/previewed/added to timeline

QDV.DLL this file contains the Digital Video decoder and encoder - it is opened when saving to a DV-AVI file

10/12/04 - Rupert - I've just spent all evening creating a .avi edited file that I hoped to re-save on my camcorder tape. The .avi I created is about 40mins long and about 8GB. However, when I came to import it into Movie Maker I can only see the first two clips (around 30 sec long each). The 8GB file plays perfectly in Real Player - showing all 40 edited minutes. However, since only the first 2 clips are visible in Movie Maker then I can't create my 40 min timeline and then save it back to my camcorder tape. It's almost as if the addresses to the other clips have been lost somehow. Please tell me I don't have to recreate the whole 8GB edited file again !!! > Rehan - Lets rule out that it is not because of DLL mis-registration. Execute the following line in Start -> Run dialog regsvr32 %windir%\system32\qdv.dll - This should result in success message. Now try importing the file again. > Rupert - I don't know what that Start|Run command did but it worked straight after that. I'm delighted - thanks very much. What does that command do? > Rehan - The command was to re-register the proper DLL for handling DV AVI files. Some other applications register their own version of the DLL to handle this functionality. However this makes everything else to start using their DLL breaking their functionality. The above command gives the control back to the official DLL.

QDVD.DLL - DirectShow DVD PlayBack Runtime

QEDIT.DLL - Direct Show Editing - c:\Windows\System32 - 511,488 bytes of 8/29/02 > SP2's file is version 6.5.2600.2180, 562,176 bytes of 8/4/04 >> intervideo was the problem

1/13/08 - Dan emailed to say that his IE7 crashed movie maker 2... so he created a batch file with these 3 lines...

regsvr32 qedit.dll /s /u

"C:\Program Files\Movie Maker\moviemk.exe"

regsvr32 qedit.dll /s

He opens Movie Maker by running the batch file and doesn't have to remember to unregister and register the DLL each time. The batch file doesn't run regsvr32 qedit.dll /s until Movie Maker is closed.

6/1/07 forum post... use Tools > Options > Compatibility tab > turn off the video filter ffdshow.ax.

3/18/05 - when I start Movie Maker it crashes straight away... faulting application moviemk.exe, version 2.1.4026.0, faulting module qedit.dll, version 6.5.2600.2180, fault address 0x0001a513 >>

1/2/05 (Ray) - Faulting application moviemaker.exe 2.0.3312.0 Faulting module qedit.dll, version 6.5.2600.2180 fault address oxoo1b2af > (Microsoft) There's a component in Direct Show which caches the information about the effects and transitions that are registered upon your system. Unfortunately there's a bug in that component which causes it to crash if you have a lot of transitions and effects installed. MovieMaker calls this routine on startup which is why you're seeing MovieMaker crash.

Fortunately there is a workaround by doing something like the following.

1. Find an application which has registered a bunch of effect filters.

2. Rename the directory that the application is installed into to something else - which will temporarily cause those effect filters to fail to load.

3. Start MovieMaker. As less effects are successfully created, MovieMaker should hopefully launch.

4. Rename the directory in step 2 back to it's original name so the original application still works.

5. Start MovieMaker again. As everything was successfully cached in step 3 it shouldn't try to recache things so it should continue to work..

9/6/04 - Franz - I get an error message when starting MM2: AppName: moviemk.exe AppVer: 2.1.4026.0 ModName: qedit.dll ModVer: 6.5.2600.2180 Offset: 0001a513 > ... I have solved my problem. Two Intervideo-AX-Files (ivi*.ax) in an "forgotten" Intervideo-Folder as well as in c:\windows. After deleting them Movie Maker 2.1 is working!

5/6/04 - Philip - I am receiving a qedit.dll error when I launch Movie Maker. AppName: moviemk.exe AppVer: 2.0.3312.0 ModName: qedit.dll ModVer: 6.5.1.900 Offset: 00018c80 - I have loaded WMM 2 and DirectX 9.0b. I also have WMP 10 loaded.

3/23/04 - Diane - I have tried to install movie maker 2, which it did as version 5.1 build 2600.spsp2.030422-1633: Service Pack 1 movie maker version 2.0.3312.0 . Every time I open it I end up with the error message "Window Movie Maker has encountered a problem and needs to close. The data in the error report says--- AppName: moviemkerror.exe AppVer: 2.0.3312.0, ModName: qedit.dll ModVer: 6.5.1.900 Offset: 00018ff3, I have tried reinstalling it, unistalling it... installing it with copying and pasting from a movie maker2 that worked on another computer, all to no avail, it still keeps closing.

11/11/03 - Tim - I am compiling a slideshow in WMM. I constantly get told that WMM has encountered an error and must close. The error report details are as follows: AppName: moviemk.exe, AppVer: 2.0.3312.0, ModVer: 6.5.1.900, ModName: qedit.dll, offset: 0000ad31 > Richard - I am having the same error, I also get it when I go to my pic folder on my other drive I have? I was thinking maybe a ram problem but with 256 I don't think so... > I doubt that this applies, but just in case... If you have DirectX 8.1 or earlier installed and have two programs trying to use this dll at the same time, the second program will crash. This is a forced condition by Microsoft... I would suggest that you do the following (if you have not already done so). Install the latest version of DirectX from Microsoft (I think the latest is Ver 9.0b). Install Windows Media Player 9.

2/10/03 - Brian Ahern - installed DirectX9 and this resolved the problem with QEDIT.DLL and seems to have stopped all crashes. I still can't produce a movie, but I think it runs out of real memory before it finishes. I end up with a movie that is incomplete. I'm going to buy another 512Mb of RAM and see if that helps. > 2/11/03 - OO - I tried DirectX9 to no avail. I thought mem paging should prevent an app running out of real mem? If this is the problem it could explain my issue - but I am not sure it is.

2/8/03 - heattreater - I found out what caused the crash. It's the beta version of WinDVD Creator from Intervideo. I uninstalled it and qedit.dll does not crash MM2 on load.I have no idea if the released version has the same bug.

2/7/03 - heat treater - crash at load time - ModName: qedit.dll ModVer: 6.5.1.900 Offset: 00018c80

2/7/03 - Brian Ahern - tried renaming QEDIT.DLL, but Windows XP® is too clever for that. As soon as I did it, the DLL was replaced with a file of the same attributes. Anyway, I tried saving again and got the same crash with QEDIT.DLL. I tried forcing the movie to save with a maximum size. Again, the problem always occurs at the end of producing the movie. At one point the movie saved slightly more than normal before crashing. (an extra 8 photos made it). It is a pain when it crashes because it always seems to happen at around 90% (which takes around 30 mins to get this far).

2/6/03 - heat treater - I'm having qedit.dll crash MM2 at startup. - ModVer: 6.5.1.900 Offset: 00018c80 - I tried DirectX 8.1 or 9.0 they both crash. Checked for another instance qedit.dll loaded by another app, using system info. Only time I can see it load is when I start up MM2 and Crash. This bug occurs on two systems. Other systems seem to work fine. Tried changing Video board of system that worked but I have the same error. It does not seem to be a video driver problem. Running it through Visual Studio Debugger I get a unhandled exception error.

2/6/03 - OO - BINGO! - I renamed the two instances of qedit (win32 and servicepack files) to qedit.dll_ and I can now save in DV- AVI, send to camcorder..etc...

QUARTZ.DLL (opened when JPG files imported/previewed/added to timeline) - DirectShow Runtime

QVPHOOK.DLL - ?? (on desktop, not on laptop)

RPCRT4.DLL (statically linked also) - Remote Procedure Call Runtime

S32EVNT1.DLL

SAMLIB.DLL (opened when JPG files imported/previewed/added to timeline) - SAM Library DLL

SECUR32.DLL (statically linked also) - Security Support Provide Interface

SERWVDRV.DLL - Unimodem Serial Wave driver - (on desktop, not laptop)

SETUPAPI.DLL - Windows Setup API

SHDOCLC.DLL - Shell Doc Object and Control Library

SHDOCVW.DLL (opens when opening project) - Shell Doc Object and Control Library

SHELL32.DLL (statically linked also) - Windows Shell Common DLL

SHGINA.DLL - Windows Shell User Logon

SHLWAPI.DLL (statically linked also) - Shell Light-Weight Utility Library

STI.DLL - Still Image Devices client DLL - (on desktop, not laptop)

SXS.DLL (opened when JPG files imported/previewed/added to timeline) - Fusion 2.5

TABHOOK.DLL - Wacom Technology TabHook

TSAPPCMP.DLL - Terminal Services Application Compatibility DLL

TSD32.DLL - DSP Group TrueSpeech(TM) Audio Encoder & Decoder

TSSOFT32.ACM - DSP Group TrueSpeech(TM) Audio Codec for MSACM V3.50

UMDMXFRM.DLL - Unimodem Tranform Module - (on desktop, not laptop)

URLMON.DLL (statically linked also) - OLE32 Extensions for Win32

USER32.DLL (statically linked also) - Windows XP® USER API Client DLL

USERENV.DLL - ??

UXTHEME.DLL (statically linked also) - Microsoft UxTheme Library

VERSION.DLL (statically linked also) - Version Checking and File Installation Libraries

WDMAUD.DRV - WDM Audio driver mapper

WININET.DLL (statically linked also) - Internet Extensions for Win32

WINMM.DLL (statically linked also) - MCI API DLL

WINSTA.DLL (opened when JPG files imported/previewed/added to timeline) - Winstation Library

WMADMOD.DLL - Corona Windows Media Audio Decoder - (on desktop, not laptop) - Decoder for Windows Media Audio 9, Windows Media Audio 9 Professional, and Windows Media Audio 9 Lossless. Also decodes all previous versions of Windows Media Audio.

WMADMOE.DLL (opened when previewing the timeline or saving a movie) - Corona Windows Media Audio 9 Encolder/Transcoder - Encoder for Windows Media Audio 9, Windows Media Audio 9 Professional, and Windows Media Audio 9 Lossless.

WMASF.DLL - Windows Media ASF DLL - 7/27/03 - Bob - After I installed Movie Maker 2 and tried to access the program, I got this error: "The procedure entry point ASFSEndTimeToTime could not be located in the dynamic link library WMASF.DLL." Also, at the top of the error pop-up window (on the blue bar), was this message: "GLJ263 Entry Point Not Found". Since this error, I can't access certain video editing software. > I found the DLL. The complete DLL library program had to be downloaded and installed. For anybody interested, here is the site: FreewareWeb.com http://www.freewareweb.com/cgi-bin/archive.cgi? download=1&ID=1660

WMM2AE.DLL - in c:\Program Files\Movie Maker - not seen used yet when running > 2/10/03 - I am having trouble with my Titles and Credits. When I try and put one into the movie, all I get is a blank > 5/4/03 - I attempted (several times) to install Movie Maker 2, but unfortunately get the following error message: Error 1904. Module C:\Program Files\Movie MakerWMM2AE.dll failed to register. HRESULT. Contact your support personel. This is displayed for the following 2 DLL's as well: WMM2FXA.dll, and WMM2FXB.dll. Despite the above error messages, Movie Maker 2 installs and most features work. Titles and AutoMovie however do not work. > 5/2/03 - I am having the same problem with Titles and Credits. When I installed MM2, I got some failed to register errors on WMM2AE.dll, WMM2FXA.dll, and WMM2FXB.dll. I've rebooted, reinstalled but still get the same errors. I don't know if they are related to the problem with the Titles and Credits or not. > 7/8 /03 - Steve Hayes - I downloaded MM2 and tried to install - however the following dll's won't register: WMM2AE WMM2FXA WMM2FXB. I tried to manually register them with regsvr32 but get error message 0x8007007e > John De Angelis - 0x8007007e = "The specified module could not be found" - sounds like you're missing a dll that the wmm* files need. This normally indicates your Windows installation is incorrect/incomplete. You can spend weeks trying to fix this problem by looking for files etc. The quickest way is generally to re-install Windows... > 5/19/04 - Alex - When trying to add titles to my movie, they appear as just a grey screen. Even the preview of the title in the right hand pane is only grey, none of the text I have typed appears. What may have caused this is on the install I had 3 errors. All errors were the same, only the filename changed. Basically a DLL failed to register. The 3 files mentioned were WMM2AE.dll, WMM2FXA.dll and WMM2FXB.dll. The exact error was : Error 1904. Module C:\Program Files\Movie Maker\WMM2AE.dll failed to register.

WMM2EXT.DLL - in c:\Program Files\Movie Maker - not seen used yet

WMM2FILT.DLL (opened when JPG files imported/previewed/added to timeline) - Movie Maker Filters

8/27/03 - Pat Hunter - I downloaded MM2, but when I double clicked on the icon to install it started did a fair bit then said I had an "error 1904 module c:/programme files/moviemaker/wmm2filt.dll failed to register. HRESULT contact your support personnel". And I went and read what error 1904 meant, but I couldn't understand what it was talking about. I think it is something that we haven't got ticked or installed somewhere. I tried again and got the same error message. I have no idea what this means! I need movie maker on my system, I have looked in start/programme files/accessories/entertainment. and it isn't there! > Have you tried to register it manually using regsvr32? If that does not work, see if you can find the failing module using DependencyWalker

WMM2FXA.DLL (opened when JPG files imported/previewed/added to timeline) - Windows Movie Maker FX - c:\Program Files\Movie Maker - 489,984 bytes, 12/20/02 - this is the DLL that handles the text overlay clips.

> 5/19/04 - Alex - When trying to add titles to my movie, they appear as just a grey screen. Even the preview of the title in the right hand pane is only grey, none of the text I have typed appears. What may have caused this is on the install I had 3 errors. All errors were the same, only the filename changed. Basically a DLL failed to register. The 3 files mentioned were WMM2AE.dll, WMM2FXA.dll and WMM2FXB.dll. The exact error was : Error 1904. Module C:\Program Files\Movie Maker\WMM2AE.dll failed to register.

7/8/03 - Steve Hayes - I downloaded MM2 and tried to install - however the following dll's won't register: WMM2AE WMM2FXA WMM2FXB. I tried to manually register them with regsvr32 but get error message 0x8007007e > John De Angelis - 0x8007007e = "The specified module could not be found" - sounds like you're missing a dll that the wmm* files need. This normally indicates your Windows installation is incorrect/incomplete. You can spend weeks trying to fix this problem by looking for files etc. The quickest way is generally to re-install Windows...

5/4/03 - I attempted (several times) to install Movie Maker 2, but unfortunately get the following error message: Error 1904. Module C:\Program Files\Movie MakerWMM2AE.dll failed to register. HRESULT. Contact your support personel. The also is displayed for the following 2 DLL's as well: WMM2FXA.dll, and WMM2FXB.dll. Despite the above error messages, Movie Maker 2 installs and most features work. Titles and AutoMovie however do not work.

2/10/03 - Dustin - I am having trouble with my Titles and Credits. When I try and put one into the movie, all I get is a blank

1/24/03 - Fisherman - Just downloaded the big numbered file, tried to install it, but it didn't work. Got the message "Problem registering OCX C:\Program files\Movie maker\wmm2fxa.dll", and I'm still there with my version 1.2 .

1/11/03 - Jeff - When I try to install MM2, it fails to register a DLL (see attached file for error), then says installation successful. But MM2 isn't installed, I still just have version 1.2. I am running Windows XP® Pro with DirectX 9. I have tried to force the DLL to register, and so far the most descriptive error that I can get is "C:\\program files\movie maker\wmm2fxa.dll was loaded, but the Dll Install entry point was not found. This file can not be registered." > 1/11/03 - PapaJohn - A post from someone on 11/30/02 said: When I run the install program I get a popup window that says it cannot register wmm2fxa.dll. It the reports tat setup has completed. I tried manually registering wmm2fxa.dll with regsvr32.dll but I get the error: 0x8007007e. Movie maker still runs but I am missing most of the effects and some of the transitions. Titles do not wok at all. I have found a solution to this. It seems that the registry key: KEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{44EC053A-400F-11D0-9DCD-00A0C90391D3}\InProcServer32\(default) was pointing to a DLL in a non-existant directory. I changed this and all now works fine. > 1/11/03 - Momo - My note with "OCX" in the title gives a different solution, which worked for me. I don't understand the registry well enough to know whether the registry solution below produces the same result.

1/9/03 - Momo - I have been running the MM2 Beta with no problems. After creating a restore point, I have tried to install the full kit provided in another link here. I get the following error message: Error registering the OCX C:\Program Files\Movie Maker\wmm2fxa.dll However, MM2 still works, showing Build number 2.0.3246.0. I do not know whether this is still the Beta build, or the final one. Can any of you please let me know whether (1) this build number is the Beta or Final and (2) whether the OCX error is something I need to fix, if I am indeed on the Final. > 1/9/03 - ru - You still have the beta (2.0.3246) and if you go to Help/About it should be a small non colored About box that comes up. Final is v2.0.3312 and should be a colorful larger box with the Windows XP® logo, etc. > 1/9/03 - maurice - I believe I have found a working solution for the OCX issue... in case others have it in the future. Here is the problem and the solution. - I used the setup file given in a link a couple of notes back to install. (This is because I can't get MM2 to appear in my Windows Update list no matter what language I use, and it is also not in the update catalog.) This gave the error in the base note. Running the file showed build 3246. MM2 seemed to work OK. - Inspecting the intallation directory revealed that all files except the MM2 EXE file were on build 3312 (the final build.) Regedit showed that the aforementioned dll was at least registered somewhere. - I right-clicked the dowloaded install file and opened it with Winzip, then extracting all files to their own directory. - I then double-clicked on the mm20ex file, which ran, and gave me a message saying "exception installation complete". Running MM2 and checking "About" now gives the correct build number. Everything appears to work so far.^

11/30/02 - Ben Jackson - When I run the install program I get a popup window that says it cannot register wmm2fxa.dll. It then reports that setup has completed. I tried manually registering wmm2fxa.dll with regsvr32.dll but I get the error: 0x8007007e. Movie maker still runs but I am missing most of the effects and some of the transitions. Titles do not wok at all. > I have found a solution to this. It seems that the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{44EC053A-400F-11D0-9DCD-00A0C90391D3}\InProcServer32\(default) was pointing to a DLL in a non-existant directory. I changed this and all now works fine. For more information look at: http://support.microsoft.com/default.aspx?scid=KB;en-us;281383&

WMM2FXB.DLL - version 2.0.3312.1 - 318,464 bytes, 1/15/03 - note that this a newer version than the 2.0.3312.0 that was in the originally installed final release package. I haven't seen it yet in the list of running modules, but it's in the c:\Program Files\Movie Maker folder.

If you are into thorough trouble-shooting of MM2 on your computer, and do not have this newer version of the DLL, I recommend that you download the latest installation package and install it over the existing software.

2/10/03 - Dustin - I am having trouble with my Titles and Credits. When I try and put one into the movie, all I get is a blank > 5/2/03 - Danny - I am having the same problem with Titles and Credits. When I installed MM2, I got some failed to register errors on WMM2AE.dll, WMM2FXA.dll, and WMM2FXB.dll. I've rebooted, reinstalled but still get the same errors. I don't know if they are related to the problem with the Titles and Credits or not. > 5/4/03 - Paul - 5/4/03 - I attempted (several times) to install Movie Maker 2, but unfortunately get the following error message: Error 1904. Module C:\Program Files\Movie MakerWMM2AE.dll failed to register. HRESULT. Contact your support personel. The also is displayed for the following 2 DLL's as well: WMM2FXA.dll, and WMM2FXB.dll. Despite the above error messages, Movie Maker 2 installs and most features work. Titles and AutoMovie however do not work. > 7/8/03 - Steve Hayes - I downloaded MM2 and tried to install - however, the following dll's won't register: WMM2AE WMM2FXA WMM2FXB. I tried to manually register them with regsvr32 but get error message 0x8007007e > John De Angelis - 0x8007007e = "The specified module could not be found" - sounds like you're missing a dll that the wmm* files need. This normally indicates your Windows installation is incorrect/incomplete. You can spend weeks trying to fix this problem by looking for files etc. The quickest way is generally to re-install Windows... > 5/19/04 - Alex - When trying to add titles to my movie, they appear as just a grey screen. Even the preview of the title in the right hand pane is only grey, none of the text I have typed appears. What may have caused this is on the install I had 3 errors. All errors were the same, only the filename changed. Basically a DLL failed to register. The 3 files mentioned were WMM2AE.dll, WMM2FXA.dll and WMM2FXB.dll. The exact error was : Error 1904. Module C:\Program Files\Movie Maker\WMM2AE.dll failed to register.

WMM2RES.DLL - version 2.0.3312.0 - 4,256,768 bytes - 12/20/02 - in c:\Program Files\Movie Maker\1033 - statically linked to MSVCRT.DLL

2/27//03 - Georg Kleinegees - MovieMaker turn off Autostart when connecting to a DV-Camera? - just found the answer by myself. this key must be deleted: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Autop layHandlers\Handlers\MSVideoCameraArrival] "InitCmdLine"="\"C:\\Programme\\Movie Maker\\moviemk.exe\" /RECORD" "ProgID"="Shell.HWEventHandlerShellExecute" "DefaultIcon"="C:\\Programme\\Movie Maker\\moviemk.exe,0" "CLSIDForCancel"="{AB007EC8-E2D4-4664-ACD9-1D059681F3DE}" "Action"="@C:\\Programme\\Movie Maker\\1033\\wmm2res.dll,-63095" "Provider"="@C:\\Programme\\Movie Maker\\1033\\wmm2res.dll,-100"

WMMFILT.DLL - c:\Program Files\Movie Maker - 122,940 - 6/13/02

2/18/03 - John Bennett - I've had all the same problems of crashing and also the "not responding" messages. But is this the root cause, I also have got left over files from mm1 which weren't deleted on the install of mm2. The problem is how do I get rid of them. If I try to delete them they just reappear of their own accord. I've got the following old files..... In the main MM folder are.... wmmfilt.dll ver 1.2.2541.1 dated 13/6/02 120kb. If any or all of these should not be there please instruct on how to kill them off Please, as I have said, They seem to have a mind all of their own....... > 2/19/03 - PapaJohn - I too have left-over stuff from MM1. This is pretty usual for a software installation to leave stuff that has to be manually deleted - or just abandoned in place. I don't think extra parts from MM1 will cause MM2 to not function properly, but it's interesting that you can't delete them without them being refreshed.

WMMRES.DLL - c:\Program Files\Movie Maker - 319,546 - 6/13/02

2/18/03 - John Bennett - I've had all the same problems of crashing and also the "not responding" messages. But is this the root cause, I also have got left over files from mm1 which weren't deleted on the install of mm2. The problem is how do I get rid of them. If I try to delete them they just reappear of their own accord. I've got the following old files..... In the main MM folder are.... wmmres.dll ver 1.2.2541.1 dated 13/6/02 312kb. If any or all of these should not be there please instruct on how to kill them off Please, as I have said, They seem to have a mind all of their own....... > 2/19/03 - PapaJohn - I too have left-over stuff from MM1. This is pretty usual for a software installation to leave stuff that has to be manually deleted - or just abandoned in place. I don't think extra parts from MM1 will cause MM2 to not function properly, but it's interesting that you can't delete them without them being refreshed.

WMMUTIL.DLL - version 1.2.2541.1 of 6/13/02 - 77,885 bytes - in the C:\Program Files\Movie Maker and the C:\WINDOWS\SYSTEM32\dllcache folders of my desktop. Also have version 1.1.2427.1 of 8/29/02 - 163,897 bytes in the C:\WINDOWS\ServicePackFiles\i386 folder of the desktop, and on my laptop in the normal working and Service Pack folders. What seems unusual is that the older file has a later revision number, that the newer version is twice as big as the older one, and that this MM1 DLL is somehow interfering with MM2 startup in some cases.

On 9/10/04, after installation of SP2 and MM2.1 on my desktop computer, I get an error message when starting MM1 "The ordinal 466 could not be located in the dynamic link library WMMUtil.dll". The DLL is the version of 77,885 bytes, and deleting it results with it being replaced by the same version. I resolved the problem by replacing it with the version of 163,897 bytes from my laptop, just copying the larger file over the existing one.

The differences between the two seem to be: (1) the larger file seems to have 5 times the resources allocated to some things, (2) ordinal 161 is referenced in the larger but not the smaller, and it points to FatalAppExitA, (3) ordinal 466 is referenced in both, and points to RegCreateKeyW, (4) the big one uses COMCTL32.DLL as an import table, while the smaller one doesn't, (5) the big one uses comdlg32.dll while the smaller one doesn't - color, font, file name, title, etc., (6) the big one uses SHELL32.DLL while the smaller doesn't, (7) the section tables in the bigger ones are 3 times the virtual sizes of the corresponding ones in the smaller file, (8) the smaller one renews itself if you delete it. But, if you copy the larger one over the smaller, it lets you, and MM2 runs with either. Once copied over the smaller one, if you delete it it's replaced by another copy of the larger one. >>> bottom line - I'd try the larger one if you have any problems which point to this file.

8/14/04 - Whenever I try to start Movie Maker I receive this error message, "The ordinal 466 could not be located in the dynamic link library WMMUtil.dll. > I have tried everything that you offered on your Website and nothing works. > I just wanted to update everyone interested. I installed XP SP2 and it installed Movie Maker 2.1 successfully. > Ordinal not found means that Windows can't find a function (ordinal) in a dll that it's looking for. In general, you have the wrong version of a dll that an application requires. How you got to this point is unknown. Could be a failed installation of Movie Maker or a failed installation of some other software that installs the same dll. version 1.1.2427.1 comes with Windows XP SP1. version 1.1.2427.0 comes with Windows XP Home/Prof 2002. Try re-installing SP1 first, then try installing MM2. If that doesn't work, try moving all dependent dlls (and files) for Movie Maker into the installation folder of MM2. In today's Windows Installer world, its recommended practice to store dependencies into an applications installation folder and not in shared folders such as System32 to avoid dll-hell issues. Last but not least, you can always start from scratch and re-install Windows. > I'll remember that information the next time I have a problem but since I installed XP SP2 I have been able to use the new MM2.1.

12/28/03 - Bob - I have error missing ordinal 466 within wmmutils.dll. Further work indicated that i'm missing an efsadu.dll file.

9/13/03 - kaos - I looked and found one other person having the same problem as I: everytime I try to run MM2 I get the following error message "The Ordinal 161 could not be located in the dynamic link library WMMUtil.dll.", but there has to be a solution other than doing a full reinstall of win XP as done by Graham.

7/2/03 - shadowman - everytime I try to run MM2 I get the following error message "The Ordinal 161 could not be located in the dynamic link library WMMUtil.dll."

6/17/03 - Graham - I get the error "The ordinal 466 could not be located in the dynamic link library WMMUtil.dll" when I attempt to launch movie maker. I have since re-installed if from the download available from the MS site to no avail. > You could try just replacing the dll. > I was using MM2 and tried everything that I could...... Including a full repair of XP. That failed to correct it, in fact I got another "ordinal missing" error once the repair was done. The error was the same but for the number 161. I have since done a full reinstall of XP (without formatting) and it works again

2/26/03 - Steven Grant - I created an AVI file in another program and I tried to import it into MM but then it crashed on me. Now it won't let me into the program again saying that: "The ordinal 466 could not be located in the dynamic link library WMMUtil.dll"

2/18/03 - John Bennett - I've had all the same problems of crashing and also the "not responding" messages. But is this the root cause, I also have got left over files from mm1 which weren't deleted on the install of mm2. The problem is how do I get rid of them. If I try to delete them they just reappear of their own accord. I've got the following old files..... In the main MM folder are.... wmmutil.dll ver 1.2.2541.1 dated 6/13/02 - 76kb. If any or all of these should not be there please instruct on how to kill them off Please, as I have said, They seem to have a mind all of their own....... > 2/19/03 - PapaJohn - I too have left-over stuff from MM1. This is pretty usual for a software installation to leave stuff that has to be manually deleted - or just abandoned in place. I don't think extra parts from MM1 will cause MM2 to not function properly, but it's interesting that you can't delete them without them being refreshed.

1/30/03 - Richard H - When I installed Movie Maker 2, some of the 1.1.2427.1 dlls were leftover without the updated version. > 1/31/03 - PapaJohn - You're right. Those 3 are dated 6/13/02 and didn't change with the final release. Looks like they were replaced with the wmm2??? DLLs and not deleted.

1/20/03 - Le'Dell - When I try to run MM2 I get this error: moviemk.exe - Ordinal Not Found / The ordinal 466 could not be located in the dynamic link library WMMUtil.dll. I recently had to change out hard drives my old one was dying and I had to rename everything in the registry that referred to C:\ to F:\ and I still have a few other issues. This is a big issue since I just started using MM2 and on 1 and 2.0 I've had no notable problems before replacing the drive. Now even after installing from the setup.exe through MS I still get the same exact error every time > 1/27/03 - John De Angelis - I'm taking a shot in the dark here, but being a programmer, usually that means that you are calling into some other program expecting to find some code, but it isn't there. In this case it probably means the version of MM2.exe you have doesn't match the version of WMMUtil.dll. You should probably re-install MM2... To re-install I think you have to modify a registry key that was posted in this newsgroup a week or so ago. > 1/28/03 - PapaJohn - Perhaps a corrupt or obsolete DLL?? The wmmutil.dll on my computer is dated 6/13/02 and it's size is 77,885. How does that compare with yours? The other thing is to search the registry for the DLL. Maybe you missed a pointer in it.

WMSDMOD.DLL - Windows Media Screen Decoder - Decoder for Windows Media Screen 7 and Windows Media Video 9 Screen

WMV8DMOE.DLL - Windows Media Video 8 Encoder - (on desktop and Toshiba laptop, not old Dell laptop - opens when saving a movie in WMV format)

WMVADVD.DLL - Windows Media Video 9 Decoder (internal name of wmv9dmod.dll) - opens when importing a WMV story or movie file...

5/18/06 - .... after burning a few DVDs from Photo Stories, I soon came across the PCTV effect. When I discovered and tried the PapaJohn custom profile for PAL DVD in PS3 with a short project, I was delighted with the results. However, when I made a long project (prob just over 200 photos) I got the WMVADVD.DLL problem when trying to burn the WMV file using Sonic MyDVD, and also if I tried to convert the WMV file to MPEG2 using TMPEGEnc. So, back to the fuzzy pictures with the standard MS profile (for PAL DVD ) OR one of the higher resolution PC profiles and a lot of work blurring individual photos to eliminate PCTV effects.

11/8/05 - involved in some crashing of MM2 when importing stories made with PapaJohn's custom profiles.

3/25/06 - involved in some more crashing of MM2 when using my custom PS3 profiles for NTSC. The longer post is : ... made several small projects (25 slides each) in Photo Story... imported the saved WMV files to Movie maker. Every time I try to save this movie (to any of the profiles) It always crashes without explanation. It will only get through about 25% then crash. I have viewed the log error report. The problem is with wmvadvd.dll version 10.0.0.3646. Fault address 0x000a59ca. This was the same error... when attempting to import a large WMV file. So I made a bunch of smaller Photo story shows (no sound or titles). So now it doesn't crash on import, but consistently when attempting to save the basic movie (no sound, no editing)(tried a series of profiles).

The problem was with the custom profiles for NTSC... resaved the projects with the standard profile, exported to Movie Maker and saved again with standard profile.

WMVCORE.DLL (statically linked also) - Windows Media Playback/Authoring DLL - 2,058,888 bytes, 12/11/02 - c:\Windows\System32 (note - have other versions in other places also)

2/4/03 - chuck darke - failure to capture - problems started after Windows Updates on 1/22/03 (updates Windows XP® 0329170, 810833, V4). Also affected, Plus Dancer would not launch giving message "Dancer.exe - Entry Point Not Found The procedure entry point WMCreateSyncReader could not be located in the dynamic link library WMVCore.DLL". > resolved by System Restore

3/10/04 - Ray - I tried to start Movie Maker and got a message "application has failed to start because WMVCORE.DLL was not found - try to rinstall and this may fix the problem" I also have sonic MY DVD on my system and that message also came up when I tried to start that program. > (Microsoft) Looks like something is wrong with the Windows Media components on your system. Probably the easiest way to fix this is to reinstall the Windows Media Player 9. > That did the trick..

WMVDMOD.DLL - Corona Windows Media Video Decoder - (on desktop, not laptop) - Decoder for Windows Media Video 7, Windows Media Video 8, Windows Media Video 9, and Windows Media Video 9 Image. 816,264 bytes, 12/11/02 - c:\Windows\System32

2/7/03 - Buddy Morel - crashes when saving a movie - faulting module - version 9.0.0.2980, fault address 0x00051c87.

2/7/03 - Thomas Jarboe - When I go to save a movie, mm2 crashes - faulting module - version 9.0.0.2980, fault address 0x00051c87.

WMVDMOE2.DLL - Corona Windows Media Video Encoder. Encoder for Windows Media Video 7, Windows Media Video 8, Windows Media Video 9, and Windows Media Video 9 Image. - 446,464 bytes, 8/29/02 - c:\Windows\System32 - opened when previewing the timeline or saving a movie

2/7/03 - Buddy Morel - crashes when saving a movie - faulting module - version 9.0.0.2980, fault address 0x00064ac4

2/7/03 - Thomas Jarboe - faulting module - version 9.0.0.2980, fault address 0x00064ac4

WOW32.DLL - Opens when previewing the timeline or saving a movie

WS2_32.DLL - Windows Socket 2.0 32-Bit DLL

WS2HELP.DLL - Windows Socket 2.0 Helper for Windows NT

WSOCK32.DLL - Windows Socket 32-Bit DLL

Other modules mentioned in postings, but not seen yet as being active on my computers when running Movie Maker 2

FRAMEDYN.DLL - 174,592 bytes, 8/23/01 - c:\Windows\System32\dllcache (and in C:\Windows\System32\wbem) This error can be caused if the System PATH environment variable does NOT include the %SYSTEMROOT%\System32\Wbem folder, or if the %SYSTEMROOT%\System32\Wbem\framedyn.dll file is missing or corrupt.

1/3/03 - Christian - I tried to update Movie Maker to the Ver. 2 Beta. Everything went fine but then after all the files were installed, a message came up that said: boot.exe - Unable to Locate Component This application has failed to start because framedyn.dll was not found. > 1/4/03 - Christian - Well, I just reinstalled Windows XP®. Works fine now.

12/21/02 - Josh S - Having the same problem...

12/21/02 - Josh - It won't install for me either. It says it can't find FRAMEDYN.DLL and gives me a boot error. I did a search on my computer, and it found FRAMEDYN.DLL, go figure. The installer says it has completed successfully, but there's no new icons, and when I load MovieMaker it still loads ver 1.1. Help!

12/17/02 - Jim - Upon attempting to install WMM 2, I get: boot.exe - Unable To Locate Component This application has failed to start because framedyn.dll was not found. Re-installing the application may fix this problem. But framedyn.dll is system32/wbem

11/4/02 - MPVinBoynton - I tried to install Movie Maker 2, but I get a message that it couldn't install because the Boot.exe couldn't find file FRAMEDYN.DLL. I have the file in the Windows/System32/Wbem subdirectory. > 11/4/02 - Kristen Whalen - There's quite few KB articles out on www.microsoft.com regarding FRAMEDYN.DLL; None of them are specific to MovieMaker, but you might want to try out some of their suggested fixes. Check out the following KnowledgeBase article, and see if it offers any insight: http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q319114& > 11/7/02 - I was able to fix this problem by changing the path statement as suggested in the article you suggested. It just had to be done differently than how they said.

ITSS.DLL - 122,368 bytes - 1/10/03 - c:\Windows\System32 (also in c:\Windows\ServicePackFiles\i386)

12/25/02 - Robert Daems - Up until a week ago it worked great. Whenever I import video now, it will act as if it is importing and you can see the clips being formed. When it has 2% left a message box pops up saying 'An error has occurred and Windows Movie Maker must close.' This is the error signature that is displayed: AppName: moviemk.exe - AppVer: 1.1.2427.0 ModName: itss.dll ModVer: 4.72.8085.0 Offset: 0000252c I have tried several different videos and I get the same message each time. I tried installing the new Beta version that is available on the Microsoft site, and it worked fine for 3 days, and even imported in half the time, but the program wouldn't even open the days after, so I reverted back to the original vers. that came with Windows XP®. The problems are still occurring. > This looks like a Destination Save problem. You may not have enough disk space. Look for *.tmp files or N$ files in Windows directory.

MMSTFX.DLL (not on my main computer)

1/31/03 - John - pointed to at the bottom of a post about XML problem(s)

MSORUN.DLL - 390,560 bytes, 2/13/01 - C:\Program Files\Common Files\Microsoft Shared\MSORun

1/14/03 - Ron - I downloaded the updated MM2, however after windows update says downloaded and installed correctly (successful) when you open the MM2 the program opens up however there is an error box that pops up shortly after opening the program. it reads: "WMM has encountered a problem and needs to close" if you click more information about this error it reads: Error Signature: AppName: moviemk.exe AppVer: 2.0.3312.0 ModName: msorun.dll ModVer: 10.0.2609.0 Offset 00028002

MSVCR70.DLL - 307,200 bytes, 11/29/00 - C:\Program Files\Microsoft Office\Office10\VS Runtime

1/13/03 - Mike Weiss - MM2 doesn't use the newer "msvcr70.dll"?

WMM2ERES.DLL - 4,096 bytes, 12/20/02 - in the c:\Program Files\Movie Maker\1033 folder