@Herbert7,
Thank you for your feedback. I see that we tried exactly the same thing to get VP5 to work. I already had this problem with version 5.5.0. I contacted support and provided them with the error report (sent automatically by DXO) and a diagnostic file. The last response indicated that the error would no longer occur with version 5.5.1. Unfortunately, I had to inform them that this was not the case — however, I did not try everything I did with version 5.5.0. Therefore, we are still waiting for a solution from the support team. I will get back to you when I hear something new.