Haddii ka dib markii si guul leh loo geeyo Windows 10 oo aad aragto in Module Platform ee la aamini karo (TPM) uu ku jiro qaab shaqeyneed oo hoos u dhacay, markaa boostadan waxaa loogu talagalay inay ku caawiso. Maqaalkan, waxaan ku aqoonsan doonaa qaar ka mid ah sababaha la garan karo ee dhaqankan ka dibna waxaan bixin doonaa xalinta arrintan iyo sidoo kale cabbirka aad qaadi karto si aad uga hortagto in arrintu dhacdo inta lagu jiro hawlgalka Windows 10 .

Waxaa laga yaabaa inaad la kulanto arrintan iyadoo ku saleysan xaaladdan soo socota.

Waxaad isticmaashaa Qalabka Dajinta^{(Deployment Toolkit)} Microsoft (Tani waxay noqon kartaa nooc kasta oo MDT ah oo taageera Windows 10 ) si aad u geyso Windows 10 adoo isticmaalaya " Enable BitLocker (offline) " tillaabada (ZTIBDE.wsf script) si loo sii diyaariyo BitLocker^(BitLocker) inta lagu jiro Windows PE ee " Horay loo soo dajiyay^(Preinstall) ” kooxda oo diritaanku waa lagu guulaystay.

Si kastaba ha ahaatee, muuqaalkan, waxaad ogaanaysaa in Module Platform ee^{(Trusted Platform Module)} la aamini karo ( TPM ) uu ku jiro qaab shaqayneed oo hoos u dhacay. Xaaladdan oo kale, TPM^{(TPM Management)} Console Management ( TPM.msc ) ayaa ka warbixiya arrinta soo socota:

TPM waa diyaar in la isticmaalo, iyada oo hoos u dhac ku yimi shaqaynteeda. Calanka Macluumaadka: 0x900 Oggolaanshaha lahaanshaha
TPM si^(TPM) fiican looguma kaydin diiwaanka.
Macluumadka diiwaanka Windows ee ku saabsan TPM's Storage Root Furaha^{(Storage Root Key)} kuma habboona TPM Keydka Xididdada Furaha^{(TPM Storage Root Key)} ama waa maqan yahay.

TPM waa diyaar in la isticmaalo, iyada oo hoos u dhac ku yimi shaqaynteeda

Haddii aad la kulanto TPM^{(TPM reduced functionality )} arrin la dhimay shaqada, waxaad ka shaqayn kartaa arrintan si aad u dirto cusub ilaa nooc cusub oo MDT ah laga helayo - ku dar amarka hoose qoraalka ZTIBDE.wsf bilowga qaybta " Full function Main^{(Function Main)} " :

reg add hklm\system\currentcontrolset\services\tpm\wmi -v UseNullDerivedOwnerAuth -t REG_DWORD -d 0x01 -f

Waxaa xusid mudan in aaladaha ay TPM -gu horeba ugu jiraan qaab shaqayneed oo la dhimay, TPM waa in la nadiifiyaa^{(TPM must be cleared)} ka hor intaadan yareynin arrintan.

Si looga hortago in arrintani dhacdo, waxaad u baahan doontaa inaadan horay u bixin BitLocker , beddelkeeda sug inaad awood u siiso nidaamka buuxa. La soco in hawlgelinta ay qaadan doonto waqti dheer in la dhammaystiro adiga oo isticmaalaya habkan.

Marka loo eego Microsoft, TPM^{(TPM reduced functionality )} arin hawleed dhimis ayaa dhacda sababtoo ah shaqada TpmValidate  ee ku jirta qoraalka ZTIBDE.wsf ayaa lahaanshaha TPM ka qaadanaya Windows PE si aan loo baahnayn. Daaqadaha waa inay awood u yeeshaan inay si sax ah u qaataan lahaanshaha TPM ka hor Khibradda Ka-baxsan-Box (OOBE)^{(Out-of-Box Experience (OOBE))} si ay u bixiso iyadoo la adeegsanayo cabbirrada saxda ah. 

Marka isbeddelkan ku yimaadda lahaanshaha TPM ee Windows PE dhaco, TPM waxaa la siiyaa xaddiyada aysan Windows fahmin. Sidaa darteed, kala sareynta muhiimka ah ee TPM waa naafo oo waxay ka dhigeen mid aan si joogto ah loo heli karin Windows .

The TPM is ready for use, with reduced functionality

If after a successful deployment of Windows 10 and you notісe that the Trusted Рlatform Module (TPM) is in reduced functionality mode, then thіs post is intended to help you. In this post, we will identify some potential known causes for this behavior and then provide the wоrkaround for thіs issue as well as thе measure you can take to prevent the issυe from oсcurring during the deployment of Windows 10.

You might encounter this issue based on the following scenario.

You use Microsoft Deployment Toolkit (This can be any version of MDT that supports Windows 10) to deploy Windows 10 by using the “Enable BitLocker (offline)” step (ZTIBDE.wsf script) to pre-provision BitLocker during Windows PE in the “Preinstall” group and the deployment is successful.

However, in this scenario, you notice that the Trusted Platform Module (TPM) is in reduced functionality mode. In this situation, the TPM Management console (TPM.msc) reports the following issue:

The TPM is ready for use, with reduced functionality. Information Flags: 0x900
The TPM owner authorization is not properly stored in the registry.
Windows’s registry information about the TPM’s Storage Root Key does not match the TPM Storage Root Key or is missing.

The TPM is ready for use, with reduced functionality

If you’re faced with the TPM reduced functionality issue, you can work around this issue for new deployments until a new version of MDT is available – add the command below to the ZTIBDE.wsf script at the start of the “Function Main” section:

reg add hklm\system\currentcontrolset\services\tpm\wmi -v UseNullDerivedOwnerAuth -t REG_DWORD -d 0x01 -f

It is worth noting that devices in which the TPM is already in reduced functionality mode, the TPM must be cleared before you can mitigate this issue.

To prevent this issue from occurring, you’ll need to not pre-provision BitLocker, instead wait to enable the full system. Be aware that the deployment will take longer to complete by using this method.

According to Microsoft, the TPM reduced functionality issue occurs because the TpmValidate function in the ZTIBDE.wsf script takes ownership of the TPM from Windows PE unnecessarily. Windows should be able to correctly take ownership of the TPM before Out-of-Box Experience (OOBE) to provision it by using the correct parameters. 

When this change in ownership of the TPM from Windows PE occurs, the TPM is given parameters that Windows does not understand. Therefore, the key hierarchies in the TPM are disabled and made permanently unavailable to Windows.

Related posts

• Hagaaji Digniin Qalabka TPM laguma ogaan qaladka kombayuutarrada Dell

• Daaqadaha ma xaqiijin karaan saxiixa dhijitaalka ah (Koodhka 52)

• Hagaaji kaydku waa qaab aan la garanayn ama khalad dhaawacmay

• Habkani waxa uu u baahan yahay warbaahin meesha laga saari karo - Qaladka dib u dejinta erayga sirta ah

• Hagaaji cilada soo galitaanka dukaanka Microsoft 0x801901f4 Windows 11/10

• Darawalku waxa uu ku ogaaday cilad darawalka gudaha DeviceVBoxNetLwf

• Khalad ayaa dhacay iyadoo lagu dabaqayo sifooyinka faylka gudaha Windows 11/10

• Wax baa khaldamay, Demi software ka-hortagga fayraska, 0x8007045d

• Cilad 1327 Invalid Drive marka la rakibayo ama la furayo barnaamijyada

• Sida loo xaliyo dhibaatada isku dhaca Saxeexa Disk ee gudaha Windows 11/10

• Barnaamijku ma bilaaban karo sababtoo ah AppVIsvSubsystems32.dll ayaa maqan

• Fadlan geli warbaahinta kaydinta dibadda oo tabo OK

• Hagaaji Windows 10 Cusbooneysii Qaladka Rakiba 0x8007042B - 0x2000D

• MBR2GPT waxay ku guuldarraysatay inay awood u siiso kaydinta/soo celinta mudnaanta Windows 10

• Dejintu way awoodi wayday inay ku abuurto khalad qaybta qaybta cusub ee Windows 10

• Hagaaji Smart Check way dhaaftay, DST Gaaban Cilad ku fashilantay kombayutarka HP

• Hagaaji qaladka Codsiga 0xc0150004 gudaha Windows 11/10

• Sida loo hagaajiyo Start PXE IPV4 gudaha Windows 11/10

• Meel banaan oo dheeraad ah ayaa looga baahan yahay wadista meesha lagu rakibay Windows

• Hagaaji ShellExecuteEx wuu fashilmay; qaladka code 8235 ee Windows10