This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Is using chrmstp.exe causing any difficulties? If not then a case could be made for leaving well enough alone.

In addition, given the excitement of  crbug.com/734899  - which caused executables named setup.exe to fail to launch - I can actually see some benefits to leaving things as is.

I'm inclined to close this as won't fix. What think you grt@?

I've been thinking about this, too. I don't think we should change chrmstp in the short term. In the long-term, I was considering randomizing the name of setup.exe at install time, which would make chrmstp unnecessary.

Changing from chrmstp.exe to setup.exe could actually cause regressions due to the issues discussed in  crbug.com/734899 . Therefore closing this bug as WontFix. A separate bug for randomizing the name of setup.exe (or at least always using a high-entropy name) should be created if one has not been already.

Let's use issue 672813 as the randomizing issue. Thanks, Bruce.