I installed ProcessMonitor from Systernals in my Windows 2003 Server Standard Edition SP2. The fist time I ran it, Windows gave me a Blue Screen Of Death (BSOD). The stop code was 0x0000007. I rebooted the VM, and was good to go.

After a few hours of tweaking, I found the root problem. I have a solution, but I'm not happy with it. Windows 2003 is looking in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727, but not in C:\WINDOWS\System32. Microsoft installs the MMC 3.0 libraries in C:\WINDOWS\System32. Unfortunately, the path-looking routines are ignoring the PATH environment variable completely.

MMC 3.0 snapins are registered in the system by using the InstallUtil.exe utility in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727.

The brute force solution is to copy the needed assemblies to the PainlessSVN directory, or to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727. I really don't like either one, because I hate messing with an user's system files, but that's my network administrator experience talking.

The strange thing, is that I have a routine in the install package to do exactly this. It's not working on Windows 2003 Server Standard Edition SP2, but works fine on SP1.

At least I'm making some headway with this ridiculous issue...