A compatible Trusted Platform Module (TPM) Security Device cannot be found


  • In a clean installation of WS08 RC0 Standard x64, Event 537, Level=Critical, Source=TBS, appears on each restart.

    Text of the event: A compatible Trusted Platform Module (TPM) Security Device cannot be found on this computer.  TBS could not be started.

    This event also occurs if you try to start the TPM Base Services service (service name=TBS) manually.

    The computer is a Dell PowerEdge 2900.

    I haven't seen this event in previous versions of WS08 (June CTP, Beta 3, April CTP), and nothing about the hardware has changed, so I'm guessing that this is a new feature introduced in RC0.

    Has anyone else seen this event?

    Does anyone know if the PowerEdge 2900 even has a TPM?

    Wednesday, September 26, 2007 5:51 PM


All replies

  • No they do not.


    Which Dell Servers have TPM in it?
    Most of the next generation (10G) of Dell PowerEdge servers will have TPM.



    Wednesday, October 10, 2007 11:48 PM
  • Thanks for answering this.
    Saturday, October 13, 2007 2:37 AM
  • glad i could help.  please mark the post as answered.
    Saturday, October 13, 2007 2:42 AM
  • I marked the post as answered, but I wonder if the "Critical" level of the event is appropriate.  Since many computers that will be running WS08 won't have TPM's, perhaps the level of the event would be more appropriately "Error" or even "Warning" with more explanation in the event message.
    Wednesday, October 17, 2007 3:16 PM
  • I am running a Dell Latitude D820, Vista Business v6.0.6000, IE 7.06.16546, WAS part of a Windows 2003r2 SBS network, changed over to workgroup and left SBS network, amongst other problems is the SQL not letting go of its ceaseless search for the MSSQL and MSSBS queries, my MS Network Monitor 3.1 has identified that Vista will not stop querying for the SBS server, even after I've shut down the remaining SQL services, and I'm getting this error constantly. I've had it appear on an identical computer for a user that left the company where I maintained the SBS 2003r2 server, and I'm getting the same errors.

    Other factors: Upon leaving the network - group policy still seems to be a problem, I cannot get Vista to stop trying to find gp settings in both laptops (and that includes disabling the gp network services on my laptop as a test to see if that would help), and still this problem occurs. I have seen it happen on a rare occassion to a couple laptops connected to the SBS server, but it disappeared on its own and did not come back. I'm worried this is causing additional problems. Any potential solution for this? I found this in the msdn2 area:


    A compatible Trusted Platform Module (TPM) Security Device cannot be found on this computer.

     But, doesn't offer a resolution for this. In services.msc, the TPM services are set to auto, but it is self stopping (thus the error, but thought I'd add this in). If I were to guess - it's because you can't technically 'de-authenticate,' in the same way you can 'authenticate' from the 2003 domain. That being said - while I still haven't gotten to interface with server 2008 (and I'd give my eye teeth at the moment in time to have a pc I could use to put that machine to the test with vista.......and I would.. too! argh!), the 'deauthentication' process option, and especially in '03 SBS would be a significant addition to functionality in resolving a lot of issues. Anyway - any help would be appreciated, thanks.

    Thursday, October 18, 2007 5:32 PM
  •  sejong wrote:
    I wonder if the "Critical" level of the event is appropriate. 

    Though I agree with your logic, "critical" often just means impossible to continue.  "deal breaker" if you will.

    whereas "warning" is just something to consider
    Friday, October 19, 2007 5:45 AM
  •   cyberreaper:

    you should start another post.

    I believe the 5/6/8 30 models are the first to have tpm.  i have a 620 and it does not have one.
    Friday, October 19, 2007 5:47 AM
  • Mike Crowley--

    Good point.  Since it is possible to continue despite the lack of a TPM, the "Critical" status is not appopriate. 
    Friday, October 19, 2007 1:00 PM
  • at this point, you're preaching to the chior!


    Friday, October 19, 2007 2:29 PM
  • In RC1, this event's level has been reduced from Critical to Information.
    Friday, December 07, 2007 2:50 PM
  • nice to know microsoft reads the forums!


    Saturday, December 29, 2007 4:38 AM