Chrmstp.exe on logon

Pesanur

As far as i know, this executable is related with Chrome auto-updater background service, so, Why if Vivaldi installing it without asking permision?

An_dz

Because Vivaldi has not installed it. This file doesn't even exist in my computer.

Pesanur

Sorry, I'm wroted bad the name of the file, is chrmstp.exe. (edited title)

Here and screenshot showing that this file come with Vivaldi.
Attachments:

An_dz

Still I don't have this file, maybe it wrongly came with version 1.0.162.9, I skipped that version. Try installing the new version to see if it's installed.

The_Solutor

I don't have it either, and even google finds very little about it, so I doubt is a Chrome thing.

Can you look at the properties–->detalis of the file?

If nothing is shown there is almost surely a malware.

Pesanur

Damm. I wroted the name bad twice. Now is correctly wroten (yes, checked it several times)..

I tried with several versions of Vivaldi (snapshots until reach the TP3), and each time that I install it, this exe run at system logon.

In properties say that the file is signed by Vivaldi Technologies AS, and the version number mach the version of Vivaldi TP3, so is a legit file.

Note: I'm use the 64bits version.

Ayespy

Maybe it is a 64-bit version thing. I don't know. I don't have it in any of my Vivaldi installs on any machine, though I do have the file in the Chrome install folder on this Win 8.1 64-bit machine. It's not malware. It is something Chrome installs.

The_Solutor

Ok now I see it.

Looks like an exact copy of setup.exe, so I don't know why the file is present twice with two different names.

Anyway it shouldn't be launched on each startup/logon. I guess that for some reason your installation isn't fully finalized and the setup tries to do its final steps on each logon…

Pesanur

@The_Solutor:

Ok now I see it.

Looks like an exact copy of setup.exe, so I don't know why the file is present twice with two different names.

Anyway it shouldn't be launched on each startup/logon. I guess that for some reason your installation isn't fully finalized and the setup tries to do its final steps on each logon…

I dont think that is this. May be if only happen in one OS, but I'm using dual boot, I have Windows 8.1 in my main HD and Windows 10 in the second, and in both happens the same.

Also an interference with the installer by the security software is discarted, as in W8.1 I use Comodo Internet Security, and in W10 I use Windows Defender.