My previous tirade was a little strong, but the .69 ‘Release Notes’ says that they will monitor comments and had to roll back prior release because of “connection failure errors”, which are being discussed in another thread! ‘The good, the bad, the ugly’ choose your poison! https://community.norton.com/en/blogs/product-update-announcements/norton-security-2220169-windows-now-available Note that it appears that the design needed fixing.
“John boy bitch” stated the customer problem very clearly, please reread why ppl bought ‘360 with VPN’ and why the customers are so furious. But in Norton’s defense there is NO EASY/SIMPLE FIX that would satisfy everyone and is probably being worked. But it would be nice if Norton acknowledged that more directly and provided a partial, more secure fix. See Sportfan100 statement of issue.
I strongly concur with ‘darth_vida’s suggestion that “AUTO start at boot” should be an option/setting (probably in firewall settings). Defaulted OFF, as turning it ON might get ‘connectivity errors’ from other auto start apps. Customer’s choice. Note VPN is not good for streaming video -OFF
. Also any fix must retain the ‘My Norton’ panel to also offer the VPN options, especially ON/OFF, as VPN may not work for all sites that need to be connected with after startup. (I even had to turn VPN OFF to start this COMMUNITY site}.
The Norton VPN encrypts, hides finance/personal info that LifeLock is interested in but not necessarily your IP address that sniffers are also interested in. The other important feature of a VPN!. During boot up lasting several minutes, your IP address might be exposed before a VPN is connected through the Firewall. I usually run ‘update’ and ‘quick scan’ manually upon powering up PC, so I also then start the VPN to have encryption protection for apps I start. Not only was my IP address exposed during W10 boot, but my IP address was exposed before the VPN connected several seconds after panel appeared.and I made my entry
My gut feel from reading various posts and threads that the ‘MY NORTON’ panel was just part of the VPN development and the developed process for ‘auto start at boot’ was not released (patched out) because some startup/bootup processes could not be connected through an already started VPN. See https://community.norton.com/en/forums/vpn-not-working-update-2220169-connection-failure-error
The question is; When in the ‘boot up’ process the VPN can/should be started.
This is a complicated question! The W10 boot involves many asynchronous process steps to add capabilities for the next more complex operations/services and some of these services connect to a site for updates before a VPN is established. Exposing your IP address. See ‘Task Manager’ and ‘History’ for examples. VPN can’t be started immediately after BIOS boot. Not enough services. One person proposed that the ‘START’ process be used, but that is very late in the boot starting processes. Some apps ‘starting’ up may try to connect before the VPN is established through the FIREWALL causing ‘connection failure errors’. The firewall may have to delay these connections?
PS I am confident that Norton has substantial knowledge about W10 boot/start up processes and update controls as shown in this related thread: https://community.norton.com/en/forums/task-scheduler-how-set-live-update-startup
As another frustrated ~!@#$%^ customer of many years I wish Norton would more directly address/acknowledge they are working for an earlier auto VPN start up option in future release. Even a partial fix/update to prevent less IP exposure as this may take some major effort to fully securely implement.