MZ@ !L!This program cannot be run in DOS mode. $=;=yZSyZSyZSӬxZSQxZSRichyZSPEd." ,` d%8.rdata@@.rsrc @@. lPP.$8.rdata8.rdata$voltmdP.rdata$zzzdbg @.rsrc$01@'X.rsrc$02 }P`a~cj|K"fL.00H `x!?E F8GPHhLRS~(@9Xxp0H`3x4r      0 @ P ` p             0 @ P ` p            8''x)+-"$..x@/H1t4\609;=MD\~\bh4oPpTwNz8 ܃v T ><6t:j LtMUI;~̸t !9?Aֶn MUI en-UShereNo issues found."No detailed information available.Supporting Data: Impact LevelFindingRecommendation ReferencesFeedbackCategoryAnalysisErrorWarning InformationalToggle navigationPA#Defender Diagnostic Insights ReportOverviewNetwork Communications Deployment OnboardingHealthUpToDatePerformance IssuesConfiguration IssuesCFAHelpASRN/ANot configured%1 hoursEverydaySundayMondayTuesday WednesdayThursdayFridaySaturdayNeverNetwork Communications TestsMDE Deployment TestsMDE Onboarding TestsMDE Feature Health TestsMDE Up-To-Date TestsPerformance TestsConfiguration Tests$CFA (Controlled Folder Access) TestsPA$ASR (Attack Surface Reduction) TestsDisabledBlockAudit UnavailableYESNO%1 service not present Not available Unknown StateProcessFilePAFindingsFindings2Click Analysis link to see the detail of findings.Machine InformationMachine InformationVMNameVMSize VMLocationSubscriptionId ResourceGroupVmId OSVersionNumber of coresNumber of logical processorsThreads per corePhysical MemoryPageFile LocationPageFile Current UsagePageFile Allocated Base SizePageFile Peak Usage Domain JoinedAzure AD JoinedWorkplace JoinedAzure AD Device IDEnrollment StatusOS ArchitectureSystem Boot TimeSystem-wide WinHTTP Proxy!Device is enrolled to AAD and MEM2Device is not enrolled and has never been enrolledDevice is managed by MDM AgentDevice is managed by SCCM Agent.Microsoft Endpoint Manager Configuration issue General errorConnectivity issue)Device was enrolled and is now unenrolledDevice is pending unenrollmentPolicies assignment failurePolicies report failureGeneral Hybrid join failureTenant mismatch'Hybrid error - Service Connection PointCertificate errorAAD Connect misconfiguration DNS errorClock sync issueMDE and ConfigMgrPAEDRSense Information Sense versionSense service StatusOrganization Id Device IDAnti-Spoofing State GUIDDiagTrack (UTC) Service Status!Anti-Spoofing capability deployedSense Configuration versionMachineAuth IDSense service StartTypeDevice Datacenter Location-Device Onboarded via Streamlined Connectivity.Microsoft Account Sign-in Assistant Start TypePA Defender AVDefender AV InformationDefender AV Service StatusDefender AV Platform Version)Defender AV Security Intelligence VersionDefender AV engine VersionDefender AV mode$Defender AV SSLOptions configurationDefender AV proxy configuration&Windows Security Center Service Status&Windows Security Health Service Status*Defender Network Inspection Service StatusDefender Core Service StatusDefender Is Tamper Protected!Defender Tamper Protection Source(Defender Is Tamper Protection ExclusionsSmartLocker ModeDefender Anti-Spyware Defender Network Protection ModeuPlease review your network configuration and ensure required URLs are not blocked. For more information refer to: %1 ServiceURLsyTest connection to the Microsoft Defender for Endpoint (CnC) cloud service URLs completed successfully. %1 with result %2Test connection to the Microsoft Defender for Endpoint (CnC) cloud service URLs failed. The test has failed for the following URL: %1 with result %2All test connections to Microsoft Defender for Endpoint (CnC) cloud service URLs have failed. The test has failed for the following URL: %1 with result %2{Test connection to the Microsoft Defender for Endpoint (Cyber) cloud service URLs completed successfully. %1 with result %2Test connection to the Microsoft Defender for Endpoint (Cyber) cloud service URLs failed. The test has failed for the following URL: %1 with result %2All test connections to Microsoft Defender for Endpoint (Cyber) cloud service URLs have failed. The test has failed for the following URL: %1 with result %2|Test connection to the Microsoft Defender for Endpoint (AutoIR) cloud service URLs completed successfully. %1 with result %2Test connection to the Microsoft Defender for Endpoint (AutoIR) cloud service URLs failed. The test has failed for the following URL: %1 with result %2All test connections to Microsoft Defender for Endpoint (AutoIR) cloud service URLs have failed. The test has failed for the following URL: %1 with result %2Test connection to the Microsoft Defender for Endpoint (SampleUpload) cloud service URLs completed successfully. %1 with result %2Test connection to the Microsoft Defender for Endpoint (SampleUpload) cloud service URLs failed. The test has failed for the following URL: %1 with result %2All test connections to Microsoft Defender for Endpoint (SampleUpload) cloud service URLs have failed. The test has failed for the following URL: %1 with result %2Test connection to the Microsoft Defender for Endpoint (MdeConfigMgr) cloud service URLs completed successfully. %1 with result %2Test connection to the Microsoft Defender for Endpoint (MdeConfigMgr) cloud service URLs failed. The test has failed for the following URL: %1 with result %2All test connections to Microsoft Defender for Endpoint (MdeConfigMgr) cloud service URLs have failed. The test has failed for the following URL: %1 with result %2{Test connection to the Microsoft Defender for Endpoint (OneDs) cloud service URLs completed successfully. %1 with result %2Test connection to the Microsoft Defender for Endpoint (OneDs) cloud service URLs failed. The test has failed for the following URL: %1 with result %2All test connections to Microsoft Defender for Endpoint (OneDs) cloud service URLs have failed. The test has failed for the following URL: %1 with result %2ZCertificate validation for the Defender for Endpoint cloud service completed successfully.&Certificate revocation was not tested.JCloud connectivity may be impaired due to certificate revocation failures.Please ensure the following URLs are not blocked: %1 and %2. For more information please refer to %3. For detailed error information, review %4.YTest connection to the Microsoft Defender Antivirus cloud service completed successfully.LTest connection to the Microsoft Defender Antivirus cloud service failed: %12If Microsoft Defender Antivirus is your primary antivirus solution or you have opted to enable EDR Block Mode, please ensure connections to AV cloud URLs are not blocked. For more information refer to: https://learn.microsoft.com/defender-endpoint/configure-network-connections-microsoft-defender-antivirus*Current network connection is not metered.)Current network connection is metered. %1Metered Networks can limit functionality in Defender MAPS communication, for example emergency signature requests are not sent (needed for custom indicators in addition to emergency signatures).ApproachingDataLimit: %1PAOverDataLimit: %1 Roaming: %1NetworkCostType: %1PAIf you intend to enable MDE Security Configuration Management then please refer to following documentation for the list of requirements.Supported PlatformseDevice does not have the minimum patch level for MDE Security Configuration Management onboarding: %1Device has Active Directory Name Services role installed. Support for Domain Controllers is currently in preview and requires additional configuration.If you intend to enable MDE Security Configuration Management for Domain Controllers, then please refer to following documentation.9Use of security settings management on domain controllers}The device is running a 32-bit operating system, which is not supported for MDE Security Configuration Management onboarding.SPlease note the device OS build is not supported by MDE and cannot be onboarded: %1FPlease refer to this article for a list of supported Windows versions.F%1 on this device is not running at Protection Level that is expected.For more information about PPL protection and why it is critical refer to this documentation. Contact Microsoft support if issue persists.PPLxPlease note the Hyper-V only server edition installed on this device is not supported by MDE and cannot be onboarded: %1XPlease refer to the MDE Supported documentation for a list of supported server editions.Supported Windows VersionsMDE Sense ServiceMDE AV Windefend ServiceWindows Security WscSvc ServiceWindows SecurityHealth Service'MDE Network Protection WdnisSvc ServiceMDE Defender Core Service+For more information, refer to the article.Please note that this machine is running with an outdated version of Defender Platform. Platform versions older than N-2 will no longer be supported.'Microsoft Defender AntiMalware Platform>Please note that this machine is running with an outdated version of Defender Antivirus 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.#Microsoft Defender Antivirus 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 UtilizationJMDE Platform experienced High Memory Utilization with current MDE versionsHigh Memory UtilizationMDE 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 initialize successfully and stuck at stage %1eRestart the machine and update to latest defender platform and if issue persists report to Microsoft.OMDE Windefend Service has failed to shutdown 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.PA0Unable 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 Microsoft Defender Antivirus 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 Microsoft Defender Antivirus.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 recognized 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 behavior 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.KThis 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 Organization ID: %1.@You should offboard the device from this organization, and then onboard it to your current organization. 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 user name in the top right corner.Security CenterwPlease 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 synchronized with your domain time. For more information on how to configure and control time synchronization 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.PAThe device was successfully onboarded to Microsoft Defender for Endpoint. However, Microsoft Endpoint Manager has not been configured through the Admin Center 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 AD. This could be due to the SCP being configured to join Enterprise DRS. Make sure the SCP record points to AAD 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 profilesPAAAD 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 ManagerEnrollment 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.PAControlled 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-Analyzed %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: %1PApASR %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.PA%What is Defender Diagnostic Insights?Defender Diagnostic Insights is a self-help diagnostics tool that collects and analyzes 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-optimized 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. t4VS_VERSION_INFOee?StringFileInfo040904B0LCompanyNameMicrosoft Corporation2FileDescriptionMicrosoft Defender for Endpoint Diagnostic EngineBInternalNamedefenderdiag.dll.LegalCopyright Microsoft Corporation. All rights reserved.ROriginalFilenamedefenderdiag.dll.muij%ProductNameMicrosoft Windows Operating System8FileVersion4.18.26040.7 (8d846dd50fd7adca65beb1b013a5fda76a9ec807)> ProductVersion4.18.26040.7l&PrivateBuildGitEnlistment(ContainerAdministrator)DVarFileInfo$Translation PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPAD%0%w *H %h0%d10  `He0\ +7N0L0 +70 010  `He dfZĸ0VLt0Mչ)u 003ݪD0  *H  01 0 UUS10U Washington10URedmond10U Microsoft Corporation1.0,U%Microsoft Windows Production PCA 20110 250619181144Z 260617181144Z0p1 0 UUS10U Washington10URedmond10U Microsoft Corporation10UMicrosoft Windows0"0  *H 0  ʻt9)C@۸H^'bD]0 d{QlRK$BR/N Yjv-E(tN:L|%P0<:0810U Microsoft Corporation10U 229879+5053260U#0)9ėx͐O|US0WUP0N0LJHFhttp://www.microsoft.com/pkiops/crl/MicWinProPCA2011_2011-10-19.crl%200a+U0S0Q+0Ehttp://www.microsoft.com/pkiops/certs/MicWinProPCA2011_2011-10-19.crt0 U00  *H  hzxiXdzq L]IYXqPI gV~q_R5ٳ); # o.J@$3o8NnMebʍ @BVFLt1M34Epb*q ]Fe]}nsbH, zȭ+i+Q"Vt}?¥rl^N M&scn`ԓl9BUKs?~szw+a00 avV0  *H  01 0 UUS10U Washington10URedmond10U Microsoft Corporation1200U)Microsoft Root Certificate Authority 20100 111019184142Z 261019185142Z01 0 UUS10U Washington10URedmond10U Microsoft Corporation1.0,U%Microsoft Windows Production PCA 20110"0  *H 0  . i!i33T ҋ8-|byJ?5 pk6u1ݍp7tF([`#,GgQ'rɹ;S5|'# oFnhttp://www.microsoft.com/pki/certs/MicRooCerAut_2010-06-23.crt0  *H  |qQyn9>\` QfG=*hwLb{Ǻz4KbzJ7-W|=ܸZij:ni!7ށugӓW^)9-Es[zFX^gl5?$5 uVx,Јߺ~,c#!xlX6+̤-@EΊ\k>p* j_Gc 26*pZBYqKW~!<ŹE ŕ]b֠c uw}=EWo3wbY~10 001 0 UUS10U Washington10URedmond10U Microsoft Corporation1.0,U%Microsoft Windows Production PCA 20113ݪD0  `He0 *H  1  +70 +7 10  +70/ *H  1" owpEA^ \cඟnXS-0B +7 1402Microsofthttp://www.microsoft.com0  *H sX^64뒛u{]V Jn,uÏB8xZp& TVp1$'pM,j G#uPrȌA곇$^̓Zl2?ӷ Ѹ`GrB[&Xנ !f_Tevf.$?}ty; Tb.#֚x +@6=8Қڗz@"?gs&BKϏr+kP30 +710| *H m0i10  `He0R *H  A=09 +Y 010  `He a1mRou-r^T|Qg>ei u20260425005035.702Z0Ѥ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  "o0"20260424171007Z20260425171007Z0t0: +Y 1,0*0 "o000 s06 +Y 1(0&0  +Y  0 00  *H  ?˭ xg'P~3玮4wU㪢쀃#$ŜHXy]iWDYsRu!gZqIK bMܗO(I6~%P;R{Q?N|kes6! cy绎3+e Wl #FT v~rVܡ^zRXctKDxA>+1TiT Iu-eP$=v{C2 1 m7+2P|1 0 00|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20103"Aȵ"0  `HeJ0 *H  1  *H  0/ *H  1" KA6J]]qkG@ i0 *H  /1000 `] Ƃ3l`Ι  00~0|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20103"Aȵ"0" ]k +Uv韫&\nYa0  *H  GQ<4)Cs~sp?O3#5I@HnK$j.FBe0ļ\j S`%[yVy BB(բCIn5V&٘X ]4ϹY~fmˑ"/o2Ӥs` ^_ _P9v煵Pꎸri'=_;,HaB]i%58xU_?gy2ު~=ESHb*ř)X/y~%T[1ΐ由Z.z'8VП2Ԝby]n]jtCQ]PCD&W)rH2-&+Bg #{'_Tv[HD/{ <^t@fG,s KXtk3+uP}ZQDxrrB'tr!݆"?XŒAhIJ!GwZhJҔD5Xr[Eg"!Zx

Windows NT KPTV 6.2 build 9200 (Windows Server 2012 Datacenter Edition) i586