Creative web design & development

Remove Sendori malware
Fix Google Chrome Error 137

(net::ERR_NAME_RESOLUTION_FAILED): Unknown error.

In this article, I explain how I removed the Sendori malware application on a laptop running Windows 7, and how it caused the dreadful Google Chrome Error 137.

Ski in Sälen - SwedenDuring our last ski vacation my daughter was not able to access the internet on her laptop, using open wifi networks. Vacations are meant to be vacations, not to fix pcs and we forgot about it and enjoyed skiing instead. But once back home I decided to investigate this problem and find why her pc could not access the internet when our other laptop would perfectly work.

I quickly suspected some nasty malware for being responsible of the issue. And I was right!
Something called Sendori was installed on her Fujitsu laptop. She never installed this thing and we couldn't figure out how the Sendori piece of crap was able to install itself on her machine.
But for sure this Sendori stuff is not a legitimate piece of software!

If something installs itself on a machine without the owner's permission, alters the behavior of the computer and does not let the user gets rid of it, it falls into the malware category.

You'd better not believe what these Sendori guys claim on their nicely polished website. This Sendori thing is a malware, it infects your computer and will do nothing good for you. It will corrupt your network access, slowdown your pc, eat memory resources to the max, make internet browsing a pain and sometimes impossible.

The Sendori malware will set itself to start when the system boots. And no hope to deactivate it using msconfig.exe and unchecking what runs at startup. It will reactivate itself immediately.

It comes with an uninstaller, that I did not consider worth trying. Looking at how this piece of junk sneaked into my daughter's computer, I seriously doubt the uninstaller would actually remove it.

Here is how I removed the Sendori malware on Windows 7

- First I booted the laptop in safe mode.
- Then I deleted the folder "Sendori" in c:\Program Files(x86)\Sendori.  You cannot remove this folder if you don't start in safe mode, because the Sendori "service" will be running if you start Windows normally.
- Next I launched Regedit and deleted ALL keys containing Sendori references.
- I ran CCleaner to check Windows registry for potential errors.
- Finally I did a search for "Sendori" on the C drive. I found even more files scattered in the system disk, including DLLs and entire folders.

- Now time to reboot and the Sendori problem should be fixed.

 

Maybe there are easier ways to remove it, but this is how I succeeded. If you don't feel confident editing the system registry you shouldn't do so.

 

No more Sendori, but no more network either

After the deep satisfaction of being able to beat the evil and remove the Sendori threat came more disappointment.

When my daughter tried to connect to her favorite online game (Starstable not to name it) Google Chrome would stubbornly returns a disappointing message with this weird error 137 code:

Error 137 (net::ERR_NAME_RESOLUTION_FAILED): Unknown error.

No more success with Internet Explorer that would not even start.

We fought the Sendori malware, but now the whole network access was gone.

Here comes the whole story. The Sendori crap corrupts the winsock files and installs its own files to hijack the user's internet connection.

In short Winsock (windows sockets API) enables network connections. Without it, network access becomes impossible.
After I removed the Sendori corrupted files, the Windows system was left with no network access configured, not even the Sendori hijacked one, and Chrome would shout its despair with a very cryptic message. I agree that Chrome developers could have written something a bit more helpful to the user here, rather than something nobody would ever understand.

 

Fixing Google Error 137 problem is simple:

In the start menu, go to Programs/Accessories and run Command Prompt with administrator rights.

(To have administrator rights, simply right click Command Prompt and select "Run as Administrator")

Then, in the command prompt window type the following command:

netsh winsock reset

Press enter...
Finally reboot the pc and the problem should be solved. :)

 

Kontakta författaren

E-post:
Ämne:
Meddelande: