View Question

Good news! We have migrated all the Q&A on this site to, and are currently monitoring questions there!

Here are some important links:

All posts here are permanently locked (and will be redirected soon), and if you have any issues with the new site, please submit a support ticket, use the contact form, or visit our Slack Workspace.

The BuildMaster Service was not starting, probably after the lastest windows updates were applied. First discovered the problem with Jenkins and found this advice

which worked so I also applied it to BuildMaster in bmservice.exe.config:
<generatePublisherEvidence enabled="false"/>

This also worked. Is this a known issue and is there a better work around / patch for it?

Thanks for the report, Andrew; if that's the case, then the problem is with the .NET CLR (and Windows Crypto) validating our code's signature.

Basically, the server is attempting to download a certificate revocation list and taking a long time due to no internet access... and the service isn't starting in the mean time.

It's not a big deal; we may ship with this setting in the future, as numerous folks experienced this as well.

Long story short... this is a suitable workaround.

Thanks for the work around.
Saved us much headache!