NotHereToPlayGames

LTSC is a version of 21H2.

Doesn't even launch for me!

I kind of have to assume that your XP VM is using an extended kernel or something. I don't know how to test for that as I don't use extended kernels (at least not yet, never know what the future brings). We should be able to tell by OS file timestamps, but I wouldn't know what files to compare timestamps.

I'm the OPPOSITE. I've had jobs that I hated and even one once that put me to "near tears" every time I drove into the parking lot. That d#mn job treated us like SLAVES, like we were property that they owned, "threatening" us every chance they got with "points". I resigned that position and all they asked was "where are you going?". Told them "No where! You MANDATE overtime and I'm good with my money, I can live a year just off of all the overtime money that my coworkers just throw into a brand new car every two or three years. I'm OUT. I'll sit at home and watch Netflix until something comes along that doesn't MANDATE my WEEKENDS and that RESPECTS their employees!". Took me two months which is longer than I was thinking it would take. Downright LOVE my job. Been at this one over a year. LOVE it so much that I work 50 to 60 hours every week without being asked to, come in when I want, leave when I want. No lunch on some days. Two hour lunches on other days. I've never been HAPPIER even though I'm "working" more hours than the SLAVE SHOP ever had me work. It's not "work" when you LOVE what you do!

Based on your screencap, it appears you are running from inside a VirtualBox VM. If you are running "seamless" then you may not really be running v108 or v92 from XP but rather from the VM "overlapping" your XP.

It's dated December 2016. Oops, that's my LTSB. It's dated October 2021.

Neither of those seem to work in 2019 LTSC

In my 2016 LTSB Win10, I could disable Windows Defender Firewall. I am aware of the "risks" associated with this - My computer, My rules, lol. I am in-process of upgrading two laptops to 2019 LTSC Win10 and the Windows Defender Firewall can no longer be disabled. This ( https://github.com/ionuttbara/windows-defender-remover ) looked promising but tons of errors in the console window during execution and Windows Defender Firewall is still enabled. Any suggestions or alternative solutions? Thanks in advance.

That's not technically how it works. But since this debate has already gone full circle, it really seems pointless to proceed. Sometimes people only see what they want to see, hear what they want to hear.

Word.

I can only speak for my build (which is what this thread is here for). I cannot do a full reverse-engineer of Humming Owl's release - but it connects to China! (at bare minimum, it connects to China on the very first launch, can't say I ran it "all day" to see if it connects "repeatedly".) edit - I cite this only as a caution, bring things from Humming Owl's release and "add" them to my release and you can be bringing in "unintended consequences". I have no plans to reverse-engineer to see WHERE this connection to China is coming from.

Russian repack does have the 360 Doctor module. The Russian repack also kept the 360base.dll and the skin file .srx's also contained portions of the 360 Doctor module. I think they did set a flag in the skin file .srx which prevents the icon from showing - that prevents a user from clicking the icon but does not prevent underlying code from launching 360 Doctor. But we have beat this dead horse sufficiently. Followers of the thread can decide for themselves if restoring error code content pane introduces unintended risks or not. We have both made our points and the reader can take it from here.

Because certain error codes cause a javascript event to be "true" that then results in connecting to Chinese IP Addresses. In the file you attached, follow the javascript code for things labeled as "first aid kit", that "first aid" is part of "360 Doctor" which was intentionally removed/disabled from my builds. I guess technically what we need, but I don't know of a good way to obtain, is a URL that results in all three dozen or so "error codes". One URL per error code.

"Upstream" has a feature called "360 Doctor" (I may have the name wrong). SOME of these error codes redirect to a "first aid kit" which is part of "360 Doctor". There are at least 3 dozen error codes. I am not claiming that all of them are tied to Chinese IP Addresses. Some of them are. Not sure why this is being HIT with such resistance. *I* am the one that mod'd the browser being discussed in this thread, am I not? "Oye", as my sister would say. (Unsure of proper spelling.)

Not for me, per se, I don't want the error codes. Unless you (D.Draker) have updated, you're running Build 1030 and there were big changes between 1030 and 2022 then even more changes to 2036 (this thread). I'm just saying "don't assume because you make an arse out of u and me". There have been DOZENS of "issues" reported over the years that were later tracked down to "mixing and matching" and "making assumptions".

Thanks. It is the "first aid kit" entries that will connect to Chinese search engines. We would need example URLs that "trigger" several of these "error codes" to fully confirm/deny that they connect to Chinese IP Addresses. I preferred to "play it safe" and just disable/remove the "possibility".

You lost me. Wasn't really a "reaction". Was it the waving hand emoji that made it look like a "reaction"?

Can't dig deeper from work computer. I will likely not dig into it from home computer either. I've shared the browser in the condition that I use it. End users are of course allowed to tweak to their own liking. Browser choice is always always always "personal preference". That's why we have HUNDREDS of browsers to choose from.

If you go this route, be cautious of versions because some language translations are tied to an "index" number that do not match between my versions and Humming Owl versions. Humming Owl maintains good notes, I leave it to the end user to know what they are merging, just don't assume that they will walk hand-in-hand. Build 1030 language indexes do not match Build 2022. Build 2022 language indexes do not match Build 2036.

They could have just been "click here for more details" types of Chinese search engine links. Regardless, something I have no use for.

I would have to revisit (which would be so back-burner that it's the neghbor's neighbor's stove), but be cautious in restoring neterror.js - some error codes are tied to Chinese search engines. Very likely could be something they introduced in v13+ and may not be in v12. Do not recall, see no real justification to restore this "feature".

I intentionally removed the error pages. One, they were all in Chinese. Two, the error code still exists in the URL and that 3-digit number is all we really need most of the time. Three, some error codes redirected to Chinese telemetry web sites.

Agreed! I've been using a Win10 VM since 2017 (and a Win7 VM, for that matter) but only THIS YEAR migrated my installation that evolved many many times since as an OS onto real hardware.

Generally speaking, I agree. But on the other hand, we really only have a FEW dozen folks that even follow MSFN. We really are a DYING BREED. I guess I also have the "advantage" of a USA flag by my name (population roughly 340,239,956) opposed to Germany (population roughly 83,289,087 [which is a lot higher than I would have guessed]).

I tell everyone that my '55 Dodge is a hybrid. Because it has downswoop trim from a '56 Dodge.