What finally drove you to "accept" aka "GIVE IN" the on-line only vault in 2013.
I'm STILL running V6.4 (2012) on all my machines and remain steadfast.
Hi Irish_Red,
I use to be steadfast also concerning Local vs. Online Vault. Back when this first started to be a real issue, I helped probably over 2 dozen users roll back to the 2012 version, so as to regain their local vault.
I also stayed with NIS 2012 well past the release of the 2013 version, for the purpose of retaining the local vault.
After awhile, I decided I wanted to be as up to date as possible with NIS. Understand, I would still like to have the Local Vault option .. but I'm no longer rolling back anymore.
There's something to be said about being up to date.
Example: Right now there's a Chrome browser/Norton Toolbar conflict going on. If a person uses IE or Firefox, no problem. For those who prefer Chrome as their browser of choice, you need to be updated to the very latest Norton version .. 21.1.0.18 to receive the patch, as Tony Weiss explains in this announcement.
If a Chrome user and not up to date with Norton, a person will not receive it.
Myself, I feel safe and secure and keep an absolute minimum of info in the vault .. though I would welcome the return of the local vault option.
Ed
Ed,
As long as you started with NIS 2012 or earlier you can upgrade to the most recent version and still keep the local vault. Just because you upgrade the basic software, as long as he vault originally was local you can keep it that way. I'm presently running NIS 2014 but have kept my local vault. I also have a copy of NIS 2012 stashed away so I have to reformat everything or buy a new machine I can start with 2012 with a local vault. A local vault is something I will not give up, if Norton forces me to I will look elsewhere for my security software.
Just finished having to reinstall NIS 2012 (by necessity I might add...) on my two-year old Win 7 laptop, which up until today was running NIS 2013 without any ID Safe configuration whatsoever or any major problems for that matter. Probably would not have done so except for one very important reason: the decision to update to NIS 2014 this morning on this unit was a total disaster. Fortunately, I used the Norton removal tool to uninstall the entire hosed mess on the laptop and then grabbed my trusty thumb drive to get a copy of NIS 2012 from my desktop rig (which has been running NIS 2012 for a couple of years now and will continue to do so) that's kept for just such an emergency. Guess what else I had kept if the balloon went up like it did this morning? Yup! A backup of my data made on a regular basis from my local vault.
Forgot about NIS screwing up the laptop because I'm actually glad in a way this all occurred. It allowed me to set up the portable with a local vault and also has permanently cemented in my will the fact that Norton had better either get their collective act together regarding this issue or they'll lose a customer who has been onboard since 1997.
I will now do any further talking on this issue with my money and not my keyboard.
As long as you started with NIS 2012 or earlier you can upgrade to the most recent version and still keep the local vault. Just because you upgrade the basic software, as long as he vault originally was local you can keep it that way. I'm presently running NIS 2014 but have kept my local vault. I also have a copy of NIS 2012 stashed away so I have to reformat everything or buy a new machine I can start with 2012 with a local vault. A local vault is something I will not give up, if Norton forces me to I will look elsewhere for my security software.
Thanks Msradell,
I'm aware of that, but didn't mention it in my post. When I finally went to the 2013 version, that's what I did .. an upgrade to keep the local vault. At some point I needed to do a clean install and knew I would lose the vault.
After the clean install, I was going to roll back to 2012, regain my vault and upgrade again. By that time it was enough for me. I was tired of all the rolling back to regain a vault if something happened.
As more time goes by users eventually won't be able to roll back to 2012 for the local vault. At some point Norton will more than likely stop supporting it.
I'm satisfied where I'm at now. Thanks for your input.
I recently used NIS 2012 to install a Local Vault on my Windows 7 Laptop and then upgrade to NIS 2014. This will work OK on Windows 7 but NIS 2012 will not install on a Windows 8 or 8.1 system. I have asked if NIS 2012 will be updated to install and work on Windows 8 or 8.1 and have been ignored. Unless Norton gives us the Local option in new releases it will die on the vine. Since the Local Vault will work in NIS 2014 why can't Norton just give us a choice to setup the Local Vault. I have a feeling that NIS 2015 will dump the Local Vault completely.
after facing the problem you mentioned (I'm using Windows 8.1) and facing the fact no solution was available for me I decided to move to Kaspersky Pure 3.0, that worked pretty well.
It's a pitty this lack of responsiveness from the Product Management Team... I had been a happy Norton products user for over a decade, now I'm not one of them, anymore.
I really can not understand why corporations understand you should trust them all your confidential data, just because they would "take good care" of it. It really doesn't make sense for me, specially for a company whose servers may be hosted in the USA, where the Government can access anybody's data with no previous (or further) notice.
Well, I wish Symantec good luck with this kind of behaviour. While it does not change, I'm OUT.
I recently tried BitDefender 2014 with its new Local Vault but it didn't work very well so removed it. Thats when I went back to Norton on my Laptop. I looked at Kaspersky but their site says their Password Manager will not work on 64bit OS so that's out.
Considering the nearly unfathomable mess that the Norton product designers and programmers have made of the ID Vault over the last two years and the reputation damage they continue to bring upon themselves and the Norton Company due to their perpetual failings, accentuated with an uncommonly arrogant defensiveness for said failings, and outright pigheadedness; I truly do believe Symantec would be better served by biting the proverbial bullet, abandoning this now completely botched up boondoggle for the lost cause that it truthfully is, and arrange licensing rights for a solution that does work--perhaps from a company such as RoboForm, who 1) really does know what they're doing, then 2) manages to do so in timely fashion, and 3) can get the job done right! Then perhaps the Norton Teams can get back to work on what they're supposedly actually good at--namely, providing improved security solutions...
Wow! There is a lot of unhappy campers here on the Local Vault. I stopped using the local vault in early 2008 and went to RoboForm on all my computers without looking back at Nortons Local Vault. To this day I still use RoboForm. I truthfully don't think Norton is listening to their customers about this issue and the members are fighting an uphill battle. Just my 2 cents.
I certainly agree that we are fighting an uphill battle! Norton no longer cares what users of their products want, they just care about what they want to provide. If the 2 things are completely different, so what? I'm sure the number of customers who don't like the way they are going is huge compared to the number that complaint here, yet they refuse to discuss the issue!!
I don't know about fighting an up-hill battle, maybe it's more like fighting fire with a sinking boat!
As it stands, there is no way to create a local vault on Windows 8.1 as you cannot install NIS12 or N360v6 on that Operating System, you need v21. Perhaps if you use NSS from a service provider you could create a local vault, but I'm not sure if you would retain that if you changed to NIS or N360.
Yet another reason not to convert to Windows 8.#! Of course the actual problem still lives with Norton refusing to accept the fact that the customers want a local vault but it's still nice to get on Microsoft's case once in a while anyway!
Sadly it seems Kaspersky's PWD MGR is not being able to catch up with Firefox evolution and it stopped working with FF 27.x version.
For a while, I decided to use FF 24.x Enterprise Edition (pretty stable and with all add-ons I need funcional, incluind Kaspersky's ones), but won't keep Pure 3.0 as my security suite if they do not solve this. Then I'll have only BitDefender left.
I decided to post this info here, mostly to warn you, folks, about this issue :-)
I don't know about fighting an up-hill battle, maybe it's more like fighting fire with a sinking boat!
As it stands, there is no way to create a local vault on Windows 8.1 as you cannot install NIS12 or N360v6 on that Operating System, you need v21. Perhaps if you use NSS from a service provider you could create a local vault, but I'm not sure if you would retain that if you changed to NIS or N360.
There was an interesting article (written by Woody Leonhard, and published) at the Windows Secrets website last month relating to the recent turmoils at Microsoft and the Windows 8.x debacle.
Here's the link to the article at the website for those who might be interested...
Agreed, this is crazy. I had local vault from older installs and was able to maintain it, until i had a hard drive crash and had to completely re-install Windows 7 Pro and N360. Now i can't use a local vault. I REALLY don't want all of my passwords in the cloud. We ALL know how safe that is after events this year.
I want to REMOVE this information from the cloud; I am not even sure how it got there, but when I log in to my Norton account, it has all of me passwords in the cloud now. Great that I didn't loose anything, but I don't want it there.
I will have to find another tool to save passwords and disable N360's vault now, but i REALLY need to know how to REALLY delete that information from the Norton servers.
This from a computer security company i have used since V1 of Norton Utilities!!
Just my 2 cents.
Of course the actual problem still lives with Norton refusing to accept the fact that the customers want a local vault but it's still nice to get on Microsoft's case once in a while anyway!