Making sense out on .MSI verbose trace - running a CustomAction?

Like in your previous question where I suggested using cmd. Exe /C XmlPreProcess. Exe ... for redirection, for debugging you can try with K instead of C .

Then any output should stick around, and you'd be able to work within the context of the MSI at the time of error.

Yes, the ErrorIcon is just noise and can be ignored. I'm in the process of removing this 'noise' from my MSI now so I can properly debug.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.