Temporary user profiles created every now and then after installing latest version

Enable this option:
Setup > Update > Advanced update setup > Pre-release updates > Enable prerelease updates.


Then Ok > Ok >Update > Update virus signature database
It would be good to restart your pc.

 

well the pre-release updates was already ticked did a manual update after but said latest edition so i don't think this is the problem

 

had pre release update selected on mine past 2-3 days, still causing temp profile issue

 

Have had pre-release updates activated for last several days experiencing temp user account creation still.

 

1 more here with same problem since 4.2.35.

Windows 7 64 bit plus the usual Office ond adobe reader etc.

Only ever have 1 user logged on at a time. Logoff, someone else logs on etc etc and intermittently you get the created temporary profile. Logoff and back on again typically ok next time.

Wierd!

 

I built a new computer for my father and his family 2 weeks ago. He called me a couple days later with this problem. I initially spent time running memtest and a couple benchmarks to stress the system to see if any other errors would occur. After finding nothing I also disabled the power conservation features on the motherboard in case the voltage changes were causing problems with the hardware I chose. I also tried with all stock values versus overclocked.

Ultimately I reformatted and reinstalled Windows 7 64 Home. I installed the roughly 17? updates from MS immediately followed by installing ESET 4.2 because I hadn't yet suspected it as the culprit. The temporary profile continued to happen randomly to everyone and I realized that *logically* it wasn't defective hardware else it would manifest in more ways than just the login. I decided to remove ESET Smart Security and thus far the problem has gone away. Originally it was happening every day, there are 5 users. 1 admin and 4 regular users and each was susceptible to the login failure creating a temporary account. The PC would run constantly and they would just log out / in as needed. Following a reboot they could always log in successfully.

Because this is not my PC I can ask if my father would mind dealing with the hassle if you need me to reinstall and try specific settings, I used all default values of the current 4.2 download. I may not be able to help though as he and my sisters might just prefer to not have to randomly wait to login to a temporary account and have to reboot. My apologies if I'm not much help but I am another case of this incident occurring.

 

Any progress on this one? I've got 2 out of 2 computers that do this far to often to keep me sane.

cheers

 

Restored back to ESS 4.0.474 no issues in 3 days, kind of reminds me when moving from ESS 3 to ESS 4 on Vista the only way to get 4 to work properly and a working internet connection was a clean install of Vista.

 

I rebuilt 2 machines from the bare disc up, installed 4.2.35 and both exhibit this issue.

I'm not rebuilding my computers again, thats pathetic, but do wonder if it is anything to do with saving my old 4.0.437 settings and importing tham back in... but I'm more likely to try something other than ESET than rebuild my computers again.

Geez, is it just me or does it seem that everyone so negative with this product just now?

cheers all

 

Please somebody confirm or deny that disabling self-defense make a difference as we are unable to reproduce the problem on any of the Windows 7 systems when switching between several profiles. Did you have any applications running when switching between profiles? Had you recently run any specific application (e.g. email client) before the problem manifested or temporary profiles are created even if you switch to another profile immediately after the system starts up?

 

Marcos I have had it happen on initial install and just doing a restart, waking up from sleep mode, logging in from one account to another, and just logging into the machine on start-up, may not happen all the time but at least once a day sometimes 3 times checking the logs. I'll give the latest version a try and see what happens, Day 4 with 4.0.474 no errors.

I did try your earlier suggestion, but still got the errors.

 

ESS components protection disabled - the same situation.

ntuser.dat handle - System process PID 4

Looks like ntuser.dat of not-logged users are locked after Virus database update.

 

Hi Marcos I can confirm it does happen even with self-defense disabled, occurred on boot up and login this morning.

 

Same here. And I can confirm the behaviour Gizmo described.

After rebooting I can log into any account. After the first Virus database update, I can't log into any account, except the one the update was done in.

Windows event log shows:

"The process cannot access the file because it is being used by another process.
File C:\Users\[username]\ntuser.dat "

System is Win 7 x64, ESS 4.2.40.

This is REALLY annoying - please get it fixed!!!

 

Could you please describe the scenario in more details? I gather that you:
- started the system and logged on to Windows 7 (not logged to several accounts at a time)
- an update was run (during the startup or later? Perhaps you could disable automatic updates for a while and run them manually to figure out the exact circumstances under which the issue occurs)
- after the update, you attempted to switch to another profile which failed and a temp. profile was created instead

I can assure you that this issue is treated with highest priority and we're doing our best to pinpoint it and fix it in the next build providing that the cause is found.

 

Marcos,

It can happen from a cold boot, a warm restart, logging off from one user account to another, switching user account, wake from sleep. I only log in as a standard user for everyday use.

 

So here's what's going on on my machine:

3 users, one of it admin (but it doesn't seem to make a difference if admin account or not).

After the first boot and login an update is done automatically. After that, no other user can log into his account. The only usable account is the one the update was done in.

The update interval is 3 hours, so after a reboot, everything is fine for 3 hours - until the next update. After that, only those users can log into their accounts, which were logged in during the update.

So for me, a workaround is either keeping all users logged in (still needs one reboot after the first start) or disabling automatic update and update only manually before a shutdown.

Still annoying - but I guess it's hard to track down if you can't reproduce it on your machine.

All this started after the update from version 4.0.474 to 4.2.40.

 

After a clean install to get ESS 4.0 to play nice with Vista when it was first released, I now find that not even clean install will not get ESS 4.2 to play nice with W7.

My solution Eset will be losing my custom which means 5 licences not alot I know, I am now trialling alternatives.

 

ive already switched to 30 day trial of bitdefender, if eset cant resolve this issue will probably purchase their software instead, loads win 7 quicker and no temp profile issues

 

watch out, i have 3 unopened support tickets from 4 years ago for a product called bitdefender game safe, which went wrong after a week, and that's all i used it. my bad, i didnt check but they tried an automatic license renewal (and failed as my card had been replaced)
the support just never happened. the forum is very helpful though.
just a word of caution.

 

It is no problem to emulate this behaviour in virtual envinronment.
Win 7 x64 , ESS 4.2.40 64b

one account administrative rights
one account user rights

Check login with each accout.

Install ESS and reboot

After the reboot :
login with administrative account go to the Eset GUI
choose Advanced GUI mode
-> Tools -> Scheduler - > Execute task to check startup files (which occurs after virus database update by default)

Wait a while.
Go to Start switch user (or log off) and login with account with user rights.

After a while you should see the temporary user profile instead of normal user profile.

 

Does that mean that disabling the startup scan tasks in scheduler makes the problem with temporary profiles go away? Could somebody else confirm it? In that case, the problem can be related to what is being scanned which might be the reason why it's not possible to reproduce it on our systems and a lot of other users haven't experienced it either.

 

Hi!

I disabled the startup scan and created a new one to happen daily at 2200. Ie it checks for the updates then and does it's stuff. (There are rarely anybody at home who will log off to let someone else log on after that). Thanks FTT and Gizmo! Your findings pointed me into the right direction.

Seems to work. Haven't heard any complaints yet...

Which reminds me that I'll have to check the date of the latest update...

 

Thank you guys, it seems we're getting the issue pinpointed. Those who experience the problem with temp profiles, please create a log from SysInspector on the affected machine, put your nick in the zip archive's name and upload it to ftp.nod.sk/support. PM me or post here when done, we'll compare the logs to see what they have in common. If disabling startup scan tasks does not resolve the problem for you, let us know.

 

disabling start up scan made no difference temp user accounts straight away reverted back to 4.0.474.0 all sorted