I already reported this in the beta thread. It's the *svc.exe files and it happens if one uses custom installation (disabling the updater and/or access protection).
It's either a bug in the install script (it should probably install the files even if the features are deselected, but should not register/activate the corresponding services - check if they are under the correct component, should probably be under MainModules, not under UpdateService and NTServices), or it's a bug in the program itself, where it doesn't correctly detect that a feature wasn't installed. I guess the former is the case.