The files are still cut off with that 2015.04 version from the drop box.

The A/V only occurs, when I install 2015.03upd3 *and* load the license. 2015.03upd3 works without license. 2015.04 works with and without license.

Is it possible that 2015.04 has changed something (not backwards compatible) in the registry?!?

Sorry no, it still fails with the version that you placed in the dropbox. The log files look exactly the same.

It's getting even stranger. I have uninstalled 2015.04 and installed 2015.03upd1. When this is in "trial" mode, everything works as expected. After loading the license, FixInsightCL suddenly fails with:

Exception EOleException in module FixInsight.Services.dll at 0020202C.

Uninstall/Reinstall 2015.04 and the XML files are cut off. No matter whether its trial or registered.
Uninstall/Reinstall 2015.03upd1 in trial mode and I can at least work.

I think this is a duplicate of: this issue

If you want to (un)select just a few rules it's always faster to turn everything on/off with a single mouse click and then check/uncheck the (ir)relevant rules.

I was just going to report the same issue. .dpr files are ignored by FixInsight.

This is the one installed with your upd01 setup from the web site. It says:
FixInsightCL version 2015.02upd1.
There is no version Info shown in Windows explorer.

The smalles dpr which returns a zero exit code plus a "failed to parse" message is this one:

program Defekt;
###
begin
end.

Unfortunately the same result in both cases. The output of the batch script with the invalid .dpr is:

Failed to parse xxxxx.dpr
Exit Code:
0

How do you return the exit code? In my command line application (compiled with XE2) I return it the following way:
Which means I exit with zero in case of an exception... Have to fix that :)

begin
    try
      ...

      analyzer := TLogAnalyzer.Create;
      ExitCode := Analyzer.Analyze(parser);

    except
      ...
    end;
end.