NotHereToPlayGames

Not always. I actually prefer X-Launcher over-and-above 360Chrome's launcher. 360Chrome's launcher has an embedded "integrity check" that can cause problems on some systems (but not on all systems). 360Chrome's launcher has embedded telemetry that has been removed during the patching/modifying of my 360Chrome releases - but its original existence should still regard it as as "suspect" over launchers that do not contain such embeds. X-Launcher is more "universal".

You're not following the whole conversation. All of this was to answer the specific needs of somebody on XP. Why are you throwing Vista into the conversation? The first solution I offered does not work in XP. This solution does. The person we are helping is on XP. Not Vista. Not 10. Not Kylin. Not TempleOS. Not MythOS. et cetera...

Meant as NOTHING MORE than A STARTING POINT. Add to, remove from. Totally up to the end-user preferences.

A starting-point

No, you use what you want, I'll use what I want. D3D9 sets a cache of 4 files. D3D11 sets HUNDREDS of cache files. In other words, SSD Killing Feature

Disabeled chromecast and the UDP ports that it opens.

MSFN members specifically asked how to delete during Supermium exit, I provided a solution. All Chrome-based browsers create, delete, and recreate this file over and over and over. Adding as a startup or exit delete only controls "when", because the browser itself is already creating, deleting, and recreating over and over and over.

A starting-point X-Supermium.ini for Step 7 above. How much or how little one wants the .ini to "do" is totally up to the end-user preferences. The possibilities are ENDLESS. ;------------------------------------------------- [Setup] AppName=Supermium ;------------------------------------------------- [FileToRun] PathToExe=$Bin$\$AppName$\chrome.exe Parameters=--user-data-dir="%Profile%" --disk-cache-dir="$Cache$" --test-type --disable-logging --no-default-browser-check --no-first-run --disable-breakpad --disable-background-networking --allow-outdated-plugins --use-angle=d3d9 --ignore-gpu-blocklist ;------------------------------------------------- [Environment] Profile=$Home$\$AppName$ Registry=$Home$\$AppName$\Registry ;-- performed when portable Supermium is LAUNCHED [Functions] DirCreate=%Profile%|%Registry% FileDelete=%Profile%\BrowserMetrics-spare.pma ;------------------------------------------------- [WriteToReg=%Registry%\$AppName$_1.reg] MainKey=HKEY_CURRENT_USER\Software\Supermium [WriteToReg=%Registry%\$AppName$_2.reg] MainKey=HKEY_CURRENT_USER\Software\Google ;------------------------------------------------- [RunBefore] RegEdit=%Registry%\$AppName$_1.reg;$AppName$_2.reg ;-- performed when portable Supermium is EXITED [RunAfter] FileDelete=%Profile%\BrowserMetrics-spare.pma DirRemove=%Profile%\ShaderCache DirRemove=%Profile%\GrShaderCache DirRemove=%Profile%\component_crx_cache FileDelete=%Profile%\Default\*.tmp;*-journal;log;log.old;*.log;*.ldb DirRemove=%Profile%\Default\GPUCache ;------------------------------------------------- [Options] DeleteTemp=true ShowSplash=false ShowTrayTip=false WriteLog=false

If it were me, I would *delete* anything-and-everything Supermium (files, folders, registry) and start completely over, all brand new! ESPECIALLY if I had a *corrupt* profile writing MULTIPLE BrowserMetric files - there should *NOT* be MULTIPLE FILES. No matter how "complex" my profile is, I would DELETE IT ENTIRELY and start completely over, all brand new! Instructions are for XP x86. 1) obtain Supermium - this tutorial will be using v132 R1 (most recent Supermium) download the nonsetup.zip https://github.com/win32ss/supermium/releases/download/v132-r1/supermium_132_32_nonsetup.zip 2) obtain winPenPack X-Launcher original Source = https://www.winpenpack.com/en/download.php?view.15 but it will take you to here = https://sourceforge.net/projects/winpenpack/files/X-Launcher/1.5.4/X-Launcher_1.5.4.zip/download 3) extract both to temporary folders - we will only copy from them and not use them as-is 4) for the extracted Supermium - a) DELETE setup.exe - personally, I have *never* clicked this! *NEVER* b) DELETE NotoEmoji.ttf - *zero* use to me, if you need this font, install manually like any other font, i *never* trust anything called "setup.exe" c) inside the Supermium subfolder - i) DELETE all three of the Supermium Classic/Ungoogled .cmd files ii) DELETE uninstall.exe iii) DELETE the two widevine files - Widevine only "partially" works in Supermium and things like Netflix do not work, a partially-functioning Widevine is *USELESS* to me iv) optional - DELETE all but the languages you actually use from Supermium's Locales folder 5) for the extracted X-Launcher - a) DELETE the _source, _tutorials, Backups, Documents, Downloads, and Lib folders - the ReadMe folder is not needed either but for the sake of a public tutorial, I leave it for the "license" b) RENAME X-Launcher.exe to X-Supermium.exe (or just Supermium.exe) - this and the next file need to have the same exact name c) RENAME X-Launcher.ini to X-Supermium.ini (or just Supermium.ini) - this and file just previous need to have the same exact name d) DELETE the Software_1 and Software_2 folders inside the Bin folder e) DELETE the Software_1 and Software_2 folders inside the User folder f) I replace the X-Launcher .exe file icon with a Chromium icon, a Supermium icon could also be used, but this tutorial will not go through the icon-swap instructions 6) create the folder where your Portable Supermium will reside - I used C:\Miscellaneous\SupermiumPortable a) copy or move all of the X-Launcher [from Step 5] contents (two empty folders [Bin and User] and two files [the .exe and the .ini] and place them in C:\Miscellaneous\SupermiumPortable b) copy or move all of the Supermium [from Step 4] contents (one and only one folder named Supermium) and place that folder in C:\Miscellaneous\SupermiumPortable\Bin (Supermium is a SUBFOLDER inside the Bin folder) 7) EDIT the X-Supermium.ini file -- sample file included in next post Read through the existing .ini before editing, the power of this file is only limited to the imagination of the user For example, I have some profiles with registry files where my OS has *DIFFERENT* "default browsers" solely depending on which brower I keep open and the OS has *NO DEFAULT AT ALL* if no browser is open You can opt to use a "portable registry" or you can opt to let Supermium use your OS registry, flexibility is endless, all up to the needs of the user 8) Launch using X-Supermium.exe, create desktop or start menu shortcuts that point to X-Supermium.exe No startup commands needed because all startup commands are moved to X-Supermium.ini's Parameters line Shortcuts can have their own icon via OS settings, et cetera

Will actually be "easier" to use winPenPak X-Launcher. I'll come up with some instructions and post later.

The loader will be two files. If we are using the loader from 360Chrome, those two files will be 360Loader.exe and 360Loader.ini. They can be renamed to SupermiumLoader.exe and SupermiumLoader.ini. The names must MATCH with the exception of .exe and .ini.

You're not portablizing the registry entries.

I'll share my setup/config later today.

We shouldn't have to do all the work "for you". These loader .ini files are not that difficult to learn!

Any my archives indicate that I also used winPenPack "X-Launcher" with Supermium and the X-Launcher also has the ability to delete files/folders at exit.

I will not have the time. It's not a priority on my end because Widevine/Netflix does not work in Supermium.

Right you are! Apologies, I should have did a trial-run first. Still should be quite easy. I suspect that 360Chrome's "loader" can be configured to run Supermium. That "loader" has the ability to delete files when the browser that it launches is closed. I have not tried, but it "should" work. Would take several folder/config differences and is not just a "copy Supermium and overwrite 360Chrome" process. There are several other "loader" obtions as well. Or, even just a simple .bat file to launch Supermium (I myself prefer actual "loaders" over .bat files). But .bat files are "extremely easy" and anybody with a keyboard should be able to figure them out.

If you are serious about having Supermium delete them after it quits, this CAN EASILY BE DONE by adding Chrome++ to Supermium then adding one line to Chrome++'s .ini file to silently and invisibly run a .bat file every time you quit Supermium.

This really should scare the living sh&t out of you. Not to scare-tactic or anything, but the "normal" behavior is for there to only be ONE folder and ONE file. The folder is basically always there, the file is erased and recreated by the browser over and over and over. If I were you, I would rebuild my profile ONE STEP AT A TIME. First verify if I only have ONE folder and ONE file with a brand new profile !!! !!! !!! Then rebuild my profile ONE STEP AT A TIME, one variable changed at a time, and track down just what I did that made Supermium start acting NOT-NORMAL.

It should also be noted that this has already been discussed at GitHub and the Supermium developer has already stated that Supermium's --ungoogled-supermium PREVENTS ANY POSSIBILITY OF THE TRANSMISSION OF THE DATA. Which, for the record, is how Official Ungoogled deals with BrowserMetrics also. Full read - https://github.com/win32ss/supermium/issues/1110 Excerpt -

I do! I don't stare at the logs while they are being written but if it lands in the log, then I know more needs done to axe telemetry. I read the log line by line each and ever day. AGREED! It should not be written in the first place! Recording the data is one thing. SENDING it is another. SENDING it is easy to prevent. Perhaps the Supermium developer took the "easy route" - record the data, but don't send it. Only a GitHub Issue would get the developer's response.

I cannot test this in Supermium (I have in the past) at the moment but give this as a Testing Method for anyone interested in PROVING THAT A BROWSERMETRICS FILE IS **NOT** "SENT" ANYWHERE. For one, the minimum file size for this BrowserMetrics file is 4 MB. That's a LARGE file and cannot be "sent" without catching it in the act, it just can't happen, 4 MB is HUGE and not a "blip on the radar" that a blink of the eye would "miss". 1) Launch System Informer or something similar so that you can see how many chrome.exe processes are running. 2) Launch DNSQuerySniffer or something similar to catch DNS activity. 3) Open your file explorer to where your BrowserMetrics file is written. 4) Launch Supermium - do not visit any web sites... let it sit IDLE for TWO FULL MINUTES... 5) Watch how many chrome.exe processes are running via System Informer or similar 6) You will see a chrome.exe process close - continue to not visit any web sites... continue to let sit IDLE... 7) You will see a couple more chrome.exe processes close - continue to not visit any web sites... continue to let sit IDLE... 8) You will see another chrome.exe process close and you will see a BrowserMetrics file eventually written - if not, exit Supermium, let all processes close, relaunch, and LET IT SIT IDLE... 9) Keep doing this over and over and over, launch Supermium, LET IT SIT IDLE, wait for BrowserMetrics to be created, exit, relaunch, LET IT SIT IDLE, over and over and over 10) NO DNS ENTRIES SHOULD EVER BE CREATED DURING ALL OF THIS I still only use Supermium R5. I have never witnessed it sending out BrowserMetrics. I only have one file that gets created, it deletes itself, then it recreates itself. I have never seen it being sent anywhere. Anything more than that, then I revert to this - submit on GitHub.

Don't listen to unproven Conspiracy Theories. Totally disconnect yourself from the internet, disable your network card, you name it. *IF* this Conspiracy Theory were true, then a TOTALLY UNCONNECTED browser would pile these up left and right "because they were not successfuly sent".

Not true.

Same here, I only ever have one of them. If you clear your cache at exit, this file deletes itself at the next launch, but recreates if that session remains open for a certain amount of time.