When registering a startable component with an unsatisfied dependency, and then this dependency is satisfied with a fluent registration, the startable component isn't started. This seems to be a bug in OptimizeDependencyResolutionDisposable, which disables the events needed for the kernel to realize that the dependency has been satisfied. Test case: http://github.com/mausch/Castle.InversionOfControl/commit/8320337199ef5ca1d4f8ecd723ef5104867c9ecb

Another issue with this is that by introducing OptimizeDependencyResolutionDisposable only in the fluent registration, the non-fluent registration can have a different behavior (like this bug).