Loading Profile...
Users can't logon after installing VIPRE
VIPRE appears to acquire an exclusive lock on the ntuser.dat file belonging to all non-logged-on users. VIPRE seems to acquire the lock during system startup, before any user has logged on. I imagine this is intended to prevent unauthorized access.
The result is that all users, except the user who installed or activated VIPRE, when attempting to logon receive the message "Windows cannot load the locally stored profile ... using a temporary profile ... The file is in use by another process." Hence, none of the user's settings are available. (Somehow, VIPRE releases the lock when the user who installed VIPRE logs on. I'm not sure if I described all this correctly. It's just what I have observed from trying VIPRE for a while.)
Sunbelt technical support have advised that this is a high priority problem and it should be fixed in a couple of releases. In the meantime, they advise me to shutdown VIPRE when switching users (VIPRE-Ticket#001-00-238889).
"Shutdown" appears to mean "disable the VIPRE Service", since that is the only way I have been able to unlock the ntuser.dat files.
The computer I most want to protect is used by users who do not have administrator privilege. Hence, if the VIPRE Service is disabled to allow them to logon, they cannot start the service after logging on. Anyhow, even users who do have administrator privilege - I do not want to ask them to start a service every time they logon.
Has anyone else experienced this problem? I can't believe I am the only customer who has installed VIPRE on a computer that is at least occasionally used by another user.
Does anyone have a suggested solution?
The result is that all users, except the user who installed or activated VIPRE, when attempting to logon receive the message "Windows cannot load the locally stored profile ... using a temporary profile ... The file is in use by another process." Hence, none of the user's settings are available. (Somehow, VIPRE releases the lock when the user who installed VIPRE logs on. I'm not sure if I described all this correctly. It's just what I have observed from trying VIPRE for a while.)
Sunbelt technical support have advised that this is a high priority problem and it should be fixed in a couple of releases. In the meantime, they advise me to shutdown VIPRE when switching users (VIPRE-Ticket#001-00-238889).
"Shutdown" appears to mean "disable the VIPRE Service", since that is the only way I have been able to unlock the ntuser.dat files.
The computer I most want to protect is used by users who do not have administrator privilege. Hence, if the VIPRE Service is disabled to allow them to logon, they cannot start the service after logging on. Anyhow, even users who do have administrator privilege - I do not want to ask them to start a service every time they logon.
Has anyone else experienced this problem? I can't believe I am the only customer who has installed VIPRE on a computer that is at least occasionally used by another user.
Does anyone have a suggested solution?
I’m a bit cranky
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Assuming my guess that VIPRE locks ntuser.dat to prevent unauthorized access is correct, then I'm not sure if this is effecive, since most users who have privilege to access another user's ntuser.dat would also have privilege to stop the VIPRE service.
A simple solution might be: don't lock ntuser.dat.
Have I got all this hopelessly wrong? My logic doesn't add up. -
Inappropriate?OOPS - Perry has just advised me I don't need to disable the VIPRE service - just right click the VIPRE icon in the system tray and choose shutdown. I haven't tried it yet, but it sounds like it will work, provided other users (including non-administrator users) can restart VIPRE after they logon, and remember to shut it down again before they logoff. It's obviously only a very short-term work-around.
I’m a bit less cranky.
-
Inappropriate?It doesn't work. It stops the VIPRE Service, and users can then logon, but it leaves the Service's start mode Automatic, so that after rebooting users cannot logon again.
I also tried stopping the VIPRE Service and setting its start mode to Manual. After 1 reboot users could logon, but the Service's start mode became Automatic, so that after 2 reboots users could not logon again.
If I set the VIPRE Service's start mode to Disabled, users can logon, but VIPRE is not running and non-Administrator users cannot start it.
I’m quite grumpy.
-
Inappropriate?This only seems to be a problem in Windows Server 2003. I have just tried VIPRE in Windows XP 64-bit, and it works perfectly.
I guess this explains why no one else is responding to my posts. -
Inappropriate?My problem is somewhat simular. I can sign on but it take forever. So I disabled the whole works
-
Inappropriate?I was a bit premature in reporting that VIPRE works perfectly in Windows XP 64-bit. What I meant was that users could logon. However, Internet Explorer takes several minutes to do anything. See my post in Gerald Stanley Tarka's problem "VIPRE 3.1.2315 slows computer to a crawl".
-
Inappropriate?I have this problem in Vista. 50% of the time if I reboot and log in with the account that installed vipre then I get the profile error, I have to reboot again to be able to log in and load my profile...
I also have various problems with pc locking up, emails not download etc.. all fixed by shutting down vipre.. I have yet to purchase a license and currently I am not convinced...
Another "problem" I have is that the trial on one pc randomly resets the trial days to 10days.. it should have expired by now but for some reason it wants to keep running :-)
The copy I loaded on my Windows 2008 server expired after the 14days.
