MISTERAMD

Member
  • Content Count

    34
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by MISTERAMD

  1. Well I disabled the EAM Self Protect, removed skin.ini, enabled EAM Self Protect, Clicked on Update... Currently I'm at version 2017.7.0.7838 With Beta, Stable and Delayed under Update Settings. Thanks all 100%
  2. I'm still at version 2017.3.2 when there is already a newer version 2017.7.0 How come my version isn't updating properly? Because of that se-uptest ini file you gave me?
  3. It's solved. I didn't have any trouble for a long time. Booting like normal, shutting down like normal.
  4. Well, still no issues. Seems to be solved. I'm hoping it stays this way. :-)
  5. 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!
  6. 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.
  7. 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.
  8. 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.
  9. 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"
  10. Yes I did precisely what you said and I restarted my pc. Version is ...
  11. I didn't encounter another user profile issue, but I don't see that uptest.
  12. 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
  13. 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

  14. 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
  15. 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. :-)
  16. 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. :-)
  17. 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.
  18. 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.
  19. 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. :-)
  20. 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. :-)