I have the same problem - running on a Windows 10 x64 system, with Movie Maker 2012 (from download of Windows Expressions just a few days ago). I simply attempted to set a start point (which cuts from the beginning of the video to the start point) and save. My system becomes non-responsive, takes 99% of the CPU and 1.5 GB of memory (I have a 3.0 GHz Core Duo on 4 GB of memory), and eventually crashes with an accvio (access violation), which probably means it ran out of memory.
It looks like an essential design problem, and this may be the reason that Microsoft is no longer developing this product. It looks like it caches much of the video and audio in physical memory, so you would need a supercomputer with 16GB of memory and 2 quad-core CPUs to process a simple 60-minute video. However, Movie Maker is a 32-bit app, so it will just crash when it's filled up the max 4GB memory complement.
I haven't done a full analysis; this is just an educated guess by a software engineer with 40+ years experience, mostly on Windows and its predecessor. Now I need to find some video editing software that actually works that will read WMV files, a tall order. I may have to convert it to MP4.
This is very disappointing, to say the least. Now that Microsoft owns YouTube, WMV is now acceptable as an upload format, so I thought Movie Maker would be the perfect editing system. No such luck.
Regards
Jon Campbell