1 person found this helpful
I eventually found a solution to this problem and it relates to the Hewlett Packard printer software. The HP software includes a laser jet monitoring service. Initially, I simply stopped the HP laserjet service from starting by using MSConfig and that worked fine. However, I thought the laserjet monitor was worth having. Clearly, the HP monitor service was opening too early and Microsoft suggested it might be the spooler opening too soon but I found another unknown service was also causing a problem. In the end I used Services to set the starting condition of the HP monitor service to "auto start delayed". This delayed opening the HP monitor service until after all other services had started.
I had initially thought that Windows commands Services, MSConfig and Events were not working but I found that if I gave them about 5 minutes to open I could use them. Once I could use "Services" I was able to determine that the LanmanServer was stuck trying to open and "Events" system log was showing an error Event 7022. I was then able to find the cause on the Microsoft website.