Windows 11: TBS service missing with Error 1060 while TPM 2.0 is healthy

GOVIND SINGH 0 Reputation points
2026-11-20T06:26:12.3233333+00:00

I am developing a Windows ERP security component that requires supported TPM 2.0 NV read/increment operations for monotonic anti-rollback protection.

The TPM itself is healthy and ready, but:

sc.exe qc TBS

returns Error 1060: The specified service does not exist as an installed service.

I have already completed:

  • DISM RestoreHealth successfully
  • SFC /scannow with no integrity violations
  • Windows repair reinstall while preserving apps, files, and settings

After all these steps, TBS still returns Error 1060.

Questions:

  1. Is TPM Base Services (TBS) expected to be registered as a service on current Windows 11 builds?
  2. If TBS service registration is intentionally absent, what Microsoft-supported Windows API should an application use for TPM 2.0 NV read/increment operations?
  3. If TBS should be present, what is the Microsoft-supported remediation?

I do not want to manually create/register TBS, clear the TPM, weaken TPM security, or use an unsupported workaround.I am developing a Windows ERP security component that requires supported TPM 2.0 NV read/increment operations for monotonic anti-rollback protection.

The TPM itself is healthy and ready, but:

sc.exe qc TBS

returns Error 1060: The specified service does not exist as an installed service.

I have already completed:

  • DISM RestoreHealth successfully
  • SFC /scannow with no integrity violations
  • Windows repair reinstall while preserving apps, files, and settings

After all these steps, TBS still returns Error 1060.

Questions:

  1. Is TPM Base Services (TBS) expected to be registered as a service on current Windows 11 builds?
  2. If TBS service registration is intentionally absent, what Microsoft-supported Windows API should an application use for TPM 2.0 NV read/increment operations?
  3. If TBS should be present, what is the Microsoft-supported remediation?

I do not want to manually create/register TBS, clear the TPM, weaken TPM security, or use an unsupported workaround.

Windows development | Windows API - Win32
0 comments No comments

2 answers

Sort by: Newest
  1. Gatlin Le (WICLOUD CORPORATION) 1,475 Reputation points Microsoft External Staff Moderator
    2026-11-20T08:19:22.9833333+00:00

    Hi @GOVIND SINGH ,

    Thank you for the detailed write-up. Since you already went through DISM, SFC, and a repair install and still hit the same error, I understand why this is frustrating, and I appreciate that you want to stay on a supported path for a security component.

    I tested this on a Windows 11 Pro VM (26H2, build 26300.9457) with TPM 2.0 present and ready, and I can confirm the same symptom you reported. sc.exe qc TBS returned OpenService FAILED 1060, and the HKLM\SYSTEM\CurrentControlSet\Services\TBS key did not exist. On that same machine, Tbsi_Context_Create for TPM 2.0 returned TBS_SUCCESS and Tbsip_Context_Close returned 0x0. sc.exe qc TBS still returned 1060 after those calls.

    On whether TBS is expected to be registered as a service, About TBS describes TBS as a system service that is preinstalled on all systems with a TPM starting with Windows 8, and says applications reach it through a DLL that exposes the C interface. I could not find any public documentation that says TBS must appear in the Service Control Manager under the name TBS on current Windows 11 builds, or that this registration was intentionally removed. My test shows the same 1060 result on build 26300.9457, but neither the test nor the docs establish whether that is by design. The documentation also does not present sc.exe qc TBS as a way to check whether TBS is available.

    As for the API, the documented interface for sending TPM 2.0 commands, including NV commands such as TPM2_NV_Read and TPM2_NV_Increment, is TPM Base Services in tbs.h (Tbs.lib, Tbs.dll). Per Tbsi_Context_Create and TBS_CONTEXT_PARAMS2, a TPM 2.0 caller creates a context with version set to TPM_VERSION_20 and includeTpm20 set to 1, then submits marshalled command buffers with Tbsip_Submit_Command. That page says only locality zero is currently supported, and that a command can be submitted successfully and still fail at the TPM, with the TPM error code returned in the result buffer. Command Blocking adds that TPM 2.0 commands go through an allow list, which has been fixed in the TPM driver since Windows 10 1809. My test only covered creating and closing a context. I did not submit NV commands, so I cannot confirm that NV read and increment pass that list on this build.

    On remediation, I could not find any Microsoft-documented procedure for restoring TBS service registration beyond the repair steps you already completed. I agree with your decision not to register the service manually or clear the TPM.

    Since the docs do not say whether the missing SCM entry is by design or a servicing issue, and you need a supportable answer for a production security component, I recommend raising this with Windows Developer Support. Please include the exact Windows build, your repair history, and the sc.exe output, so the team can confirm the intended behavior for your build directly.

    I hope the test results and the references above help clarify what the public documentation does and does not commit to regarding TBS registration on current Windows 11 builds, and make it easier to decide how to approach the remaining points with Windows Developer Support. If you feel the information has helped you move forward, you are welcome to follow this guidance when convenient, as it can help others with the same question find it more easily. If you later receive clarification from Microsoft or come across additional documentation on this behavior, you are always welcome to share it here as well.

    Thank you.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-20T06:27:34.9833333+00:00

    Test Tbsi_Context_Create rather than using sc.exe qc TBS as the availability check, and use Tbsip_Submit_Command to send properly marshalled TPM 2.0 NV commands when that context succeeds.

    Service status on current Windows 11

    Microsoft’s public documentation still describes TBS as a system service, preinstalled on Windows 8/Windows Server 2012 and later on systems with a TPM.^1^ It does not document Error 1060 as expected behavior or state that the TBS Service Control Manager registration was intentionally removed from a particular Windows 11 build.

    A directly matching Windows 11 report documents the same missing-service symptom, but it has no accepted or recommended answer.^2^ Therefore:

    • Error 1060 alone does not establish that TPM access is unavailable.
    • It also cannot be declared officially intentional from the currently published documentation.
    • Do not create an SCM service entry manually; that would not be a documented TBS installation procedure.

    Supported API for TPM 2.0 NV operations

    The supported native Windows interface is the TPM Base Services API in tbs.h, linked through Tbs.lib and implemented by Tbs.dll.^3^

    For TPM 2.0:

    1. Create a TBS context with Tbsi_Context_Create.
    2. Set TBS_CONTEXT_PARAMS2.version to TPM_VERSION_20.
    3. Set the reserved field to zero and includeTpm20 to 1.
    4. Marshal the applicable TPM 2.0 command—such as TPM2_NV_Read or TPM2_NV_Increment—into a byte buffer.
    5. Submit it with Tbsip_Submit_Command.
    6. Parse both layers of status:
      • the returned TBS_RESULT;
      • the TPM response code in the returned TPM response buffer.

    A minimal availability probe is:

    #include <windows.h>
    #include <tbs.h>
    
    TBS_HCONTEXT context{};
    TBS_CONTEXT_PARAMS2 params{};
    params.version = TPM_VERSION_20;
    params.includeTpm20 = 1;
    params.includeTpm12 = 0;
    
    TBS_RESULT result = Tbsi_Context_Create(
        reinterpret_cast<PCTBS_CONTEXT_PARAMS>(&params),
        &context);
    
    if (result == TBS_SUCCESS) {
        Tbsip_Context_Close(context);
    }
    

    Tbsi_Context_Create is the documented operation that creates the handle used to pass commands to TBS. It can return specific errors including TBS_E_SERVICE_NOT_RUNNING, TBS_E_SERVICE_DISABLED, and TBS_E_TPM_NOT_FOUND.^4^

    Submit an already-marshalled command as follows:

    UINT32 responseSize = sizeof(response);
    TBS_RESULT result = Tbsip_Submit_Command(
        context,
        TBS_COMMAND_LOCALITY_ZERO,
        TBS_COMMAND_PRIORITY_NORMAL,
        command, commandSize,
        response, &responseSize);
    

    Only locality zero is currently supported. A successful TBS submission can still contain a TPM-level failure in the response buffer, so check the TPM response code before accepting an NV read or increment as successful.^5^

    TBS schedules access across competing callers and passes other TPM commands through after handling relevant resource virtualization.^6^ The application remains responsible for TPM 2.0 wire-format marshalling, sessions, authorization, NV index attributes, policies, and response parsing. TBS is not a high-level NV counter API.

    How to interpret the API probe

    • TBS_SUCCESS: TBS is operational despite sc.exe returning 1060. Treat the SCM query as unsuitable for feature detection and continue through the API.
    • TBS_E_TPM_NOT_FOUND: the requested TPM version was not found. Investigate TPM exposure/version rather than service registration.
    • TBS_E_SERVICE_NOT_RUNNING or TBS_E_SERVICE_DISABLED: this is an actual TBS availability failure, unlike SCM Error 1060.^7^
    • TBS_E_ACCESS_DENIED: review the caller context and whether the command is blocked. Windows 8 and later permit standard-user and administrator access, but TBS restricts certain TPM commands through command blocking.^8^

    Supported remediation if the API fails

    Since DISM, SFC, and an in-place repair installation have already completed without restoring the SCM entry, repeating them is unlikely to distinguish the issue.

    There is no documented Microsoft procedure in these sources to reconstruct or manually register TBS. If Tbsi_Context_Create returns a TBS service error on an otherwise healthy TPM:

    1. Record the exact Windows edition, build and revision from winver.
    2. Capture the exact TBS_RESULT in hexadecimal.
    3. Confirm that Tbs.dll loads and record any relevant TPM/TBS event logs, without modifying service or TPM state.
    4. Open a Microsoft Support case with the API result and repair history, asking whether that build intentionally hosts TBS without a visible SCM entry or has a servicing defect.

    Clearing the TPM is not appropriate merely for Error 1060 or a missing SCM entry. Microsoft warns that clearing it removes TPM-held keys and can cause data loss; TPM clearing belongs to specific initialization or lockout recovery scenarios, neither of which is established here.^9^


    References

    1. About TBS - Win32 apps | Microsoft Learn
    2. Windows 11 — TBS (TPM Base Services) not present: support status and user-mode alternatives for NV / monotonic counter - Microsoft Q&A
    3. TPM Base Services
    4. Tbsi_Context_Create function (tbs.h)
    5. Tbsip_Submit_Command function (tbs.h)
    6. Command Scheduling
    7. TBS Return Codes
    8. Using TBS
    9. Troubleshoot the TPM
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.