Jump to content

Problems with autoupdate to build 7138


stapp
 Share

Recommended Posts

EAM on Windows 7 64bit.

Turned on laptop and was logged in with a temp profile.

Logged out and back into my own profile.

EAM started autoupdate and never finished it. Some things such as taskmanager etc were slow to respond.

In the end I rebooted (went straight to my own profile as normal this time)

EAM has not attempted to update again and still says last update was yesterday when I hover over taskbar icon.

I may attempt manual update later, however I think something is broken :( 

Find attached debug logs, screenshot of GUI and update log.

update.PNG

update log.txt

a2service_20170201065719(1116).zip

Link to comment
Share on other sites

Can I just check which beta update we are supposed to be on?

In Christian's latest changelog here for 7138

https://support.emsisoft.com/topic/26809-emsisoft-anti-malware-emsisoft-internet-security-20171-released/

It shows the same changelog details as 7102

http://changeblog.emsisoft.com/2017/01/23/beta-updates-2017-01-23/

Link to comment
Share on other sites

"Have there been any users reporting user profile issues?" (There's no Zitat icon?)
All the icons are greyed out again, just showing cryptic points in a quadrat. When I move over them with the mouse, nothing happens.



Yes, right now, me.

When I started up my laptop a window opened showing the message "Das Benutzerprofil konnte nicht geladen werden..."

So I went on with "Ok" and the notebook behaved as woken up from Ruhemodus, asking me to click the central icon with my username.

This way I reached my normal desktop.

Happened two times from 3 tries since new version 7138 is installed.

Link to comment
Share on other sites

I was able to load my user profile the first time it happened.

But this afternoon the user profile was completely broken and I had to restore a Macrium image I made a few days ago before 7138.

I have no logs Frank because I restored an image.

But something perhaps is not well :(

Link to comment
Share on other sites

What sort of Event might you expect to see which could have caused this for Moreau and myself?

We both seem to have had the same thing happen, first temp profile login and then broken user profile.

Do you have any thoughts?

 

 

Link to comment
Share on other sites

Hi Moreau,

I think my colleague already replied on the forum. As a temp workaround you could:

Set the EAM service to manual should do the trick. That will start the service only after the profile has been loaded and the a2guard.exe part starts.

 

Link to comment
Share on other sites

  • 3 months later...
Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...