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.