vurdomain.blogg.se

The process described above may require you to rename the project file to. Necessity is the mother of invention :)Ī question came up around how to view all file extensions in windows. We were unable to revert to the backup copy as it was too outdated.I originally posted this information as a post to a WMM forum back in April of 2010.Removing the invalid extentRef resolved this issue for me.WMM does not know how to handle invalid references and just crashes.In this case, there was no extentRef of id="14" in the "ExtentRefs" Section of the project XML File.The project file was able to be opened without crashing WMM.

After saving the changes, I renamed the the.So that the whole section now looks like: I deleted these 3 lines in the corrupted file: Towards the bottom of the file, noticed this section: In this case, There was a difference between the good and bad file.

Using WinMerge (Open source file comparison utility), I compared the Good project.

In this case, IE Loaded the file fine so I knew there were no XML Schema issue.

If there is an issue with the XML Structure, IE will tell you.

Opened the renamed copy of the corrupted project file in Internet Explorer.

Made a copy of the corrupt project file and rename it to a.

Made a copy of an older backup of the project file that was in a known good state.

Ensured that WMM could open other project files (In this case it did).

Most likely the corruption was the result of a Windows Movie Maker crash.

The root cause was found to be an Invalid ExtentRef ID in the. This error message was encountered when trying to load the corrupt project file: Windows Live Movie Maker has Stopped Working This post describes the process I went through to isolate the problem and repair the file. A little over a year ago I helped fix a corrupted Windows Live Movie Maker project file.