Following some issues with Microsoft software it became the last stop solution to "RESET" W10
We all know what that leads to re-installing software etc. - That is where my Norton 360 problem begins.
After re-installing I found that the VPN was not activating on my request.
Most of the time the message box came up at bottom right to report an error connecting -try later - except later was always later.
Sometimes after repeated attempts I wouldn't get any message - the VPN was clearly not connecting.
Important to note there were no instances of error codes to reference.
I tried all the avenues suggested for my problem as it presented itself including re-installing the software - several times in fact - making special note to install all data. When I inspected the programmes folder I was disappointed to see a Norton folder so mixed in with my several attempts I also uninstalled the Norton utility. - Yes the folder disappeared but it made no difference. Even opened up a chat line
(Case: xxxxxxxx) - Parvez tried his best -basically guiding me through the process I had already exhausted.
I was very close to capitulating and going to a clean install of W10 as perhaps the only way forward.
I should also add at this point that I had a second PC sharing the licence and connected to the same ISP - that was working fine - an insurance that it was not the connection - as the help pages quite rightly suggested that as a possible source of the fault.
In desperation I started looking further and picked up on the reported errors with error codes referenced.
I think it is second on the list - Error 9012,87 "an error is preventing...…..(ref errorID87)
I followed the instruction to uninstall the miniport drivers as per the instruction. Important to note there was NOT a Symantec TAP
Clicked on the action tab and selected scan for changes.
The drivers reappeared and appeared to be running - without further intervention - a departure from the Norton guided procedure.
Checked the VPN Start up - SUCCESS!! - Restarted the computer again to double check - okay so far
I see many people have posed questions around this topic over a period of time. I think confusion arises because the problem seems to present itself in different ways - possibly with different PC's or processors. For instance whilst I resolved my problem it was through a procedure that reportedly had error coding - I never saw error codes on my screen.
With that very much in mind I thought it would be good form to share my success.
Hopefully someone will find this helpful - including Norton/Symantec because I think the help pages seem to have a few holes in them.
[Edit: Masked case ID to conform with the Participation Guidelines and Terms of Service]