As an system administrator, I know how difficult it can be to solve Windows Update errors. This is particularly the case with Windows Update, because Windows Update always returns generic errors. KB-articles will likely not help you, because these articles are written with theoretical knowledge, and are barely based on real-world scenarios.
Posts under ‘Windows 2008’
Event 37: The speed of processor # in group # is being limited by system firmware
On some of our HP DL360G6 servers, the following warning (event id 37) showed up in the event log of Windows 2008 R2
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 12/21/2009 5:04:12 PM
Event ID: 37
Task Category: (7)
Level: Warning
Keywords:
User: SYSTEM
Computer: <servername>
Description:
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 2139 seconds since the last report.”
Error 5: Access is denied. when you try to start the DHCP Client service
When you start your computer, or try to start the DHCP client service, you may receive the following error:
Could not start the DHCP Client service on Local Computer.
Error 5: Access is denied.
This problem may occur after an upgrade from Windows 2000 to 2003, or after you’ve changed permissions in the registry.
FIX: The Parallel port driver service failed to start
After you have disabled the Parallel Port in your BIOS, the following error may occur every time you start Windows.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 8/13/2009
Time: 9:15:47 AM
User: N/A
Computer: computername
Description:
The Parallel port driver service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
View the BIOS version of your motherboard
As an administrator, there may come a time that you have to upgrade the bios. A new firmware may fix some bugs and may have new functionality. It also may be a required before you can request support from the manufacturer.
In all these cases, the first step to take is to determine the current BIOS version / firmware version. Yes: you can determine the firmware version by rebooting the computer and going into the BIOS, but in production environments this is often not recommended. :-)
Especially for these situations, you can view the BIOS version while running Windows. There are two easy ways to determine your current firmware version.