{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/",
        "slug": "scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available",
        "url": "https://update.dsesecurity.com/updates/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/"
        },
        "title": "Scope w32tm /resync command fails with \"The computer didn't resync because no time data was available.\" in observed AD/DNS state",
        "summary": "Use w32tm /resync command fails with \"The computer didn't resync because no time data was available.\" to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "briefing",
            "name": "Briefing"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "microsoft-365-identity",
                "name": "Microsoft 365 & Identity",
                "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T17:00:50+00:00",
        "modified_at": "2026-08-27T17:33:25+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 601,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of w32tm /resync command fails with \"The computer didn't resync because no time data was available.\"",
        "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.",
        "primary_source": {
            "name": "w32tm /resync command fails with \"The computer didn't resync because no time data was available.\"",
            "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/error-message-run-w32tm-resync-no-time-data-available",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>Use this document to resolve one bounded operational decision: Scope w32tm /resync command fails with &#8220;The computer didn&#8217;t resync because no time data was available.&#8221; in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/error-message-run-w32tm-resync-no-time-data-available\" target=\"_blank\" rel=\"noopener noreferrer\">w32tm /resync command fails with &#8220;The computer didn&#8217;t resync because no time data was available.&#8221;</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Introduction below H1, Microsoft states: “This article provides several possible solutions to an error that you may get when you run the w32tm /resync command to synchronize time with a time source.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n<li>At Introduction below H1, Microsoft states: “_Applies to:_ Windows Server (All supported versions) _Original KB number:_ 929276.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n</ul>\n<p>Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.</p>\n<h2>What the source does not establish</h2>\n<p>The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. It does not establish a deployment&#8217;s current state, authorize a production change, prove compliance, or show that Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials are healthy. Documented options are review inputs, not universal mandates.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?</li>\n<li>What baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?</li>\n<li>Which success, stop, and escalation criteria are written before testing begins?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.</p>\n<p>For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.</p>\n<h2>Verification and evidence</h2>\n<p>Keep the source locations <strong>Introduction below H1</strong>; <strong>Introduction below H1</strong> adjacent to the sanitized artifacts used for comparison. Prefer sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, with enough identity and timing data for an independent recheck.</p>\n<p>Label this evidence set <strong>DSE-20260827-396</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/error-message-run-w32tm-resync-no-time-data-available\" target=\"_blank\" rel=\"noopener noreferrer\">w32tm /resync command fails with &#8220;The computer didn&#8217;t resync because no time data was available.&#8221;</a> — Microsoft</li>\n</ul>",
        "content_text": "Use this document to resolve one bounded operational decision: Scope w32tm /resync command fails with “The computer didn’t resync because no time data was available.” in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official w32tm /resync command fails with “The computer didn’t resync because no time data was available.” from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article provides several possible solutions to an error that you may get when you run the w32tm /resync command to synchronize time with a time source.” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “_Applies to:_ Windows Server (All supported versions) _Original KB number:_ 929276.” The research record locates this support at Introduction below H1.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials are healthy. Documented options are review inputs, not universal mandates.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?\nWhat baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nKeep the source locations Introduction below H1; Introduction below H1 adjacent to the sanitized artifacts used for comparison. Prefer sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, with enough identity and timing data for an independent recheck.\nLabel this evidence set DSE-20260827-396 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\nw32tm /resync command fails with “The computer didn’t resync because no time data was available.” — Microsoft",
        "content_markdown": "Use this document to resolve one bounded operational decision: Scope w32tm /resync command fails with “The computer didn’t resync because no time data was available.” in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [w32tm /resync command fails with “The computer didn’t resync because no time data was available.”](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/error-message-run-w32tm-resync-no-time-data-available) from Microsoft supports the following bounded statements:\n\n- At Introduction below H1, Microsoft states: “This article provides several possible solutions to an error that you may get when you run the w32tm /resync command to synchronize time with a time source.” The research record locates this support at Introduction below H1.\n\n- At Introduction below H1, Microsoft states: “_Applies to:_ Windows Server (All supported versions) _Original KB number:_ 929276.” The research record locates this support at Introduction below H1.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.\n\n## What the source does not establish\n\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials are healthy. Documented options are review inputs, not universal mandates.\n\n## Applicability questions\n\n- For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- Which owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?\n\n- What baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?\n\n- Which success, stop, and escalation criteria are written before testing begins?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\n\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\n\n## Verification and evidence\n\nKeep the source locations Introduction below H1; Introduction below H1 adjacent to the sanitized artifacts used for comparison. Prefer sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, with enough identity and timing data for an independent recheck.\n\nLabel this evidence set DSE-20260827-396 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\n\n## Official references\n\n- [w32tm /resync command fails with “The computer didn’t resync because no time data was available.”](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/error-message-run-w32tm-resync-no-time-data-available) — Microsoft"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/",
                "url": "https://update.dsesecurity.com/updates/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Scope w32tm /resync command fails with \"The computer didn't resync because no time data was available.\" in observed AD/DNS state",
                        "item": "https://update.dsesecurity.com/updates/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/#article",
                "identifier": "https://update.dsesecurity.com/updates/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/",
                "url": "https://update.dsesecurity.com/updates/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/",
                "headline": "Scope w32tm /resync command fails with \"The computer didn't resync because no time data was available.\" in observed AD/DNS state",
                "description": "Use w32tm /resync command fails with \"The computer didn't resync because no time data was available.\" to review this narrow operational decision…",
                "abstract": "Use w32tm /resync command fails with \"The computer didn't resync because no time data was available.\" to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to resolve one bounded operational decision: Scope w32tm /resync command fails with “The computer didn’t resync because no time data was available.” in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official w32tm /resync command fails with “The computer didn’t resync because no time data was available.” from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article provides several possible solutions to an error that you may get when you run the w32tm /resync command to synchronize time with a time source.” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “_Applies to:_ Windows Server (All supported versions) _Original KB number:_ 929276.” The research record locates this support at Introduction below H1.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials are healthy. Documented options are review inputs, not universal mandates.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nWhich owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?\nWhat baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nKeep the source locations Introduction below H1; Introduction below H1 adjacent to the sanitized artifacts used for comparison. Prefer sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, with enough identity and timing data for an independent recheck.\nLabel this evidence set DSE-20260827-396 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\nw32tm /resync command fails with “The computer didn’t resync because no time data was available.” — Microsoft",
                "datePublished": "2026-08-27T17:00:50+00:00",
                "dateModified": "2026-08-27T17:33:25+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/scope-w32tm-resync-command-fails-with-the-computer-didn-t-resync-because-no-time-data-was-available/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Scope w32tm /resync command fails with \"The computer didn't resync because no time data was available.\" in observed AD/DNS state"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Briefing",
                    "Advisory priority"
                ],
                "genre": "Briefing",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Microsoft 365 & Identity",
                        "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 601,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "w32tm /resync command fails with \"The computer didn't resync because no time data was available.\"",
                    "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/error-message-run-w32tm-resync-no-time-data-available"
                }
            }
        ]
    }
}