MZ@ !L!This program cannot be run in DOS mode. $;=ߍZSZSZSӬZSQZSRichZSPEd'}@0" ,0` (8.rdata@@.rsrc @@'}@0 lPP'}@0$8.rdata8.rdata$voltmdP.rdata$zzzdbg .rsrc$01(.rsrc$02 uZ|#.Please note that this machine is running with an outdated version of Antivirus Defender engine. After a new package version is released, support for the previous two versions is reduced to technical support only. Versions older than that are listed in this section, and are provided for technical upgrade support only.#Antivirus Microsoft Defender enginePlease note that this machine is running with outdated security intelligence version. It is recommended to apply the most recent security intelligence version to ensure optimal protection and compatibility.%Microsoft Defender Anti-Virus UpdatesPA9Sense High CPU usage is observed due to Sense NDR trafficDTry applying the Sense EDR exceptions to the following processes: %1PAHigh CPU UtilisationJMDE Platform experienced High Memory Utilisation with current MDE versionsHigh Memory UtilisationMDE Platform Update FailuresMDE Engine Update FailuresMDE Signature Update FailuresEMDE Signature Update are failing as there is already instance running_Wait for all process Instances of MpSigStub.exe is exited before trying signature update again.QMDE Windefend Service has failed to initialise successfully and stuck at stage %1eRestart the machine and update to latest defender platform and if issue persists report to Microsoft.PMDE Windefend Service has failed to shut down successfully and stuck at stage %1MUpdate to latest defender platform and if issue persists report to Microsoft.UMDE Exclusion references environment variable(s) (%1) which are not system variables.^Please review your exclusions: '%1' to make sure they reference correct environment variables.0Unable to retrieve Windows Defender preferences.If you intended to implement MDE Device Configuration Management, then please refer to the following article for more information.?Verify that Windows Defender service is running and accessible.9Configure Antivirus Microsoft Defender using Group PolicyConnectivity requirements@Configure hybrid Azure Active Directory join for managed domainsM365 Security PortalPAaTroubleshoot onboarding issues related to Security Management for Microsoft Defender for EndpointDefault MDE Policies keyDefault MDE Sensor Service key Default MDE Cache directory path Default MDE Cyber directory pathDefault MDE directory path&Default MDE ProgramData directory pathDefault MDE Temp directory path Default MDE Trace directory pathDelete the registry keys related to AntiSpoofing in order to force the device to generate a new private key and re-register. Run the command %1Nothing to do. During the duration of the time starting at Cyberthrottling start event sense cyberdata did not flow into the MDATP portal.This device attempted to onboard through Microsoft Monitoring Agent (MMA) agent but failed as it does not support onboarding using this method.Please refer to our online documentation to understand what onboarding method is appropriate for this device's Operating System.&MDE Onboarding Supported Configuration8The machine is associated with a specific AAD Tenant ID.Please ensure that the AAD Tenant ID from your MDE Tenant matches the SCP Tenant ID listed above. To see your MDE Tenant Identification please refer to the M365 Security Portal6Device is anti-spoofing capable and in a stable state.CSharedSignatureRoot is configured and accessible to SYSTEM account.1SharedSignatureRoot configuration appears normal.CSharedSignatureRoot registry value is not configured or accessible.eThis is informational - verify if SharedSignatureRoot configuration is expected for your environment.+Signature update schedule configuration: %15SignatureScheduleDay: %1, SignatureUpdateInterval: %2NReview your signature update schedule settings as needed for your environment.:Configure scheduled scans for Antivirus Microsoft Defender.SignatureDefinitionUpdateFileSharesSources: %1MReview signature file shares sources settings as needed for your environment.SignatureFallbackOrder: %1HReview signature fallback order settings as needed for your environment.Please note that this machine has a policy that only allows domain based trusted publishers to be added. This may interfere with MDE sensor which needs to install certificates to the Trusted Publisher store.For more information, refer to the article. To avoid unexpected issues, remove the associated group policy configuration: Local Authenticode Flags= %1, GP Authenticode Flags = %2.TrustedPublishersPA\Unable to read Service Connection Point (SCP) from Active Directory configuration partition.GService Connection Point (SCP) contains non-supported configuration: %1DService Connection Point (SCP) contains non-supported configuration.lThe device cannot be joined to Azure AD since the SCP record is configured to join device to Enterprise DRS.]Service Connection Point (SCP) is not configured in Active Directory configuration partition.^Unable to connect to Domain Controller to retrieve Service Connection Point (SCP) information.xThere is a discrepancy between the AAD Tenant ID from your MDE Tenant and the tenant ID in the SCP Entry of your domain.Please ensure that the AAD Tenant ID from your MDE Tenant matches the SCP Tenant ID listed above. To see your MDE Tenant Identification refer to the documentation.dThe device is managed by SCCM Agent and will not be managed by the MDE Security management solution.Configuration Manager is recognised as the single security management authority. Defender for Endpoint will not manage security settings on devices that are already managed by Configuration Manager. If you wish to change this behaviour you will need to set the Manage Security settings using Configuration Manager toggle to Off. Refer to the following documentation for additional information.:Device is anti-spoofing capable but not in a stable state.fPlease refer to the guidelines in the following article. Contact Microsoft support if issue persists.0Microsoft Defender for Endpoint - CVE-2022-232782Microsoft Defender for Endpoint - Threat AnalyticsDefault paths are missing: %1.Please ensure the mentioned missing path(s) exist and have not been renamed. You may need to create the missing folder(s) with system context.PAKThis device failed to onboard via Microsoft Endpoint Configuration Manager.uThis issue can happen if the registry key %1 is missing from: %2. To create the missing registry key you can use: %36Device is reporting to an expired Organisation ID: %1.?You should offboard the device from this organisation, and then onboard it to your current organisation. Contact Microsoft Support if you don't have access to the offboarding script with the mentioned OrgID. Note: To view the current OrgID, please go to the MDE portal and click on the username in the top right corner.Security CentrewPlease note the device has error 'Loading the private key for the client authentication certificate' in the OpsMgr log.pPlease uninstall and re-install MMA (Microsoft Monitoring Agent) on this device and check if the issue persists.?The local time on the device is not matching the time in Azure.vPlease check that the local system time is accurate and the correct time zone is set. If this device is domain joined, please ensure that the 'Windows Time' service is running and the device is synchronised with your domain time. For more information on how to configure and control time synchronisation please refer to the article to ensure local time in BIOS is accurate. WindowsTimeLDevice is running an older version of System Center Endpoint Protection: %1.You should upgrade to the latest available version to ensure compatibility and allow malware detections to be logged in the Defender for Endpoint security portal.=Error occurred in the security configuration management flow. The device was successfully onboarded to Microsoft Defender for Endpoint. However, there was an error in the security configuration management flow. This could be due to the device not meeting the prerequisites for Microsoft Defender for Endpoint management channel.1Prerequisites for Microsoft Defender for Endpoint=Error occurred in the security configuration management flow.The device was successfully onboarded to Microsoft Defender for Endpoint. However, Microsoft Endpoint Manager has not been configured through the Admin Centre to allow Microsoft Defender for Endpoint Security Configuration./Microsoft Endpoint Manager tenant configurationConnectivity issue occurred.The device was successfully onboarded to Microsoft Defender for Endpoint. However, there was an error in the security configuration management flow which could be due to a connectivity issue. Verify that the device can communicate with MDE Endpoints.?Azure Active Directory and Microsoft Endpoint Manager endpointsGeneral Hybrid join failure.The device was successfully onboarded to Microsoft Defender for Endpoint. However, there was an error in the security configuration management flow and the OS failed to perform hybrid join. Refer to links for troubleshooting OS-level hybrid join failures.9Troubleshoot hybrid Azure Active Directory-joined devicesTenant mismatch.The device was successfully onboarded to Microsoft Defender for Endpoint. However, there was an error in the security configuration management flow because your Microsoft Defender for Endpoint tenant ID doesn't match your Azure Active Directory tenant ID. Make sure that the Azure Active Directory tenant ID from your Defender for Endpoint tenant matches the tenant ID in the SCP entry of your domain.(Hybrid error - Service Connection Point.The device was successfully onboarded to Microsoft Defender for Endpoint. However, Service Connection Point (SCP) record is not configured correctly and the device couldn't be joined to Azure Active Directory. This could be due to the SCP being configured to join Enterprise DRS. Make sure the SCP record points to Azure Active Directory and SCP is configured following best practices. For more information refer to the links.$Configure a service connection pointCertificate error.-The device was successfully onboarded to Microsoft Defender for Endpoint. However, there was an error in the security configuration management flow due to a device certificate error. The device certificate belongs to a different tenant. Verify that best practices are followed when creating profiles.Trusted certificate profilesAAD Connect misconfiguration.-The device was successfully onboarded to Microsoft Defender for Endpoint. However, there was an error in the security configuration management flow due to a misconfiguration in AAD Connect. To identify what is preventing the device from registering to AAD, consider running the troubleshooting tools.'Device Registration Troubleshooter ToolAFor Windows Server 2012 R2 dedicated troubleshooting instructions DNS error.The device was successfully onboarded to Microsoft Defender for Endpoint. However, there was an error in the security configuration management flow due to a DNS error. Check the internet connection and/or DNS settings on the device. The invalid DNS settings might be on the workstation's side. Active Directory requires you to use domain DNS to work properly (and not the router's address). For more information, refer to the links.Clock sync issue.The device was successfully onboarded to Microsoft Defender for Endpoint. However, there was an error in the security configuration management flow. Verify that the clock is set correctly and is synced on the device where the error occurs.Policies download failure.The device was successfully onboarded to Microsoft Defender for Endpoint. However, the device was unable to download the endpoint security policies from MEM. Verify that the device can communicate with MDE Endpoints.Unenrollment failure.The device is currently enrolled but needs to be unenrolled. However, the unenrollment process was unsuccessful due to a transient error. Verify that the device can communicate with MDE Endpoints.Policies assignment failure.The device was successfully onboarded to Microsoft Defender for Endpoint and was able to download the endpoint security policies from MEM. However, there was a failure during the assignment of the policies.Policies report failure.The device was successfully onboarded to Microsoft Defender for Endpoint and was able to download the endpoint security policies from MEM. However, there was a failure during the report of the policies to MEM.PA]This device cannot be onboarded in current state as its ImageState inside '%1' is incomplete.This issue can happen if OS image has performed multiple consecutive sysprep attempts and registry was set to '%1'. Contact Microsoft support if issue persists.Windows Setup State InformationKThe ImagePath value in registry may have been tampered prior to onboarding.fPlease review this error and inspect the ImagePath (within %1) to ensure it points to a valid %2 path.)Sense cyberdata throttled events detectedMDE and ConfigMgrThe device is managed using Configuration Manager and Microsoft Defender for Endpoint. Controlling policies through both channels may cause conflicts and undesired results. To avoid this, endpoint security policies should be isolated to a single control plane.:Co-existence with Microsoft Endpoint Configuration ManagerEnrolment status Changed The device is managed using Configuration Manager and Microsoft Defender for Endpoint. The device was unenrolled from the security configuration management solution either because the enforcement scope has changed or the MDE-Management tag was removed from the device.The %%TEMP%% (and %%TMP%%) system environment variable is not defined. This can cause failures in Windows Defender and other system components that rely on a temporary directory.Define the TEMP and TMP system environment variables. The default value is %%SystemRoot%%\TEMP for system accounts. Verify the path exists and has appropriate permissions.The %%TEMP%% directory is not accessible. This can cause failures in Windows Defender components that need to write temporary files.XVerify the %%TEMP%% directory exists and the current account has read/write permissions.The %%TEMP%% directory is set to a non-default path. A non-standard TEMP path may cause issues with components that assume the default location.PAReview whether the custom %%TEMP%% path is intentional. If unexpected, reset TEMP and TMP system environment variables to the default value (%%SystemRoot%%\TEMP for system accounts).PPlease note the device has multiple MMA (Microsoft Monitoring Agent) workspaces.If the device is onboarded to Defender for Endpoint via ASC (aka Azure Defender for servers) integration, then it is recommended to remove the MDE workspace to avoid cyber upload issues. For more information on ASC integration with Defender for Endpoint please refer to the article. MDE in Azure|This machine has failed to onboard due to missing permissions for registry key HKLM_System_CurrentControlSet_Services_Sense.This can happen due to interference from third-party security products or if SYSTEM account full control permissions are missing for HKLM_System_CurrentControlSet_Services_Sense. The permissions found for SYSTEM account are: %1NPlease note that this server does not have the modern unified agent installed.Unified agent for downlevel servers is not installed on this device. It is recommended to install the new agent for optimal performance and protection capabilities. For more information refer to the documentationFOnboard Windows servers to the Microsoft Defender for Endpoint serviceYPolicies assignment failure occurred because of the following environment variable(s): %1&The device was successfully onboarded to Microsoft Defender for Endpoint and was able to download the endpoint security policies from MEM. However, there was a failure during the assignment of the policies. Please remove any non-existing path(s) from the above system environment variable(s).5Set environment variables in the System Control PaneliPolicies assignment failure occurred since Dynamic Fair Share Scheduling (DFSS) is enabled on the device.=The device was successfully onboarded to Microsoft Defender for Endpoint and was able to download the endpoint security policies from MEM. However, there was a failure during the assignment of the policies due to API limitation that can occur when DFSS is enabled. Please contact Microsoft support for assistance.MDevice is not up-to-date and does not have anti-spoofing capability deployed.Please ensure you deploy the recommended security patch to protect the device from spoofing, for more information refer to the links.0Microsoft Defender for Endpoint - CVE-2022-232782Microsoft Defender for Endpoint - Threat AnalyticsWDevice is running with an old version of the Microsoft Defender for Endpoint EDR sensorMPlease update the sensor to ensure you have optimal protection and stability.5Microsoft Defender for Endpoint update for EDR SensorThis machine has failed to onboard as MsSense.exe crashed during initialisation phase for TelLib.dll. The error from the crash was: %1This can happen if the SYSTEM account does not have permissions to write to the expected path (ProgramData\Microsoft\Windows Defender Advanced Threat Protection\Cyber). Please validate the ACLs in the path and reset the permissions from parent folder if needed.EDevice is anti-spoofing capable but is not yet registered with cloud.lPlease ensure connectivity to EDRCloud CnC URLs is not blocked. Contact Microsoft support if issue persists.MA configuration or dependency is preventing Network Protection from starting.TPlease review this error message to understand the blocking issue and resolve it: %1aSupported TLS cyphers are not enabled on this machine. This can affect connectivity to MDE cloud.Please inspect the configured cyphers (within HKLM\SOFTWARE\Policies\Microsoft\Cryptography\Configuration\SSL\00010002) to ensure it contains minimum required cyphers for connectivity to MDE cloud."Cypher suites and TLS requirementsbTLS 1.2 client protocol is not enabled on this machine. This can affect connectivity to MDE cloud.Please confirm that TLS 1.2 client is enabled (within HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client).PAXECDH cyphers are not enabled on this machine. This can affect connectivity to MDE cloud.Please confirm that ECDH KeyExchangeAlgorithm is enabled (within HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\ECDH).Basic URL test failedNetworkProtection component is disabled or failed URL check test. This may indicate a presence of a network redirector (Ex: Cisco Umbrella).gS\geD j/? [ <  9eY YQY.!gO ] eTc (%1). TVYeWU as' _ U O <LW:: 6 c B'Y[ B'.! @M> 'U, [ McuU8 YMV _7] 9?5 F[ [ YV#WB! < @B%QUB ; ;e gS</K e' 3M< _e8VF. 8+Uc>> c= VY B3, 3 OT;VqY VB UQ )  :#U  cW @g[/@/]  ? [U M5, R S-Ys g[ Tae.DY5]a <U7 _eW]/?#c+_ ? YUc 5W  D@Controlled Folder AccessFFailed to load mde_cfa_evaluation module - CFA diagnostics unavailable3Verify MdeDiag installation and module registration:No CFA (Controlled Folder Access) detections found in logs0No action required - CFA is functioning normally-Analysed %1 suspicious files for trust statusVReview CfaTrustChecks.txt in the diagnostic output for detailed trust analysis resultsA%1 is not trusted by CFA because process image is not known good.[Add it to list of allowed apps or add an AV exclusion for this file if you trust this file.>%1 is not trusted by CFA because its parent is not known good.8%1 is not trusted by CFA because its parent is a script.A%1 is not trusted by CFA because it loaded an untrusted file: %2.R%1 is not trusted by CFA because it was injected into by an untrusted process: %2.9Add an AV exclusion for this file if you trust this file.IAdd an AV exclusion for this process if you trust it (Process Exclusion).PA Process: %1 CFA Events: - Action: %1, Reason: %2 Taint Events:" - TaintType: %1, TaintReason: %2 Guidance: %1(%1 occurrences)PApASR %1 GUID '%2' (source: %3) has leading or trailing spaces/tabs which can prevent the rule from being applied.mRemove leading and trailing whitespace from the ASR Rule GUID in your Group Policy or registry configuration.ASR %1 GUID '%2' (source: %3) contains curly braces. GUIDs must be specified without braces (e.g. 56a863a9-875e-4185-98a7-b882c64b5ce5).^Remove the curly braces from the ASR Rule GUID in your Group Policy or registry configuration.rASR Exclusion '%1' (source: %2) has leading or trailing spaces/tabs which can prevent the exclusion from matching.rRemove leading and trailing whitespace from the ASR exclusion path in your Group Policy or registry configuration.ASR %1 GUID '%2' (source: %3) is not a valid GUID. Expected format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (e.g. 56a863a9-875e-4185-98a7-b882c64b5ce5).{Correct the ASR Rule GUID in your Group Policy or registry configuration to use valid GUID format without extra characters.ASR Exclusion '%1' (source: %2) contains a parent-directory ('..') segment. After resolving '..' the effective excluded path may be much broader than the literal entry suggests, silently expanding the exclusion beyond its intended scope.Replace the ASR exclusion entry with a fully-resolved absolute path that does not contain '..' segments. Recent versions of Microsoft Defender reject non-canonical exclusion entries at config load time.%What is Defender Diagnostic Insights?Defender Diagnostic Insights is a self-help diagnostics tool that collects and analyses the diagnostic data, and provides a report to help troubleshoot Windows virtual machine performance problems in Azure. Defender Diagnostic Insights Windows documentation is %1.'Where do I start to review this report?Start with the Overview tab. Review the recommendations and links for the findings. Learn about how they can affect performance, and also about best practices for performance-optimised configurations. Learn more about reviewing the report %1.?What kind of data is collected by Defender Diagnostic Insights?Defender Diagnostic Insights collects information about the Windows VM, disks or storage pools configuration, performance counters, high resource consumers, logs, and various traces. Details about what kind of information is collected by Defender Diagnostic Insights is %1.PPPPh`An error occurred while running LUA module. lAn error occurred while loading LUA file module. TSyntax error occurred in LUA module. @LUA memory error occurred. @LUA general error occurred. <LUA panic error occurred. pLUA execution has been interrupted by stop signal. Failed to dynamically configure heap snapshots for process. 4VS_VERSION_INFOee?fStringFileInfoB080904B0LCompanyNameMicrosoft Corporation2FileDescriptionMicrosoft Defender for Endpoint Diagnostic EngineBInternalNamedefenderdiag.dll.LegalCopyright Microsoft Corporation. All rights reserved.ROriginalFilenamedefenderdiag.dll.muij%ProductNameMicrosoft Windows Operating System8FileVersion4.18.26080.3 (9e1f3147fbc83f18a98a965394a23e07747d7295)> ProductVersion4.18.26080.3DVarFileInfo$Translation PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDING(0( *H '0'10  `He0\ +7N0L0 +70 010  `He 8Z_V¹`a4m2rt{K鹠 0a0I3$]q $0  *H  0S1 0 UUS10U Microsoft Corporation1$0"UWindows Production PCA 20230 260430183934Z 270429183934Z0p1 0 UUS10U Washington10URedmond10U Microsoft Corporation10UMicrosoft Windows00  *H 04bIp%x3 m˝~83`;P#tίeC #3& j1zQ ,-KM_ɨ$8 /?vE^WxqenQvϗ3I~dBoK>w/LF "U HP LR.k'mAѶtի !N _GaE3X2r0{:sV1!iaF4j8..wk!G' Xn̍d%&_'94ˑk[;?9ēx+vE->LTC_ n#o]yOgVgHG+?atʮ,1^r-15t00U0U%0 +7 +0U+NN"! 0EU>0<:0810U Microsoft Corporation10U 500446+5079150U#0 ?Z =!U1S"0ZUS0Q0OMKIhttp://www.microsoft.com/pkiops/crl/Windows%20Production%20PCA%202023.crl0g+[0Y0W+0Khttp://www.microsoft.com/pkiops/certs/Windows%20Production%20PCA%202023.crt0 U00  *H  4Z  1 ˫5FV5;DŐ-%ۚi Mr'4Ɣ!I皸a08.wq ̔`Щ!əO{yeNuj҂XfC ˼S. TQGR|d5$kOJL3$|!&O̅X=H\\ {PΞe;ϳb'iN۲c -fx9b+V#)!˜y^\);W툊kLf3S71 rP`FVsa /C)Ҩ:/Њ$nEh1womGP6h~!R&ar!4 Bswr_ew|8bPOB_L;p5zΙ/2)ta#Z\ԝ l(CR|3!^ B$V H, FD?003V K!0  *H  01 0 UUS10U Washington10URedmond10U Microsoft Corporation1200U)Microsoft Root Certificate Authority 20100 230613183415Z 350613184415Z0S1 0 UUS10U Microsoft Corporation1$0"UWindows Production PCA 20230"0  *H 0 . ]nqKHb!NF-iY3'xv} /gW@SpגrKҳ>e)Vƃo[y2i]U`˰ʹgxLm%5uG<>#ҥ_x Bf.ޕFo)ݹ<-}έ=p2蝁yQUAoCĵZU~f*>PI!#x(LiinjkIsWL3uoĿX-*e+H$ y\ n%8!_>Զ RH0ƥ>f~4Qbo=5?QI^}PuOlzp0H}qRQ#O3 J/xw_ W;Q5x?Epd"Hi'ư http://www.microsoft.com/pki/certs/MicRooCerAut_2010-06-23.crt0  *H  0Bh߄\d"nh~U(ejZ-@20260815031021.02Z0Ѥ01 0 UUS10U Washington10URedmond10U Microsoft Corporation1%0#U Microsoft America Operations1'0%U nShield TSS ESN:8900-05E0-D9471%0#UMicrosoft Time-Stamp Service0 03"Aȵ"0  *H  0|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20100 260219193956Z 270517193956Z01 0 UUS10U Washington10URedmond10U Microsoft Corporation1%0#U Microsoft America Operations1'0%U nShield TSS ESN:8900-05E0-D9471%0#UMicrosoft Time-Stamp Service0"0  *H 0 ≺B.R&cFn/%6Qm!:h۵7c\_^FҪY43?D!+ ;,G *rd/[:u=j ?LW Dz?2Em5\#}I\[>7OxFYvY)9[iJS?.0z:?oUkr2Z/ڕr&1 p<hxAA A9+ :3:W}xn\9O!!m>n9F具ON>Qz(%Rh,< ,S8}aEJB_\ tZo< 縘\ b&k5X䪂PD]bI%2@'/%rrI0E0UYj'[H-*j0U#0]^b]eS5r0_UX0V0TRPNhttp://www.microsoft.com/pkiops/crl/Microsoft%20Time-Stamp%20PCA%202010(1).crl0l+`0^0\+0Phttp://www.microsoft.com/pkiops/certs/Microsoft%20Time-Stamp%20PCA%202010(1).crt0 U00U% 0 +0U0  *H  bϧpom%j> ._;%-1dӍ/yPmM<_d}҄b!2L;wn~3 }2UmÅd71T:$n8OiU{w:"zsv~=$u Bk #.F]4Z#OqNO*9W3radb;hb؛4B!% {F7L ˕ ]Z5] E$V1Ο 7x*Έwd. _+ϪX}B>o9 ;)Ȭ+'ˠ'2B2^ⵌV@,LMYȜ%wHrM/0q0Y3kI0  *H  01 0 UUS10U Washington10URedmond10U Microsoft Corporation1200U)Microsoft Root Certificate Authority 20100 210930182225Z 300930183225Z0|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20100"0  *H 0 Lr! y$yՂҩlNu5WlJ⽹>`3\OfSqZ~JZ6gF# w2`}jRDFkvPDq\Q17 8n&S|9azĪri65&dژ;{3[~Rb%j]SVMݼ㑏9,Qpi 6-p15(㴇$ɏ~TUmh;Fz)7EFn20\O,b͹⍈䖬Jq[g`= s}AFu_4 }~ٞE߶r/}_۪~66L+nQsM7t4G|?Lۯ^s=CN39LBh.QFѽjZasg^(v3rק  co 6d[!]_0tعP a65Gk\RQ]%PzlrRą<7?xE^ڏriƮ{>j.00 +70# +7*RdĚhttp://www.microsoft.com/pki/certs/MicRooCerAut_2010-06-23.crt0  *H  U}*,g1$[rKo\>NGdx=139q6?dl|u9m1lѡ"fg:SMݘx6.Vi {jo)n?Hum m#TxSu$Wݟ=heV(U'$@]='@8)üTB  jBRu6as.,k{n?, x鑲[It 쑀=J>f;O2ٖtLrou04zP X@1Q{p( 6ںL 4$5g+ 挙"'B=%tt[jў>~13}{8pDѐȫ::bpcSMmqjU3XpfM050Ѥ01 0 UUS10U Washington10URedmond10U Microsoft Corporation1%0#U Microsoft America Operations1'0%U nShield TSS ESN:8900-05E0-D9471%0#UMicrosoft Time-Stamp Service# 0+g۰:Iչ)30~0|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20100  *H  *:0"20260815010852Z20260816010852Z0t0: +Y 1,0*0 *:0`00 +$06 +Y 1(0&0  +Y  0 00  *H  1Lde 3+Jܮy@¿D]:p kqfDc,ڧc Hb!Ma'Qx95"@T0ƓFHӔd<; C/Ǣ Y2Ya됮U.DQ0_rLN_=z AM(%ed$o>4|#  ~wLZ.N;1 0 00|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20103"Aȵ"0  `HeJ0 *H  1  *H  0/ *H  1" )]PYyzIqBwtJˡb0 *H  /1000 `] Ƃ3l`Ι  00~0|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20103"Aȵ"0" Pܡm]F6qI&r2.M5c0  *H  q>m&-(ԛ9]޺x- (s[y|baAx^6pLAD뿼U}}Gოq\uljP@}SrDͽ<<_ O!\휞\d `h N;L6}Vϋ޵aarlHZn3W*w[ y)+rdo|^LΈA`v !W:,=(DΊyT{j}x l6LI?){,'pug?7={!#0iŐMKNhXg|=GGਕ n<%-U .!tXYTH@9%:Kr\Zk쾥i7rשּׁ"/Yi6u(!b<R3t{D7jGxHy