NotHereToPlayGames

That's not the portable version that I use. I don't have the source for mine at the moment. I'll compare the two one of these days. So far, I'm happy with the one that I am using. It too has an "updater" and it too uses "chrome++" (which has never really worked 100% in any Edge variant). And I'm not familiar with the "chrome-next-mini" enhancements that this one references. Personally, I generally "boycott" anything that a MARKETING department gave the name of "enhancements".

There are also software KVM's. Several computers all on the same network can be made to use the mouse and keyboard all from only one of those several computers. The versions that I have used in the past were only used for mouse and keyboard, despite being called KVM, I just didn't need the V part.

I'm leaving it at that for now. If the OP doesn't reply, then I shall view this as me wasting my time and will move on. No skin off my back either way.

Guide for Half Baked Phase 1: Only TWO executibles are required. The first executible is found here: https://www.softpedia.com/get/Antivirus/Removal-Tools/Defender-Remover.shtml Windows Defender has had a ton of Zero Day vulnerabilities exploited (BlueHammer, RedSun, UnDefend). It really is a FALSE SENSE OF SECURITY and a MAJOR source of resource WASTE. If you "want" to run some form of anti-virus, that's your call, it is YOUR computer (personally, I am *against* them, ALL OF THEM, but I do take other preventative measures). If you can't bring yourself to AXE IT, then, and no offense, but you aren't being SERIOUS about wanting to debloat (even half-baked). Right-click it and Run as administrator and select the "Y" option (your computer will reboot): The second executible is found here: https://www.majorgeeks.com/files/details/windows_update_blocker.html Download, extract/unzip, and EDIT the Wub.ini file !!! The original Wub.ini section that we are editing will look like this: [Service_List] ; 2=Auto ; 3=Manual ; 4=Disabled wuauserv=2,4 dosvc=2,4 WaaSMedicSvc=3,4 UsoSvc=2,3 BITS=3,3 EDIT/ADD to that section so that it looks like this: [Service_List] ; 2=Auto ; 3=Manual ; 4=Disabled wuauserv=2,4 dosvc=2,4 WaaSMedicSvc=3,4 UsoSvc=2,4 BITS=3,3 mpssvc=2,4 BFE=2,4 WinDefend=2,4 WdNisSvc=3,4 TimeBrokerSvc=3,4 Save the edited Wub.ini then Run as administrator the Wub.exe for 32bit OS or Wub_x64.exe for 64bit OS. Select Disable Updates, check Protect Services Settings, and click Apply Now.

With no replies whatsoever, the OP has left us all with no other choice but to speculate: he's decided this endeavor is too large to undertake, so he's just going to accept Win10 as a bloated mess and "live with it" or downgrade and miss out on "millions better" in capabilities. I don't want him to "give up" and nobody should ever "live with" the BLOATED MESS that we all know Win10 to be. So here, let's try this a different way. Instead of a full deboat, let's just axe the TOP FIFTEEN "usual suspects" that can bottleneck a Win10 config. Call it "baby steps", a FULL DEBLOAT is HIGHLY recommended, but sure, let's take "baby steps". These "fifteen" alone got my default as-is Win10 VM from OVER ONE HUNDRED processes (did settle to 92 eventually [took 26 minutes!]) per Task Manager down to (in-process). In the past, I've always called my configs that have not been FULLY debloated as Half Baked. 1) Windows Updates 2) Windows Updates 3) Windows Updates 4) Windows Security 5) Windows Security 6) Windows Security 7) Windows Defender 8) Windows Defender 9) Windows Action Center 10) Windows Action Center 11) Windows Firewall 12) Windows Search Indexer 13) Microsoft Edge 14) (in-process) 15) (in-process) Default As-Is (ie, original install, no steps taken yet to debloat): This is only after TWO "baby steps" (ie, two executibles to remove/disable Defender + Updates + Firewall). Low 80s process count after startup, waited same 26 minutes as above, settled down to 77. Technically, the process count was at 77 within a few minutes of startup, but seemed fair to wait the same amount of time for comparison. I'll call this Half Baked Phase 1:

That should be MORE than enough FOR NOW, and only to GET YOU STARTED. There's MORE if you really truly want an OPTIMIZED bloat-free Win10.

And if you dislike things like "Indexer" (of which I am in that crowd), then you should also dislike and disable C:\Users\Admin\AppData\Local\Microsoft\Windows\WebCache.

Probably too large of a script to post here, but I also remove "Get Started", "Windows Backup", and EVERYTHING pertaining to EDGE. Technically, I use Edge (as a third when-needed browser) but ONLY AS A PORTABLE, I DO NOT WANT IT "ENTANGLED" WITH THE OS, AND DO NOT WANT THE BACKGROUND UPDATE CRAP.

I also remove "Security Health App".

These I disable AFTER install (via a PowerShell script). # Computer Management >> System Tools >> Task Scheduler >> Task Schedule Libray >> Microsoft >> Windows # # Disable: # Application Experience # Autochk # Chkdsk # Diagnosis # DiskCleanup # DiskFootprint # Feedback > Siuf # LanguageComponentsInstaller # MemoryDiagnostic # Power Efficiency Diagnostics # Servicing # Speech # WindowsUpdate

These are also COMPLETELY REMOVED from my installation .iso. ie, the Selected="true" entries.

The only "non-waste" of time way for me to compile my list is to provide it IN THE WAY THAT I USE IT. Which in my case is from my WINREDUCER EX-100 config file. All of the Value="5" entries below are my REMOVED services, they're not ever even installed, removed completely from my installation .iso. The Value="4" entries below are my DISABLED services, I allow them to be installed, but they are DISABLED by default. The Value="3" entries below are my MANUAL services. If there is any Value="2" entries, they are AUTOMATIC services. Any Value="1" entries, they are AUTOMATIC (DELAYED) services. Entries with empty value fields just allow the Windows installation process to set them at normal Windows "default". BUT... there are a ton of "services" that have to be "installed" (ie, Windows Indexing/Firewall/Defender are examples), BUT I DISABLE/REMOVE THEM LATER, I just can't disable/remove beforehand. You asked for a list, this is the easiest way to provide one.

I'll compile "my list". But, a word of warning, if you "have faith" in CRAP like "smartscreen" or Windows Defender, than frankly me compiling a list is a "waste of my time" as you (3rd person plural, not referencing "you" as any ONE person) already has your (3rd person plural) view of how that Win10 should be configured. Which is perfectly fine, of course, it is "your" computer.

I've had nothing but HUGE success in that regard! Whether you think of my Win10 experience as upgrading from XP, my Win10 is WAY better, faster, and smoother than XP (even on a 10+ year old laptop with only 4 GB RAM !!!). And a "million times" more CAPABLE. No need to run SLOW-AS-HELL web browsers that just INCREASINGLY "can't do sh#t" !!! !!! !!! Hey, "to each their own". I don't have a mobile phone or tablet to "fall back on", I *MUST* have *everything* work on my computer. So yeah, Win10 really is a "bare minimum" these days. Not to be misread, there are some VERY "capable" Firefox Forks. If that's your thing. "To each their own." Or whether you think of my Win10 experience as upgrading from a previous Win10 version, my Win10 LTSC is WAY better, faster, and smoother than those previous versions of Win10. And I'm not talking "placebo effect", I simply do not fall for prey to PE, I believe in Quantifiable Measurements and never "gut feel".

Well, two things here. 1) There really is zero reason for r3d to fix what HE DID NOT BREAK. 2) We-the-consumer can just slip back to a previous version - IT AIN'T GONNA HURT YOU ONE D@MN BIT TO USE A PREVIOUS VERSION. This is where the Browser Universe is just a bunch of whining babies, it really is the biggest STUPIDITY on the planet that browsers are updated so d@mn fast and no matter how fast it is, there are always folks that want it FASTER. FASTER is WHY we have issues like this. Because the ecosystem is all about pushing updates out fast, fast, fast. INSTEAD OF TRULY TESTING THOSE UPDATES BEFORE SENDING THEM OUT INTO THE UNIVERSE. And we end up with an ecosystem that is "happy" because they get FAST updates instead of GOOD updates. Send out VULNERABILITIES all day long, nobody really cares, "because they fix them fast". No, what we have is that they CREATED those vulnerabilities and sent them out to a population DEMANDING faster update cycles. PUBLIC GOT WHAT THEY WANTED.

I disagree. For one, the user agent is ANCIENT TECHNOLOGY that is DYING, DYING, DYING. And for two, we should never lump Firefox forks (r3dfox, this thread) and Chromium forks (Supermium) into that sort of direct comparison. No offense, but web sites that still do use the ANCIENT TECHNOLOGY of the DYING user agent isn't exactly (pro and con) up to par with the latest "googleims" and therefore stuck with Site A relying on a faked OLD user agent, Site B relying on a faked RECENT user agent, Site C relying on something totally in the middle, and therefore those OLD SCHOOL web sites can never use a ONE-FOR-ALL user agent, you will always have to rely on the "user agent override" settings in about:config.

I'm seriously wondering what the significance is, ie, the "viral" aspect is, of that number THREE. e3k-blah... r3dfox... probably just overthinking it, but that 3 just feels like some "viral meme" that I'm just not "hip enough" to know.

Yeah, I kind of assumed upstream as "e3k-blah" is also affected.

Q.E.D. However, whether this is an rd3fox issue or an upstream issue is "not my problem", no clue if it upstream, no clue if it only r3dfox, don't care, neither is my default browser. edit: those are in Win10. so if this isn't doing this in Win7 or Vista, I cite again as "not my problem", but then we are faced with NO LONGER calling this "Vista+" but saying "don't use on 10 [or 11?]".

v151 not working like it has always worked in the past:

v150 working like it has always worked in the past:

You're not looking at it correctly. I will post PICTURES to demonstrate. Will be back . . .

Okay, but that kind of misses my question. IF this only affects v149, then IT DOES *NOT* EFFECT Supermium. ie, "the sky isn't falling" edit: ie, the "stupidly aggressive" update schedule (that both Chrome and Firefox do!) **CAUSED** the "exploit" so *ONLY* people that "update every d@mn day" (exaggerating for effect) were even effected

What does "exists in the wild" *REALLY* mean? ie, does it really affect v144? Or does it just affect those that "thought" they were safe by always running the most recent?

Everything still working fine after upgrading Guest Additions to 7.0.26.