Jump to content

Corrupted Profile windows 7 fresh install


Recommended Posts

Hi, I wanted to see if anyone is noticing a lot of profile errors in windows 7. We run a computer shop

and noticed in the last month a lot of computers coming back with a corrrupted profile. Emsisoft

anti-malware is on the pc's. I just installed windows 7 64bit fresh on 2 different pc's HP. All windows upates 

are installed. I had all programs done just needed to install a new copy of Emsisoft. Rebooted after Emsisoft

install a BOOM-PROFILE ERROR. PLEASE HELP

Link to comment
Share on other sites

Charles again, its funny how a lot of people are viewing my topic but no comments. 

Remember we run a computer shop. We are having at least 3 COMPUTER RETURNS A DAY due to 

"Temporary profile is loading up". All different brands of pc's. We remove EAM  and problem does not come back.

 

Link to comment
Share on other sites

The temporary profile issue is a known bug. Our developers are trying to resolve it. Right now the only workaround is for the user to log out, and then log back in. They will then be able to use their computer normally.

Link to comment
Share on other sites

  • 2 weeks later...

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. :-)

Link to comment
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 :)

Link to comment
Share on other sites

49 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.

Link to comment
Share on other sites

Are seeing it on Windows 8 and Windows 10.  I have previously discounted EAM as the culprit because it is not occurring on a large number of machines.  But so far, it has only happened on machines with either EAM or Bitdefender installed.

Link to comment
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

Link to comment
Share on other sites

Just so that everyone is aware, we have released a fix for this issue and the update should install automatically:

 

The version number of the update is 2017.3.2.7392, so if you would like to check and see if it is installed then when you open Emsisoft Anti-Malware or Emsisoft Internet Security you can click on the Emsisoft name in the upper-left corner to see the version number.

If you want the version number to be displayed on the Overview screen when you open Emsisoft Anti-Malware/Emsisoft Internet Security, you can do the following:

  1. Open Emsisoft Anti-Malware/Emsisoft Internet Security.
  2. In the little gray box near the bottom that says License, hold your mouse over where it says Renew for free!.
  3. A little X will appear to the right of where it says Renew for free!.
  4. Click on the little X, and the version number will be shown instead.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...