View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0022299 | MMW 5 | General | public | 2026-08-29 08:02 | 2026-08-29 19:18 |
| Reporter | michal | Assigned To | |||
| Priority | immediate | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 2027 | ||||
| Target Version | 2027 | Fixed in Version | 2027 | ||
| Summary | 0022299: MM can create unwanted entries GoogleChromeAutoLaunch_xxxx in Windows autorun | ||||
| Description | It seems new Chromium has some experimental feature causing, that it can create entries like "mediamonkey\chrome.exe" --startup-foreground-launch in Windows Autorun registry section (HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run). Such exe even does not exist, so it does not run anything, but it can clutter Windows registry a lot, because it always creates the same entry with new unique ID few second after every app start. We should switch this feature "LaunchOnStartup" off in Chromium. | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?p=534055#p534055 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3519 | ||||
|
|
Fixed in build 3519. Affected users should delete entries manually (they will need admin rights), i.e. delete in regedit all keys from HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run with name like GoogleChromeAutoLaunch_<GUID> and value containing "MediaMonkey\chrome.exe" --startup-foreground-launch |
|
|
I added also automatic cleanup of these entries during the first run of the new build. It cleans only entries for the same installation folder, to be sure, we really clean only these "our" values. |
