In 2013, it was observed that shortly after the startup process, Automatic Updates (codice_2) and Service Host (codice_3 in Windows XP would claim 100% of a computer's CPU capacity for extended periods of time (between ten minutes to two hours), making affected computers unusable. According to Woody Leonhart of InfoWorld, early reports of this issue could be seen in Microsoft TechNet forums in late May 2013, although Microsoft first received large number of complaints about this issue in September 2013. The cause was an exponential algorithm in the evaluation of superseded updates which had grown large over the decade following the release of Windows XP. Microsoft's attempts to fix the issue in October, November and December proved futile, causing the issue to be escalated to the top priority.