Failed init during install

[user13377]

VPN Standard install file cannot find the policy.def file online, and so it aborts.
This is a one day old fresh install of Win 10. I did try disabling firewall etc. I am directly connected to the internet, no wifi.

[bjm]

@user13377

VPN Standard install file cannot find the policy.def file online, and so it aborts.
This is a one day old fresh install of Win 10. I did try disabling firewall etc. I am directly connected to the internet, no wifi.

Hello @user13377
OEM reset?
Microsoft Defender Antivirus?
You posted with Norton Family | Parental Control board?

fwiw ~ as per AI

A VPN helps with privacy and securing connections (especially on public Wi-Fi), but it doesn’t replace antivirus protection. Windows 10 already includes Microsoft Defender Antivirus for that, which should remain active alongside Norton VPN.

The “policy.def cannot be found online” error during install of Norton VPN usually means the installer can’t reach Norton’s servers to download required components.

If this is a true clean Windows install, then leftover software is unlikely and the issue is more likely related to connectivity, DNS, or certificate trust.

However, if this was an OEM reset, those can sometimes reinstall trialware (including security/VPN components), so prior software or drivers could still be present.

I’d suggest checking:
• System date/time is correct
• Run Windows Update fully (updates root certificates)
• Try DNS like 1.1.1.1 or 8.8.8.8
• Test on another network (e.g., mobile hotspot)

That error is usually not about your firewall—it’s Norton’s installer failing to download a required component (the policy definition file) from its servers. On a fresh Windows install, a few common things can trigger it.

Here’s how to work through it in a practical way:

---

What’s actually happening

During install, Norton Secure VPN reaches out to Norton servers to pull policy.def. If anything interferes (network filtering, TLS issues, DNS, or system clock), the installer just aborts.

---

Most likely causes (on a fresh Win10 build)

1. Incorrect system date/time (very common)

If your clock is off—even by a bit—secure connections can fail.

• Right-click clock → Adjust date/time
• Turn on Set time automatically
• Click Sync now

---

2. Missing Windows updates / root certificates

A fresh Windows 10 install often lacks updated certificate chains.

• Run Windows Update fully (repeat until nothing left)
• Reboot after updates

---

3. DNS or ISP filtering issue

Sometimes the installer can’t resolve Norton endpoints properly.

Try switching DNS temporarily:

• 8.8.8.8 / 8.8.4.4 (Google)
• 1.1.1.1 (Cloudflare)

---

4. Corrupt or incomplete installer

Don’t rely on a cached or older file.

• Re-download from your Norton account
• Or better: use the stub installer (small downloader) instead of an offline package

---

5. TLS / crypto settings not initialized

On clean systems, TLS 1.2+ might not be fully enabled via legacy settings.

Quick check:

• Internet Options → Advanced tab
• Ensure Use TLS 1.2 (and 1.3 if present) is checked

---

6. Security software remnants (less likely here)

Even on “fresh” installs, OEM images or prior attempts can leave drivers.

Best cleanup approach:

• Use Norton Remove and Reinstall Tool
• Reboot
• Then reinstall VPN

---

Quick “fast path” fix (try this first)

1. Sync system time
2. Run all Windows Updates
3. Reboot
4. Switch DNS to 1.1.1.1
5. Download fresh installer
6. Run installer as Administrator

---

This specific policy.def failure has historically been tied to:

• Norton backend/CDN hiccups (temporary)
• Geo/DNS routing issues
• Or outdated Windows trust store

So if this just started “today,” it may resolve on its own within hours.

Older hardware (especially systems that don’t meet Windows 11 requirements) can introduce a few “gotchas” that line up with what you’re seeing:

---

Where older systems can be iffy

1. Outdated firmware / BIOS

• Can affect network stack behavior or TLS handling
• Not super common, but it does happen

2. Network drivers

• Old or generic drivers can cause:
  • Odd connectivity issues
  • Problems reaching specific CDNs/endpoints
• Worth updating from the OEM site if possible

---

3. Certificate / crypto support gaps

On a fresh Windows 10 install:

• Root certificates may be outdated until Windows Update runs
• TLS 1.2 needs to be fully functional

This one lines up very closely with the policy.def failure

---

4. OEM preload leftovers (if not truly clean)

As you mentioned earlier:

• Trialware (security/VPN tools)
• Network filter drivers

These can interfere—even if the system feels “fresh”

5. Hardware instability (edge case)

• Failing NICs or flaky connections
• Usually shows broader symptoms though, not just one installer failing

If your “fresh install” was an OEM reset (using the “Reset this PC” feature or a manufacturer recovery partition), it often carries over leftover configurations, drivers, or “bloatware” that a true clean install from a USB would not.

This is likely why you are seeing the policy.def error. In an OEM reset, Windows often pulls from a “recovery image” stored on a hidden partition. If that image is outdated or contains a pre-installed (and now expired or broken) version of Norton, it can conflict with the new installer you’re trying to run.

Why an OEM Reset is causing this:

• Outdated Root Certificates: OEM images are often months or years old. Even if you “reset” today, the underlying system may lack the modern security certificates needed to verify Norton’s policy.def file online.
• Pre-installed Trials: Many OEMs (Dell, HP, Lenovo) include a trial of Norton or McAfee. Fragments of these pre-installed versions can block fresh installations from completing.
• Corrupted Recovery Image: If the local recovery partition itself has a minor corruption, every “reset” you perform will replicate that same error.

Action Plan for an OEM Reset system:

1. Purge Pre-installed Bloatware: Go to Settings > Apps and check if a different version of Norton (like “Norton Security” or “Norton 360”) or a different antivirus was pre-installed by the manufacturer. Uninstall it immediately.
2. Force a “Cloud Download” Reset (If you want to reset again): If you decide to reset the PC again, choose Cloud Download instead of “Local Reinstall”. This pulls fresh Windows files from Microsoft rather than using the manufacturer’s potentially buggy local image.
3. Sync System Clock: Ensure your date and time are set to Sync now in Windows settings. If the clock is even slightly off, the SSL handshake to download the policy file will fail.

Did your computer come with a pre-installed antivirus trial like McAfee or a different Norton product that you noticed after the reset?

AI sourced content may make mistakes

[bjm]

3 May
I followed every suggestion from the AI.
The log file indicates there is actually file on the server. Here following is Claude.ai response to the error log file. I tried
accessing branding dot norton dot com and got a ‘not found’ response which means i got through.
Looking at your log, the installer failed trying to download a branding/policy file:

https://branding.norton.com/PROD/26.4/16/1364/21371777/policy.def

It got HTTP 404 (Not Found) every time — meaning the server responded, but that specific file doesn’t exist at that path. This strongly suggests the issue is not your internet connection or a firewall block, but rather a bad/mismatched URL in the installer itself.

To confirm your connection to Norton’s servers is fine, try opening this in your browser:

branding.norton.com

If that loads (even a blank page or a redirect), your internet is reaching Norton’s servers just fine. The 404 is Norton’s problem — that specific file path doesn’t exist on their end.

Hello @user13377
May be best – for you – to document/report this issue directly via Norton support.
Norton support will likely request remote session – to see – as you see.

Note: for an official Norton support response – open a support case:
Norton Support Help Center → Contact us (bottom of page)
Contact Norton Support → Let’s get started.

[user13377]

Contacted support. They got it to install just fine.

[bjm]

@user13377

Contacted support. They got it to install just fine.

Hello @user13377
Thanks for sharing your progress.
Can you share what support did…?

[bjm]

Hello @user13377
Thanks for sharing your progress.
Can you share what support did…?

[user13377]

Support took over my computer remotely with my permission and installed from another app source that actually worked, so I never did get an explanation of why that had to happen. Was fun to watch. I have used several other vpn’s flawlessly but this one was so troublesome to get working.
I wanted to make sure everything was fine before I said anything.

[bjm]

@user13377

Support took over my computer remotely with my permission and installed from another app source that actually worked, so I never did get an explanation of why that had to happen. Was fun to watch. I have used several other vpn’s flawlessly but this one was so troublesome to get working.
I wanted to make sure everything was fine before I said anything.

Hello @user13377
Thanks for sharing.