I don't think so, no. SQLDiablo identified the problem in the RTM release, we found it again in SP1. While describing the problem to a Microsoft support engineer, he told us to apply CU6 ASAP because there is a bug in SP1. The (unrelated) SP1 bug causes the windows installer to start repeatedly which causes the windows registry to inflate. We checked the registry on all our sql servers, found a bad one and ended up having to reinstall the OS on it, I didn't know whether to laugh or cry.