stapp

FIXED
Temp user profile issue in 7219 EAM Win 7 64bit

37 posts in this topic

Updated EAM from 7213 to 7219 on Win 7 64bit.

Turned laptop off.

After a few moments turned it back on again (to confirm delay in boot fixed now)

Then got to old user profile issue again. Had to log out and log in again as me.

Attached are both sets of debug logs from the 2 boots this morning, plus the 4 event viewer errors 1508, 1502, 1515, 1511.

Note the user profile service in this session said it had successfully started (1531) immediately before the errors.

(Frank this user has a ticket with you for similar issue?)

https://support.emsisoft.com/topic/26833-bootvorgang-korrumpiert/#comment-167652

 

a2guard_20170226055045(3236).zip

ev4.zip

0

Share this post


Link to post
Share on other sites

This temp user profile issue happened again today on Win 7 64 bit (the only one it seems to happen on)

I was able to log off and log in again as myself.

No EAM logs as the 7 day only logging rule had been applied by EAM (have turned them back on again)

Picture from my Event Viewer

evlog.PNG.a00eb9389cdb08e26253c8cc19e630bc.PNG
Download Image

0

Share this post


Link to post
Share on other sites

Thanks stapp.

We've created a special update feed so that users that have the issue can switch and provide engine logs.

Support will take care.

0

Share this post


Link to post
Share on other sites

Please let me know if you have these rare userprofile issues, so we can switch you to the special update feed.

0

Share this post


Link to post
Share on other sites

 

Build 7336

Just booted my Win 7 laptop into a temp profile again. Logged out and then logged into into my own profile.

EAM started to autoupdate and 'installing'' got sort of stuck. It ended up taking almost 9 minutes before it finished.

Debug logs attached

a2guard_20170331151518(2996).zip

0

Share this post


Link to post
Share on other sites

Don't know if you need my feedback but I think it may be interesting that my machine starts up every day like brandnew still.

I didn't see the temp profile since I thanked my helpers on February 26th.
While Emsi moved through some versions there was never any problem. Today v.7353 appeared on my screen. Runs smooth and stable.
 
I have no idea cause I didn't change anything in my usage. Good luck!

0

Share this post


Link to post
Share on other sites

Thanks Moreau.

The issue unfortunately is still there, it's very rare and we're on it with highest prio.

 

 

0

Share this post


Link to post
Share on other sites

I'm having issues with temporary profiles created by Windows 7 64bit Ultimate Edition. I have encountered this issue in 2016. I thought my OS was corrupted or my harddrive somehow. I reformatted and reinstalled the OS on a brand new SSD. Everything was working perfectly, until recently where the OS creates a TEMP profile from time to time.

I started a topic recently at https://www.bleepingcomputer.com/forums/t/643713/windows-7-temp-profile about this issue. I think that it's because I have ticked "scan at boot" that EAM is causing some issues when the OS boots.

Only temporary solution to get your profile back is to go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList remove the folder that is pointing to the TEMP profile, and change the SID ending with .bak into the SID without the .bak.

Meaning if the SID is par example "S-1-5-21-####-####-####-1000.bak" than you need to change that to "S-1-5-21-####-####-####-1000"

On the right side, you'll need to change some things aswell :

"Flags" should be 0
"State" should be 0
"RefCount" should be 0

Than reboot the OS to get back into your own profile with all settings, etc..

Until Windows creates a new TEMP profile... Annoying, time wasting, ...

I'm using Process Monitor ( https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx ) to see and check what is going on at boot. I see a lot of ini and dll files from EAM that seems to delay the boot time / boot sequence. I'm not 100% sure about that. A developer knows best what is going on offcourse. :-)

0

Share this post


Link to post
Share on other sites

No need for all that reg stuff,  the temp profile issue will only happen again later if you are prone to it.

Just log out and log in again is the quickest way round it for now.

The devs will sort it very soon I am sure :)

0

Share this post


Link to post
Share on other sites
58 minutes ago, stapp said:

No need for all that reg stuff,  the temp profile issue will only happen again later if you are prone to it.

Just log out and log in again is the quickest way round it for now.

The devs will sort it very soon I am sure :)

Yeah I do know that. Let us hope it won't take long though. EAM is good software. If I choose to switch to another user and than log back into my account, the issue isn't solved. I really need to restart the OS in order to get it solved. Time will tell. I'm hoping to get the issue back when my Process Monitor is running to see what is causing it, so far the issue hasn't come back. I have removed every task (dropbox update & adobe acrobat update) that it needs to do when the computer boots. I have seen online, on another forum something about Google Update. I think it might be the combination of several software that are booting at boot combined with the EAM scan at boot that's causing this. In the log files of Windows 7, I also saw something about a process that is being used, so that it can't load the user profile properly and it was pointing to ntuser.dat under the C:\Users\ directory.

Wondering if this issue occurs in Windows 10.

0

Share this post


Link to post
Share on other sites

I didn't have this TEMP profile issue since april 9, until today, I encountered it again. While being in this TEMP profile, I saw this in Process Monitor. Something was unloading everything on my computer, till the moment that Windows Flag + E gave me an "Explorer.exe can not launch" message. Even MsPaint.exe had this issue. It spammed the same message in the Process Monitor log file for like 20 million times!! Sometimes I saw that it unloaded everything from all my drivers, GPU drivers, every exe that was installed, and so on... Seems more like a virus to me than that it has something related to EAM!

What happened before this was that EAM did an update of the software.

Algemene informatie:

Update gestart: 16/04/2017 3:58:55
Einde update: 16/04/2017 3:59:14
Verstreken tijd: 0:00:19

update successvol

Gedetailleerde informatie:

68 modulen, 509570 bytes

a2hosts.dat (1523 bytes) - Geüpdated
a2trust.dat (450 bytes) - Geüpdated
Signatures\BD\dalvik.ivd (2648 bytes) - Geüpdated
Signatures\BD\e_spyw.cvd (5758 bytes) - Geüpdated
Signatures\BD\e_spyw.i01 (1154 bytes) - Geüpdated
Signatures\BD\e_spyw.i02 (706 bytes) - Geüpdated
Signatures\BD\e_spyw.i03 (538 bytes) - Geüpdated
Signatures\BD\e_spyw.i04 (386 bytes) - Geüpdated
Signatures\BD\e_spyw.i05 (1480 bytes) - Geüpdated
Signatures\BD\e_spyw.i06 (11423 bytes) - Geüpdated
Signatures\BD\e_spyw.i07 (9229 bytes) - Geüpdated
Signatures\BD\e_spyw.i08 (1280 bytes) - Geüpdated
Signatures\BD\e_spyw.i09 (3846 bytes) - Geüpdated
Signatures\BD\e_spyw.i10 (517 bytes) - Geüpdated
Signatures\BD\e_spyw.i11 (535 bytes) - Geüpdated
Signatures\BD\e_spyw.i12 (489 bytes) - Geüpdated
Signatures\BD\e_spyw.i13 (455 bytes) - Geüpdated
Signatures\BD\e_spyw.i14 (503 bytes) - Geüpdated
Signatures\BD\e_spyw.i15 (432 bytes) - Geüpdated
Signatures\BD\e_spyw.i16 (931 bytes) - Geüpdated
Signatures\BD\e_spyw.i17 (690 bytes) - Geüpdated
Signatures\BD\e_spyw.i18 (570 bytes) - Geüpdated
Signatures\BD\e_spyw.i19 (640 bytes) - Geüpdated
Signatures\BD\e_spyw.i20 (543 bytes) - Geüpdated
Signatures\BD\e_spyw.i25 (495 bytes) - Geüpdated
Signatures\BD\e_spyw.i26 (972 bytes) - Geüpdated
Signatures\BD\e_spyw.i27 (1405 bytes) - Geüpdated
Signatures\BD\e_spyw.i28 (603 bytes) - Geüpdated
Signatures\BD\e_spyw.ivd (1010 bytes) - Geüpdated
Signatures\BD\emalware.000 (769 bytes) - Geüpdated
Signatures\BD\emalware.387 (414 bytes) - Geüpdated
Signatures\BD\emalware.388 (462 bytes) - Geüpdated
Signatures\BD\emalware.419 (6143 bytes) - Geüpdated
Signatures\BD\emalware.420 (5853 bytes) - Geüpdated
Signatures\BD\emalware.421 (7374 bytes) - Geüpdated
Signatures\BD\emalware.422 (363 bytes) - Geüpdated
Signatures\BD\emalware.423 (362 bytes) - Geüpdated
Signatures\BD\emalware.424 (380 bytes) - Geüpdated
Signatures\BD\emalware.425 (370 bytes) - Geüpdated
Signatures\BD\emalware.426 (25905 bytes) - Geüpdated
Signatures\BD\emalware.427 (2322 bytes) - Geüpdated
Signatures\BD\emalware.428 (4042 bytes) - Geüpdated
Signatures\BD\emalware.429 (2426 bytes) - Geüpdated
Signatures\BD\emalware.430 (4947 bytes) - Geüpdated
Signatures\BD\emalware.431 (1973 bytes) - Geüpdated
Signatures\BD\emalware.432 (1732 bytes) - Geüpdated
Signatures\BD\emalware.433 (2491 bytes) - Geüpdated
Signatures\BD\emalware.434 (2188 bytes) - Geüpdated
Signatures\BD\emalware.435 (8718 bytes) - Geüpdated
Signatures\BD\emalware.436 (3127 bytes) - Geüpdated
Signatures\BD\emalware.437 (8058 bytes) - Geüpdated
Signatures\BD\emalware.438 (9178 bytes) - Geüpdated
Signatures\BD\emalware.470 (46221 bytes) - Geüpdated
Signatures\BD\emalware.471 (94181 bytes) - Geüpdated
Signatures\BD\emalware.472 (31496 bytes) - Geüpdated
Signatures\BD\emalware.473 (8521 bytes) - Geüpdated
Signatures\BD\emalware.474 (1389 bytes) - Geüpdated
Signatures\BD\emalware.i08 (1536 bytes) - Geüpdated
Signatures\BD\emalware.i21 (364 bytes) - Geüpdated
Signatures\BD\emalware.i24 (718 bytes) - Geüpdated
Signatures\BD\emalware.i25 (24313 bytes) - Geüpdated
Signatures\BD\emalware.i26 (5564 bytes) - Geüpdated
Signatures\BD\emalware.i33 (68474 bytes) - Geüpdated
Signatures\BD\emalware.i51 (71356 bytes) - Geüpdated
Signatures\BD\htmltok.cvd (874 bytes) - Geüpdated
Signatures\BD\java.cvd (3015 bytes) - Geüpdated
Signatures\BD\update.txt (347 bytes) - Geüpdated
Signatures\BD\vbtok.cvd (393 bytes) - Geüpdated

Is there any news about this? This is really getting f. annoying. :-)

Screenshot 16-04-2017 04.27.07.png
Download Image

0

Share this post


Link to post
Share on other sites

Hi misteramd,

The fix for this issue will become available in this months beta and stable release.

However it will take 2 more weeks before we will release this months stable build.

We have created a special update feed with a hotfix for users with this Profile loading issue.

Please follow the below procedure to switch to the special update feed:

1) disable selfprotection in EAM (Settings / General)
2) copy skin.ini into the EAM program folder (attachjed in skin.zip)
3) enable selfprotection in EAM
4) update EAM
5) restart pc

Looking forward to your feedback.

 

 

skin.zip

0

Share this post


Link to post
Share on other sites
4 minutes ago, Frank H said:

Hi misteramd,

The fix for this issue will become available in this months beta and stable release.

However it will take 2 more weeks before we will release this months stable build.

We have created a special update feed with a hotfix for users with this Profile loading issue.

Please follow the below procedure to switch to the special update feed:

1) disable selfprotection in EAM (Settings / General)
2) copy skin.ini into the EAM program folder (attachjed in skin.zip)
3) enable selfprotection in EAM
4) update EAM
5) restart pc

Looking forward to your feedback.

skin.zip

When I click on skin.zip I get:

 

The page you are trying to access is not available for your account.

Error code: 2C171/1

1

Share this post


Link to post
Share on other sites

I did what you said.

I see nothing new. The update installed 66 new things including

66 modulen, 6041815 bytes

a2cmd.exe (2377 bytes) - Geüpdated
a2engine.dll (1055309 bytes) - Geüpdated
a2framework.dll (2659 bytes) - Geüpdated
a2guard.exe (2704 bytes) - Geüpdated
a2hosts.dat (2853 bytes) - Geüpdated
a2service.exe (2625 bytes) - Geüpdated
a2start.exe (3094 bytes) - Geüpdated
a2trust.dat (397 bytes) - Geüpdated
a2update.dll (2349 bytes) - Geüpdated
a2wizard.exe (2667 bytes) - Geüpdated
CommService.exe (2379 bytes) - Geüpdated
EmDmp.exe (2618 bytes) - Geüpdated
EmsiClean.exe (2281 bytes) - Geüpdated
emutils.dll (220453 bytes) - Geüpdated
InstallerHelper.dll (2374 bytes) - Geüpdated
logging.dll (2237 bytes) - Geüpdated
resource.dll (2279 bytes) - Geüpdated
 

 

0

Share this post


Link to post
Share on other sites

HI,

So you still have the userprofile issue ?

Could you confirm that when you check Settings / Updates you see 'se-uptest' in the update feed textbox ?

 

 

 

0

Share this post


Link to post
Share on other sites

did you restart your pc ?

Is the version number 2017.3.2 ?

This version only includes a fix for the userprofile issue, so indeed nothing new ;)

0

Share this post


Link to post
Share on other sites
Just now, Frank H said:

did you restart your pc ?

Is the version number 2017.3.2 ?

This version only includes a fix for the userprofile issue

Yes I did precisely what you said and I restarted my pc. Version is ...

 

Screenshot 17-04-2017 09.05.42.jpg
Download Image

0

Share this post


Link to post
Share on other sites

okay thanks.

Please monitor the userprofile issue, it should be fixed and let me know how things go please.

0

Share this post


Link to post
Share on other sites

I have changed the 5 Maximum Simultanious Update thing to 1, but even than...

It just installed

General Information:

Update started: 17/04/2017 21:07:50
Update ended: 17/04/2017 21:08:00
Time elapsed: 0:00:10

Update successful

Detailed Information:

16 modules, 38573 bytes

a2hosts.dat (443 bytes) - updated
Signatures\BD\e_spyw.cvd (630 bytes) - updated
Signatures\BD\e_spyw.i10 (1347 bytes) - updated
Signatures\BD\e_spyw.i11 (428 bytes) - updated
Signatures\BD\e_spyw.i20 (1178 bytes) - updated
Signatures\BD\e_spyw.ivd (659 bytes) - updated
Signatures\BD\emalware.000 (444 bytes) - updated
Signatures\BD\emalware.494 (1657 bytes) - updated
Signatures\BD\emalware.495 (2535 bytes) - updated
Signatures\BD\emalware.496 (4715 bytes) - updated
Signatures\BD\emalware.502 (16513 bytes) - updated
Signatures\BD\emalware.i04 (524 bytes) - updated
Signatures\BD\emalware.i27 (6078 bytes) - updated
Signatures\BD\htmltok.cvd (638 bytes) - updated
Signatures\BD\java.cvd (437 bytes) - updated
Signatures\BD\update.txt (347 bytes) - updated

But there is no se-uptest. The only thing I found is inside the skin.ini file you gave me "[general]
feed=se-uptest"

Screenshot 17-04-2017 09.08.43.png
Download Image

0

Share this post


Link to post
Share on other sites

Hi,

Quote

I have changed the 5 Maximum Simultanious Update thing to 1, but even than...

How is this related to the userprofile issue ? 
The 5 simultaneous update connections setting is related to the speed of update downloads only.

 

0

Share this post


Link to post
Share on other sites
1 minute ago, Frank H said:

Hi,

How is this related to the userprofile issue ? 
The 5 simultaneous update connections setting is related to the speed of update downloads only.

 

Nah, I was trying to trigger that se-uptest message in the Update Feed if it is even there, but I can't even click on the field to open the box, nor the Question Mark next to it to read for what it is.

0

Share this post


Link to post
Share on other sites

yes that's correct.

If you add an update feed in the skin.ini, you can't change it anymore in the UI.

Not sure why it doesn't display se-uptest.

Anyways you have the correct version 2017.3.2 installed.

Let's wait for your confirmation that this version fixed the userprofile issue.

0

Share this post


Link to post
Share on other sites
15 hours ago, Frank H said:

yes that's correct.

If you add an update feed in the skin.ini, you can't change it anymore in the UI.

Not sure why it doesn't display se-uptest.

Anyways you have the correct version 2017.3.2 installed.

Let's wait for your confirmation that this version fixed the userprofile issue.

So far so good. I wish I knew what triggered Windows to create a temp profile to really know if it's fixed or not.

0

Share this post


Link to post
Share on other sites

Hi,

Good to hear.

The Userprofile issue is not reproducible at will.

It -could- occur during the time EAM locks the profile during boot time, which is for a few millisecond only.

 

0

Share this post


Link to post
Share on other sites
22 hours ago, Frank H said:

Hi,

Good to hear.

The Userprofile issue is not reproducible at will.

It -could- occur during the time EAM locks the profile during boot time, which is for a few millisecond only.

 

I'm not sure if this is related to EAM or not, but yesterday when I "shutdown" my Windows, the turning icon next to "Shutting Down..." stopped turning, meaning it stopped in the middle of the shutdown process. I had to manually switch the PC off and back on.

I do see a "0x40010004" error code, meaning some app has been forced to shutdown, but this happened not by me.

Beheer van bureaubladvensters is afgesloten met code 0x40010004

Desktop Window Manager is closed with code 0x40010004

De kennisgevingssubscriber van winlogon  <SessionEnv> was niet beschikbaar om een kennisgevingsgebeurtenis te verwerken.

The knowledge gevings subscriber of winlogon <SessionEnv> was unavailable to handle a notification event.
0

Share this post


Link to post
Share on other sites

Hi,

We currently are fixing an issue related to W10 that could cause the shutdown issue you experienced.

As soon as I have news i'll post it here.

Thanks

 

0

Share this post


Link to post
Share on other sites
2 hours ago, Frank H said:

Thanks & I'm using Windows 7 64bit on my main computer. I have EAM on my Win10 64bit in offline modus, but I need to remember to buy a new license for Win7 & Win10. Currently I'm using a license for my Win7 64bit only.

So far no temp profile!

0

Share this post


Link to post
Share on other sites

Thanks for your feedback !

you can easily add an additional seat to your existing 1 seat license and renew your license with a nice discount, which increases per year,  here:

https://www.emsisoft.com/en/order/renew/

thanks

0

Share this post


Link to post
Share on other sites

Well, still no issues. Seems to be solved. I'm hoping it stays this way. :-)

0

Share this post


Link to post
Share on other sites

Thanks for your feedback, it's appreciated.

0

Share this post


Link to post
Share on other sites

It's solved. I didn't have any trouble for a long time. Booting like normal, shutting down like normal.

0

Share this post


Link to post
Share on other sites

Thanks misteramd !

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.