N360 Online Management

[ITMA]

I don’t log onto the N360 UI - Remote Online Management very often. The product is functioning; so, why bother.
I logged on today and this is what I found:-

My 3rd device (W10 ESU) flags up, as above. N360 is fully functional and I cycle my devices; so, they all get used, very often. The ‘INACTIVE‘ & ‘NOT PROTECTED‘ flags were the initial query.
I reloaded N360 twice, using a couple of different methods.
N360 is still fully functional; alas, it picked up the ‘NEW DEVICE‘ flag, as well as retaining the ‘INACTIVE‘ & ‘NOT PROTECTED‘ flags.

If anyone can shed a little light on this anomaly, I’d be grateful.

[bjm]

@ITMA

My 3rd device (W10 ESU) flags up, as above. N360 is fully functional and I cycle my devices; so, they all get used, very often. The ‘INACTIVE‘ & ‘NOT PROTECTED‘ flags were the initial query.
I reloaded N360 twice, using a couple of different methods.
N360 is still fully functional; alas, it picked up the ‘NEW DEVICE‘ flag, as well as retaining the ‘INACTIVE‘ & ‘NOT PROTECTED‘ flags.
If anyone can shed a little light on this anomaly, I’d be grateful.

Hello @ITMA

This specific glitch happens because Norton’s portal relies on hardware identification hashes. When you reloaded Norton 360 using different methods, the portal treated those modifications as entirely separate machines, creating a duplicate placeholder.

Because the portal is still tracking your old installation profile (which is no longer sending data), that original entry is permanently flagged as ‘INACTIVE’ and ‘NOT PROTECTED’. Meanwhile, your live, functional app is mapped to the ‘NEW DEVICE’ entry.

Since your local desktop application displays a green, secure status, your Windows 10 ESU system is completely safe. You can easily purge the stale data and fix the dashboard by manually deleting the ghost entries.
Step 1: Purge the Ghost Entries from Your Dashboard

1. Sign in directly to your online Norton Account Portal
2. Hover over My Account in the top-right corner and click on My Subscriptions.
3. Find your current active Norton 360 plan and click Manage Devices.
4. Look through the list for the specific entries marked ‘INACTIVE’ or ‘NOT PROTECTED’ matching your W10 ESU machine.
5. Click the Bin/Trash icon next to those dead entries and confirm by clicking Remove. This frees up your license slots and removes the false error flags.

Step 2: Rename and Sync the Correct Profile

1. While still in the portal, look at the remaining entry for your Windows 10 machine (the one marked ‘NEW DEVICE’).
2. Use the Edit Name (pencil icon) feature to give it a distinct name (e.g., “W10-ESU-Main”), so you can distinguish it from future ghosts.
3. Go back to your physical Windows 10 computer, open the local Norton 360 UI and Resync.

v26 Account Resync

1. Open your Norton 360 desktop application.
2. Look at the top dashboard panel and click on your Profile/Account Icon.
3. If an account overview pane click Sign Out.
4. Close the application fully, then reopen it.
5. Click Sign In and re-enter your account credentials.

When you install Norton, it looks at specific physical parts of your computer to create a unique ID. It uses a combination of parts that generally do not change, including:

• Your motherboard serial number
• Your CPU ID
• The MAC address of your network card
• Your hard drive’s unique serial number

Why the Duplicate Entries Happened

The Norton server uses this hardware hash to recognize your machine. However, certain actions cause the server to think a brand-new computer is trying to connect:

• Registry/Installation Path Changes: Re-installing Norton using two different methods (like a standard uninstaller vs. a deep-clean removal tool) alters the registry keys and setup paths.
• Virtual Network Adapters: If your Windows 10 ESU system uses certain VPNs, virtual switches, or MAC address randomization, the network portion of the hash changes.

When the Norton server receives data with a slightly altered hash, it does not overwrite your old profile. Instead, it plays it safe, protects your machine under a “New Device” entry, and leaves the old profile behind to rot as “Inactive.”

AI sourced content may make mistakes

[ITMA]

Originally,
1. I used the Norton RnR Tool, with no success. Then:- on to 2
2. I deleted the offending device and deleted everything I could find in c:\ & the directory, with a view to a forensic clean.
3. I reinstalled N360 as a new user; expecting to add my email id , to tag the software to my existing account: it didn’t happen. The forensic clean, failed along the way ?

So, to the bjm reply
I never did have ‘dead licences’ and subsequently a ‘new device’; all I’ve ever seen is the image I posted, originally with two flags and then with all three. I’ve removed the device twice; but, it comes back the same. I’ve run the bjm instructions verbatim, to no effect.

I’d be interested, where we go next . . .

[bjm]

@ITMA

Originally,
1. I used the Norton RnR Tool, with no success. Then:- on to 2
2. I deleted the offending device and deleted everything I could find in c:\ & the directory, with a view to a forensic clean.
3. I reinstalled N360 as a new user; expecting to add my email id , to tag the software to my existing account: it didn’t happen. The forensic clean, failed along the way ?

So, to the bjm reply
I never did have ‘dead licences’ and subsequently a ‘new device’; all I’ve ever seen is the image I posted, originally with two flags and then with all three. I’ve removed the device twice; but, it comes back the same. I’ve run the bjm instructions verbatim, to no effect.
I’d be interested, where we go next . . .

Hello @ITMA
Thanks for sharing your progress.
Since, your Remote Management is enabled & your forensic scour cleaned all file/reg dross.

When your Norton account reports a hardware profile labeled as “NEW DEVICE” with an “INACTIVE” status, it means a license placeholder has been generated for a fresh installation, but the software has not yet linked or fully activated on that specific hardware.

This specific combination usually occurs during setup or account maintenance.

Why This Happens

• Pending Installation: You used the “Download or Share” feature to send an installation link via email or SMS to a new device, but the setup process has not been completed on that machine.
• Server Sync Delay: You recently completed the installation on a new device, but the local software has not yet finished its initial synchronization with the Norton portal.
• Missing Account Sign-In: The Norton software is physically installed on the machine, but you have not yet logged into your Norton account within the app itself to link the license.
• Accidental Seat Transfer: A license slot was freed or reassigned, creating a blank placeholder entry waiting to be claimed by hardware.

How to Fix It

1. Complete the Setup: Open the Norton application on the new physical device and complete any pending setup prompts.
2. Sign In Globally: Click Sign In or Activate Now inside the device’s Norton app interface and enter your primary account credentials.
3. Trigger a Refresh: Ensure the target device has an active internet connection, leave the Norton application open for a few minutes, and then refresh your browser page on the My Devices portal.
4. Purge Ghost Entries: If you do not recognize the entry or did not attempt to add a device, click the Trash/Bin icon next to the inactive placeholder to permanently remove it and protect your available plan slots.

+++++++++++++++++++++++++++++++++++++++++++++++++++

May be best – to document/report “issue” directly via Norton support.
Note: for an official Norton response – open a support case:
Norton Support Help Center → Contact us (bottom of page)
Contact Norton Support → Let’s get started | Welcome (signed in)

AI sourced content may make mistakes

[ITMA]

. . . not making any headway at all, with the problem.
Alas, I’m out of time on the issue. But, since the product works; I’ll drive this along from the other end, the Norton end.
When the product alarms and informs me I’m UNPROTECTED, I’ll address the issue again.