Hi, Thanks for your posting. We dont get similar feedback about June 2012 patches, but we have similar article that describes services will not start after apply some updates. Workaround is modifying the registry to increase the default time-out value for the service control manager, just like what you did. This may resolve the problem, however we recommend that you research the problem to determine whether it is a symptom of another problem. Like K Seeker mentioned above, please check event viewer to find related event logs for further troubleshooting. And generally, Windows will create a system restore point before install Windows updates. You may restore the system point, if this issue disappears in the restored system state, we can use a 50/50 approach to quickly narrow down which update is causing this issue. For more information please refer to following MS articles: Event ID 7011 Basic Service Operations http://technet.microsoft.com/en-us/library/dd349371(v=WS.10).aspx A service does not start, and events 7000 and 7011 are logged in Windows Server 2003 http://support.microsoft.com/kb/922918 Reporting Services Windows Service will not start after applying MS08-052 http://blogs.msdn.com/b/psssql/archive/2008/09/23/reporting-services-windows-service-will-not-start-after-applying-ms08-052.aspx Hope this helps! TechNet Subscriber Support If you areTechNet Subscription user and have any feedback on our support quality, please send your feedback here.Lawrence TechNet Community Support

Does anyone know what change occurred in the June 2012 'Patch Tuesday' set of patches that would have affected services? This request is because after applying this month patches several Services running decided to stop working after the reboot. It has happened on three different servers each running different applications. If we try to manually start the services they time out, yet if we manually start the program the service runs (which can be done for some of them) the program functions correctly. We have found a workaround which involves increasing the timeout, via creating a DWORD value "ServicePipeTimeout" (with a value, in our case of 60000 decimal) in the location of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control After a reboot the troubled services do eventually start, but as this increases the time a server takes to load we would still like to identify the source of the issue. The variety of services this has effected include a backup service, a EDMA export service and a service related to our financial software. Thank you

Honestly, I haven't seen any issues with regard to June 2012 patches on our servers. It might be a co-incidence that services stopped simultaneously on 3 of your servers. You might wanna check event viewer on servers in question to see if there are any warnings/errors related to stopped services.Thanks !