Maqaalkan, waxaan sahamin doonaa sababta oo aan sidoo kale ku siin doonaa xalka arrinta Dhacdada 1098: Khaladka: 0xCAA5001C Token broker Operation ku guuldareystay^{(Event 1098: Error: 0xCAA5001C Token broker operation failed)} Windows 10^{(Windows 10)} . Waxaa laga yaabaa inaad la kulanto arrintan marka aad gasho a Windows 10 Kumbuyuutar ku salaysan oo aad isku daydo inaad gasho Store Store^{(Windows Store)} for Business . Si kastaba ha ahaatee, Xaqiijinta Tusaha Firfircoon ee Azure^{(Azure Active Directory)} ( AAD ) waa guuldareystay. iyo Event 1098 waxa la galiyay Microsoft- Windows - AAD /Operational log.

Aqoonsiga Dhacdada 1098^{(ID 1098)} : Cilad 0xCAA5001C, Hawlgalka dilaaliyaha Token waa fashilmay

Arrintani waxay dhacdaa haddii ay jiraan oggolaansho ama astaamo lahaanshaha ka maqan^{(missing permissions or ownership attributes)} mid ama labadaba furayaasha Diiwaangelinta ee soo socda:^(Registry)

HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\ Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\PSR

HKEY_USERS\S-1-5-21-299502267-1950408961-849522115-1818\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion \AppModel\SystemAppData\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\PSR

Ku dhig SID -ga laga soo warbixiyey isticmaalaha dhacdada aqoonsiga 1098^{(ID 1098)} ilaa dariiqa hoos yimaada HKEY_USERS . Xaaladdan oo kale, waa -

S-1-5-21-299502267-1950408961-849522115-1818

Si arrintan loo xalliyo, samee waxyaabaha soo socda:

1. Lahaanshaha furaha^{(Take ownership of the key)} haddii loo baahdo (Mulkiilaha = NIDAAMKA).

2. Hagaaji rukhsadaha furayaashan diiwaanka ee kor lagu soo bandhigay adiga oo awood u siinaya dhaxalka ( hagaajinta mid waa inay hagaajisaa labadaba ilaa isticmaaleyaal badan ay galaan isla qalab mooyaane). Hoos ka daawo sawirka:

Haddii aad aragto oggolaanshaha ~\PSR Registry furaha ee hoos yimaada HKEY_USERS\ { SID }, meesha laga^{(Inherited from)}  dhaxlay waxay muujinaysaa dhaxalka jidka HKEY_USERS\ { SID }.

Haddii ay tani xallin waydo arrinta, ka fiirso socodsiinta Habka Kormeerka^{(Process Monitor)} intaad samaynayso habka xaqiijinta si aad u raadiso ACCESS DIIDAY^{(ACCESS DENIED)} meelaha kale ee Diiwaanka^(Registry) ama nidaamka faylalka ee sababi kara fashilka xaqiijinta.

Arrintan ayaa laga yaabaa inay saamayso Bakhaarka Windows ee Ganacsiga iyo sidoo kale Ganacsiga Gobolka Roaming.^{(This issue may affect the Windows Store for Business as well as Enterprise State Roaming.)}

Event ID 1098: Error 0xCAA5001C, Token broker operation failed

In this post, we will explore the cause and also proνide the solution to the issue of Event 1098: Error: 0xCAA5001C Token broker operation failed in Windows 10. You might experience this issue when you log on to a Windows 10-based computer and you try to access Windows Store for Business. However, the Azure Active Directory (AAD) authentication fails. and Event 1098 is logged in the Microsoft-Windows-AAD/Operational log.

Event ID 1098: Error 0xCAA5001C, Token broker operation failed

This issue occurs if there are missing permissions or ownership attributes on one or both of the following Registry keys:

HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\ Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\PSR

HKEY_USERS\S-1-5-21-299502267-1950408961-849522115-1818\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion \AppModel\SystemAppData\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\PSR

Match the SID reported for the user in event ID 1098 to the path under HKEY_USERS. In this case, it is-

S-1-5-21-299502267-1950408961-849522115-1818

To resolve this issue, do the following:

1. Take ownership of the key if necessary (Owner = SYSTEM).

2. Fix the permissions on these registry keys shown above by enabling inheritance (fixing one should fix both unless multiple users log on to the same device). See the image below:

If you view the permissions of the ~\PSR Registry key under HKEY_USERS\{SID}, the Inherited from field shows inheritance from the HKEY_USERS\{SID} path.

If this does not resolve the issue, consider running Process Monitor while performing the authentication method to look for ACCESS DENIED in other areas of the Registry or file system that could be causing the authentication failure.

This issue may affect the Windows Store for Business as well as Enterprise State Roaming.

Related posts

• Aqoonsiga Dhacdada 158 qalad - Diskiga isku midka ah ee GUIDs ee ku jira Windows 10

• Hagaaji aqoonsiga Event ID 7031 ama 7034 qalad marka isticmaaluhu uu baxo Windows 10 kumbuyuutarka

• Sida loo saxo Dhacdada ID 642 ESENT qaladka Windows 11/10

• Hagaaji dhacdada ID7001 Maareeyaha Xakamaynta Adeegga Windows 11/10

• Aqoonsiga dhacdada 307 iyo 304 oo leh kood qalad 0x801c001d Windows 11/10

• Sida loo hagaajiyo DCOM Event ID 10016 qaladka Windows 10

• Xidhmada Fix lagama diiwaan gashan karo Windows 11/10

• Khaladka 2738, Ma geli karo wakhtiga runtime VBScript ee ficilka gaarka ah

• Hagaaji qaladka Runtime ee Logitech Setpoint Windows 10

• Hagaaji Bdeunlock.exe Sawirka Xun, Khaladka Nidaamka ama Aan ka jawaabin khaladaadka

• Adeeggu kama bilaabo khaladka Aqoonsiga Dhacdada 7000, 7009, 7011

• Nidaamka qalliinka lama bootin karo sababtoo ah khaladaadka darawalka

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

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

• Haah! Ma badbaadin karno midkaas - Windows Photos App

• Ku rakib Realtek HD Audio Driver Failure, Cilad OxC0000374 Windows 10

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

• Hagaaji Cilada Dukaanka Microsoft 0x87AF0001

• Hagaaji qaladaadka OOBEKEYBOARD, OOBELOCAL, OOBEREGION

• Khaladaadka hagaaji 0xC00D3E8E, Guriga waxaa lagu akhriyaa kaliya Windows 11/10