That being the issue might make sense. My experience is it (Winoldap running) only happens the first time the SP is ran. Replace the CHM help thing with a simple VB exe would not be difficult. A simple window showing text (VB easily does RTF) and a close button would not be difficult to write.
I don't think its that because I don't have winoldap loaded on my computer or it doesn't conflict with SP whether it be real hardware or vm. People can manually kill the task or if I remeber who made it can add the command kill winoldap. If I had this issue I would have rectified it a long time ago. I'm not sure how to approach because I can't test scenarios.
Now the vbs script will come in handy with trying to detect with VMs. Its so many VMs software we'll be working our asses off try to please every single user. So far, 3.65 works with VMware and not others and 3.66 works with qemu and not others. I have already started the process for 3.67. Maybe we can find the right combination for VMs because I really don't want to install 10 different VMs on my computer and configure them etc... Then its the versions of VMs, not everyone is going to be using the same build which will bring more issues.