Nord VPN, Local Network, New Router

[Countcussy]

Until recently, I have been using Nord VPN without issue across my home network, most of which is wired.
This includes my main PC, a NAS with my Plex Server and backup drives, all the TV`s, PS5 etc, etc.

After a recent problem with my EE provided Smart Router, I purchased a TP-Link Archer 2100.

Since this time, having Nord VPN start with windows is killing my Local network. The Network folder is empty, and my Mapped drives on the Nas are unavailable as the network name is in use.
In this state, I have 2 network connections in the Notification area.
1. Nordlynx - Internet access.
2. Local area network - No internet access

If I restart windows, sometimes it fixes the problem, sometimes not. Rebooting the NAS can also sometimes fix the issue.
I do not have enough knowledge to know if this is because I swapped out the router, a nord VPN update, or a setting in the new router. (I presume the EE boxes are designed to be foolproof)

My current work around is to manually start Nord VPN once my PC has booted which works, but would really like to go back to having Nord start with windows.

Any ideas?

 

[Firegod]

If you go into the app, click the settings cog, then go into general, and scroll down and click run diagnostics. This will launch a support tool. Try doing "Reset App" and/or "Reset Network". Do either of those help? Also sometimes just a simple uninstall, reboot and reinstall fixes things.

 

[Countcussy]

Well, after lots of fannying about, turns out its nothing to do with NordVPN. It was a red herring. Same symptoms with no VPN installed.
The actual problem was cold boot vs restart, And I was not cold booting when testing my VPN theory. The actual restart was fixing the issue. Leading me up the garden path.

Managed to re-create the symptoms on every boot. With and without VPN.

Shutdown and restart, Internet but no local network access.
Restart only, Internet & local network.

I reset my whole network, checked for driver updates etc. etc.
Googling led me to a random suggestion of disabling "Fast-Start-up" in the power settings. Done that, and bizarrely, the problem has gone away.
No Idea why that would fix my issue, but it has. Hopefully, this will help someone else in the future.