I am running Windows Movie Maker 2012 on Windows 7 x64. Unfortunately, I still get the errors from time to time and I am not able to recover the clips.
0x87160139 - unable to save project
0x8007000E - file(s) might be corrupt
Hardware-wise, the PC is well equipped: 6 core Xeon processor, 24 GB RAM, a 6 GB/s 240GB solid state drive. The system never crashes in and runs very fast and stable for general use.
I have been using Windows Movie Maker since Windows XP but only ran into this problem after starting to edit 1080 video. When the 0x87160139 error appears, it usually seems to affect 4 or 5 clips at once. Sometimes it will plague a couple of clips, but then
spreads to others near it. Usually I can close my project, wait a minute, then re-open WMM and open the project. Then the clips are OK.
I do not believe this is a codec problem (for me) because all of my video was shot with the same camera and the problem does not plague all of my clips. I can throw together a short (30 second or 1 minute) video using the same video clips without any problems.
Things I've tried to fix the problem:
- Install a more power video card (NVidia 210 swapped for NVidia GT 630)
- Up date WMM, video card drivers, codecs, Windows Update
- Disabling Symantec Endpoint Protection
- Moved all of my video clips from a standard hard drive to the SSD to gain faster access times.
- Windows System and App logs are free of any obvious errors.
- Using the "Fix Clip" option never works. My only option is to delete the clip and re-add and re-trim it.
Ironically, sometimes one of the yellow triangle clips will still be playable inside the program, even though there is no thumbnail for it on the timeline.
Because I am currently in the middle of editing a 25 minute program, I have been saving/rendering the unfinished video from time to time in case the whole project craters on me.
On a semi-related note, for what it's worth, with every version of WMM since Windows XP, I've experienced a problem where, in a finished video, there is a noticeable lag/delay/pause when a new clip/scene starts. I see a still image of the first frame of video
for a short time, then the video starts to move and the sound starts. Also, WMM does not perform well with 1080 video. I have to run a GPU monitoring program (GPU-Z) and keep an eye on that. Once the "Video Engine Load" starts dropping back to a lower percentage,
then WMM will become responsive and I can continue editing. I think this is primarily a function of the large amount of data in 1080 video.
I am about to give up on WMM and learn something else. I guess this product, being free with the OS, is worth pretty much nothing.