Norton error YOU ARE UNPROTECTED, please click here to repair

[bjm]

@Robert_M2

Norton error YOU ARE UNPROTECTED, please click here to repair
When I click this is what I get:
Norton 360
22.25.3.5
BucketID: 0CA3E5F2
Windows 10 Pro
19041.1.amd64fre.vb_release.191206-1406
Norton Autofix Results: 0 item(s)
[…]

Hello @Robert_M2

When the warning appears, what does the main Norton window show as requiring repair? The Autofix report only shows that Norton detected a problem and generated BucketID 0CA3E5F2, but it does not identify which protection component is causing the “You Are Unprotected” warning.

Is Norton 360 version 22.25.3.5 your current installed version, and if so, are you intentionally remaining on v22?

Are you intentionally using an old offline installer?

Intelligent Updater has been deprecated for legacy Norton products

======

1. What does winver show?
2. Why is the system still on v22.25.3.5?
3. What specific component is Norton claiming is “unprotected”?

1. What does winver show?

This tells us whether:

• The machine is genuinely on an ancient Windows 10 release, or
• Autofix is simply reporting a base build string that looks old.

Without winver, we’re guessing.

2. Why is the system still on v22.25.3.5?

This may turn out to be nothing, but it could reveal:

• Intentional choice (“I refuse v24/v26”)
• Upgrade failures
• Unsupported configuration
• Long-standing update problems

Any of those would be useful context.

3. What specific component is Norton claiming is “unprotected”?

This is probably the most important question.
Because “You Are Unprotected” is a status message, not a diagnosis.
There’s a huge difference between:

• Auto-Protect disabled
• Firewall disabled
• Security service stopped
• Licensing issue
• LiveUpdate issue
• Product activation issue

Right now we don’t know which bucket we’re in.

======

The most unusual part of your report is the repeatability. A reinstall temporarily resolves the issue, but after several days Norton begins reporting protection errors again and eventually LiveUpdate stops functioning. Since this has reportedly occurred multiple times over several years, it does not sound like a simple one-time installation problem.

A few questions:

1. Is your Norton subscription currently active?
2. Are you intentionally remaining on Norton 360 version 22.25.3.5, or has the product never upgraded to the current v26 release?
3. What Windows version does winver report today?
4. Do you have any other security, firewall, VPN, cleanup, or system-hardening software installed?
5. When the “You are Unprotected” message appears, which protection feature is shown as needing repair?

The answers may help determine whether this is a product upgrade issue, a Windows issue, or a problem affecting Norton services after installation.

======

I’m interested why a machine in 2026 is still reporting v22 and a 19041 build.
That may be the biggest clue in the entire post.

19041 is the base build for Windows 10 Version 2004, released in 2020. If a system were fully patched and current on Windows 10 today, you’d expect to see something more like:

• Version 22H2
• Build 19045.xxxxx
  *Microsoft kept the same underlying code branch, but:
• 2004 = 19041
• 20H2 = 19042
• 21H1 = 19043
• 21H2 = 19044
• 22H2 = 19045

Please run winver and report what it shows.
For example:

• Version 22H2 (OS Build 19045.6093) → reasonably current Windows 10.
• Version 2004 (OS Build 19041.x) → seriously out of date and potentially a contributing factor to Norton issues.

The combination of:

• Norton 22.25.3.5
• Windows build string showing 19041
• Repeated LiveUpdate failures

would definitely make me wonder whether the machine has been stuck on an old software/update path for quite a while. That may not be the root cause, but it’s significant enough that I’d want clarification before chasing Norton-specific explanations.

======

• Norton’s primary engineering focus today is v26.
• Legacy components and legacy documentation may receive less attention than current-platform resources.
• A v22 user encountering a BucketID with “Autofix Results: 0 item(s)” does not inspire confidence that there is an actively curated repair workflow behind every legacy fault.

What we don’t know is whether:

• Autofix’s backend database is frozen for v22,
• partially maintained,
• or still maintained but simply has no fix for that particular BucketID.

The fact that Autofix reports a BucketID but returns “0 item(s)” suggests the fault was detected but no automated repair was available. Whether that is because the issue is unknown, unsupported, or no longer covered by Autofix’s repair catalog is difficult to determine from the information provided.

======

Let’s line up the facts as presented:

• User is on v22.25.3.5.
• User claims multiple uninstall/reinstall cycles.
• After reinstall, LiveUpdate works.
• System is fine for 3–5 days.
• Then “You Are Unprotected” warnings begin.
• Autofix returns BucketID and 0 item(s).
• Eventually LiveUpdate stops working.
• This has happened 3–4 times like clockwork.

Now add:

• Norton has spent years migrating users off v22.
• Intelligent Updater for legacy products has now been deprecated.
• A normally functioning v22 installation should eventually encounter the modern Norton update ecosystem.

Either:

The user is omitting a major detail

Examples:

• Intentionally reinstalling from an old v22 installer.
• Blocking upgrades.
• Running an unsupported Windows build.
• Using a firewall/proxy/VPN that interferes with Norton.
• Previously worked with Support.

or

The machine is failing some communication path

Not necessarily licensing, but some “call home” function:

• Product entitlement validation.
• Product update eligibility.
• LiveUpdate communications.
• Account synchronization.
• Backend service communications.

I think we’re missing at least one very important fact. The v22 version, the 3–5 day delay, and the eventual LiveUpdate failure don’t quite fit together into a coherent story yet. Something has not been communicated.

What we know

The user says:

• Norton 360 v22.25.3.5
• Windows 10
• Reinstalled Norton 3 times
• LiveUpdate works initially
• After 3–5 days, “You Are Unprotected” warnings begin
• Autofix shows BucketID 0CA3E5F2 and 0 items
• Eventually LiveUpdate stops working
• This cycle repeats

What we do NOT know

• Actual winver result
• Whether v22 is intentional
• What component is unprotected
• Whether the machine ever attempted migration to v24/v26
• Whether Support has been involved
• Whether other system problems exist

AI sourced content may make mistakes