dllhost.exe com surrogate kqglocmweib

[TiioakTx]

I noticed a few days ago my computer was running slowly.
So i looked at the task manager and noticed a DLLhost.exe running under COM Surrogate, there was 26 of these running and now there is another one running called kqglocmaweib.exe under google chrome. there are 8 instances of this running

 

[TwinHeadedEagle]

Hello,



They call me TwinHeadedEagle around here, and I'll be working with you.



Before we start please read and note the following:

• At the top of your post, please click on the "Watch thread" button and make sure to check Watch this thread...and receive email notifications. This will send an email to you as soon as I reply to your topic, allowing me to solve your problem faster.
• Please do not install any new software during the cleaning process other than the tools I provide for you. This can hinder the cleaning process. Please do not perform System Restore or any other restore.
• Instructions I give to you are very simple and made for complete beginner to follow. That's why you need to read through my instructions carefully and completely before executing them.
• Please do not run any tools other than the ones I ask you to, when I ask you to. Some of these tools can be very dangerous if used improperly. Also, if you use a tool that I have not requested you use, it can cause false positives, thereby delaying the complete cleaning of your machine.
  
• All tools we use here are completely clean and do not contain any malware. If your antivirus detects them as malicious, please disable your antivirus and then continue.
• If during the process you run across anything that is not in my instructions, please stop and ask. If any tool is running too much time (few hours), please stop and inform me.
• I visit forum several times at day, making sure to respond to everyone's topic as fast as possible. But bear in mind that I have private life like everyone and I cannot be here 24/7. So please be patient with me. Also, some infections require less, and some more time to be removed completely, so bear this in mind and be patient.
• Please stay with me until the end of all steps and procedures and I declare your system clean. Just because there is a lack of symptoms does not indicate a clean machine. If you solved your problem yourself, set aside two minutes to let me know.
  
• Please attach all report using
  
  button below. Doing this, you make it easier for me to analyze and fix your problem.
  
• Do not ask for help for your business PC. Companies are making revenue via computers, so it is good thing to pay someone to repair it.
• If I don't hear from you within 3 days from this initial or any subsequent post, then this thread will be closed.

Fix with Farbar Recovery Scan Tool

This fix was created for this user for use on that particular machine.

Running it on another one may cause damage and render the system unstable.

​

Download attached fixlist.txt file and save it to the Desktop:

Both files, FRST and fixlist.txt have to be in the same location or the fix will not work!

• Right-click on
  
  icon and select
  
  Run as Administrator to start the tool.
  (XP users click run after receipt of Windows Security Warning - Open File).
• Press the Fix button just once and wait.
• If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
• When finished FRST will generate a log on the Desktop, called Fixlog.txt.

Please attach it to your reply.

 

[TiioakTx]

awesome lets get this computer clean

 

[TwinHeadedEagle]

Okay, follow my steps when you're ready.

 

[TiioakTx]

I would like to say thank you for the help, but it seems we are too late. The hard drive has crashed on the computer. I can not get it to boot in any form at all. It just black screens with a message saying " The file is possible corrupt. The file header checksum does not match the computed checksum. " I don't even get the chance to opt into the bios to try to boot in safety mode. I made this post on my very old laptop.

 

[TwinHeadedEagle]

How did that happen?

 

[TiioakTx]

no clue. was posting on here than had to run work. came like 2hrs later to that black screen and message. tried to reboot and got the same screen again

 

[TwinHeadedEagle]

We will have to work outside windows to try to fix your problem:




Please download Farbar Recovery Scan Tool and save it to a flash drive.

• Plug the flashdrive into the infected PC.
• Restart your computer and tap F8 to bring up the Advanced Menu, then click Repair your computer
• Follow the prompt to enter keyboard input method, and then the prompt to enter a password. If the machine does not have a password, simply click Enter.
• In the Choose Recovery Tool menu select Command Prompt.
• You will see a big black window with a blinking cursor (command prompt).
  
  
  
  
  
  Access the notepad and identify your USB drive
  
  In the Command Prompt please type in:
  

  notepad

  and press Enter.
• When the notepad opens, go to File menu.
• Select Open.
• Go to Computer and search there for your USB drive letter.
• Note down the letter and close the notepad.
  
  
  
  
  
  Scan with Farbar Recovery Scan Tool
  
  Once back in the command prompt window, please do the following:
• Type in e:\frst.exe and press Enter.
  You need to replace e with the letter of your USB drive taken from notepad!
• FRST will start to run. Give him a minute or so to load itself.
• Click Yes to Disclaimer.
• In the main console, please click Scan and wait.
• When finished it will produce a logfile named FRST.txt in the root of your pendrive and display it. Close that logfile.
  
  Transfer it to your clean machine and include it in your next reply.

 

[TiioakTx]

ok, after hitting f8 once the computer starts to boot I have a black screen with the following options. windows 7 or windows 7 loader XE and at the bottom of the screen it says windows memory diagnostic
enter=choose tab=menu esc=cancel

 

[TwinHeadedEagle]

When you seletc Windows 7 or Windows 7 loader, press Tab button. Then you should see Repair option.

 

[TiioakTx]

when i have the white bar over windows 7 and then hit the tab key it moves the bar to the bottom of the screen to the windows memory diagnostic, if i have the bar over the windows 7 and hit enter to choose it, it tries to boot the computer and I see no repair option. Would you like a picture of my monitor to see what I am talking about?

 

[TwinHeadedEagle]

Yes, I would like to see

 

[TiioakTx]

Hope that it is a good enough image
the white bar is over the " windows 7 loader xe "

 

[TwinHeadedEagle]

That is all right. What happens when you switch to Windows 7 above and press Tab?

 

[TiioakTx]

if have the white bar over the windows 7 and then hit tab, the white bar moves to the bottom of the screen and covers up the windows memory diagnostic

 

[TwinHeadedEagle]

When you highlight it, try pressing F8 again. Do you now get Repair your system option?

 

[TiioakTx]

there we go, now i see;
repair your computer
safe mode
safe mode with networking
safe mode with command prompt
enable boot logging
enable low-resolution video (640x480)
last known good configuration (advanced)
directory services restore mode
debugging mode
disable automatic restart on system failure
disable driver signature enforcement
start windows normally

 

[TiioakTx]

So I scrolled back up the thread and did the instructions as you said to do, here is the file

 

[TwinHeadedEagle]

Download attached fixlist.txt and save it to your USB flashdrive as fixlist.txt

>> Boot into Recovery Environment


Start FRST in a similar manner to when you ran a scan earlier, but this time when it opens ....

• Press the Fix button once and wait.
• FRST will process fixlist.txt
• When finished, it will produce a log fixlog.txt on your USB flashdrive.

>> Exit out of Recovery Environment and post me the log please.



Try to boot Windows normally...

 

[TiioakTx]

Here you go. When I tried to boot the computer normally, I still get the " the file is possible corrupt. The file header checksum does not match the computed checksum."