The Windows OS Thread - Formerly THE OS for gamers and normies, now sadly ruined by Pajeets

TPM has always been an onchip/board ASIC even when it was implemented in Android phones for fingerprint unlock. Or at least it was for a time in select Samsung and Google phones. A TPM chip should only do three things.

1.Generate a cryptographic key in the ASIC's memory.
2.Receive input and encrypt and store it in the ASIC'S memory.
3.Receive input and send a success signal if it matches encrypted data.

When you make an account or change your credentials, it does 2 for your password or credentials.
When you enter your password or credentials it does 3.

If it does anything more it's insecure. TPM motherboard chips are not developed or produced by Microsoft. They are developed and produced by third part silicon manufacturers. Take it up with Qualcomm if it's insecure not Microsoft. As Microsoft only accesses your TPM chip through an API which the board manufacturer's drivers provide.

This is of course assuming that Microsoft isn't scanning the data before it gets to the chip, not that that would be any different then just sending it to the NSA when you enter it on the login screen.
 
Last edited:
You posted a story written in 2021 about a bug that was patched in 2020. gr8 b8 m8
Microsoft recently addressed 60 known fucking bugs and vunlnerabilities in their shitty operating system like a few days ago. Imagine how long those were left unattended and just how many other issues have not been detected by their shitty team.

Not to mention that their patches don't always work. The fact that they claimed to have "fixed" all those issues is not a guarantee in the slightest.
By the way, I'm a dumb nigger.
Will you tell me why Windows is superior? Judging from everything I've seen recently in this thread, I'd say it kinda sucks.
>You exaggerated about the use of compilers in my dogshit installers.
Sorry, ma'am. I haven't used 'jeetdows in a little over three years. Believe it or not, I can't list every .exe installer I've ever used.
 
Last edited:
  • Dumb
Reactions: Betonhaus
As soon as this guy realizes what a fucking retard he is for thinking the Office installer compiles Word from sources.
>Big Corpos hate him
>Learn how to obtain source code for popular Windows software with this one little trick


Oh look, I can draw circles on Linux.

 
  • Thunk-Provoking
Reactions: Gog & Magog
Microsoft recently addressed 60 known fucking bugs and vunlnerabilities in their shitty operating system like a few days ago.

Yes, fixing bugs is an important, if boring, part of software development.

Debian vulnerabilities:

Arch vulnerabilities:

openSUSE vulnerabilities:

RHEL vulnerabilities:

Believe it or not, I can't list every .exe installer I've ever used.

Can you name even one piece of relatively mainstream Windows software you've used that built from sources when you installed it?

Sorry, ma'am. I haven't used 'jeetdows in a little over three years.

I've been using Linux for 18 years.
 
TPM has always been an onchip/board ASIC even when it was implemented in Android phones for fingerprint unlock. Or at least it was for a time in select Samsung and Google phones.

You should read the article. On-board TPM is insecure because the initial communication across the CPU-TPM bus at boot time is insecure. On-chip TPM doesn't have this problem.
 
And you got filtered so hard you're shilling for Microcock? Without even modding the fucking thing? :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story: :story:

Huh. You still haven't answered the question:

Can you name even one piece of relatively mainstream Windows software you've used that built from sources when you installed

How many emojis do you think it will take to distract people from the fact that you don't know how installers work and thought that Linux distros don't issue regular security updates?
 
  • Like
Reactions: Dante Alighieri
How many emojis do you think it will take to distract people from the fact that you don't know how installers work and thought that Linux distros don't issue regular security updates?
That's your epic own here? In that case:
  1. Most of what I installed was cracked games and most of them compile the games. I'm sorry that I can only remember what I've worked with personally and don't have an academic knowledge of your dogshit .exe installers.
  2. I never said Linux doesn't have security updates. The main difference here is that while Windows has insane bugs and vulnerabilities, Microsoft pretends there's no problem with their software. Judging by the four links you posted it's fair to say that FOSS devs are much more open about their issues.
Can you feel how you feel about the fact that Microsoft datamines you and gives that data to the NSA from the moment you install Windows 11?
 
That's your epic own here? In that case:
  1. Most of what I installed was cracked games and most of them compile the games. I'm sorry that I can only remember what I've worked with personally and don't have an academic knowledge of your dogshit .exe installers.
  2. I never said Linux doesn't have security updates. The main difference here is that while Windows has insane bugs and vulnerabilities, Microsoft pretends there's no problem with their software. Judging by the four links you posted it's fair to say that FOSS devs are much more open about their issues.
Can you feel how you feel about the fact that Microsoft datamines you and gives that data to the NSA from the moment you install Windows 11?
Windows Installation Process
An installer will take the following steps to set your app up for use (the precise order of which may vary depending on the developer's customizations):

An installer can contain other archives, like the aforementioned MSI or formats like CAB. As a first step the installer will extract these to a temporary location.
Next, it will check to see that any dependencies that have been set are available. If anything's missing it will download it if possible, or exit the installer with an error if not.
If any dependencies are required, they will be installed first using whatever installer they come with (ever had an install interrupted for .NET Framework?).
Next, the installer will begin copying the app's files and placing them in their correct location.

Windows does not compile for installers. Speaking for someone who has actually written and compiled programs and has more then two brain cells

How about you show us one of these "cracked games" where you can walk us through the exact step where the program is compiled? Or are you talking out of your ass and don't understand anything past follow the step by step instructions without understanding the underlying operation.
 
  • Agree
  • Like
Reactions: 419 and N Space
Most of what I installed was cracked games and most of them compile the games.
You mean unpack? I usually rip the music from cracked setups and I have never seen any with source code for the games in them, it just takes forever with some repacks because they use absurd compression settings
 
Most of what I installed was cracked games and most of them compile the games. I'm sorry that I can only remember what I've worked with personally and don't have an academic knowledge of your dogshit .exe installers.
Exceptionally few games have open source code, which you'd need to be able to compile.
To clarify, and please don't be offended, but I think it's genuinely necessary: Compilation is when a computer runs a software that translates source code into processor instructions. It's a very arduous task, especially for larger binaries such as games, and you never do it if you can avoid it. Ignoring the fact that very few companies are eager to share their source code in the first place, just the fact that downloading games and updates from stores like Steam would take up ten times more bandwidth and hundreds of times more CPU time, if you were compiling everything yourself, means you fucking never do.

What your installer is doing is decompressing files like 3D models, audio, and textures for the 3D models, and placing all the files in the right folders, and creating a shortcut to the executable in your start menu. They don't compile anything. When a cracked game from the likes of fitgirl takes so much longer to install than the same game from Steam, it's simply because they're using more intensive compression methods in order to save on bandwidth. They're not compiling anything.
 
  • Agree
Reactions: 419
How about you show us one of these "cracked games" where you can walk us through the exact step where the program is compiled?
You are fucking autistic and gay.
5889143-df9c59ec7e923e58b6912a2e680d3c5a.png
betonhaus-gay-loves-story.png
I'm not going to look up installers I downloaded years ago for your retarded semantics argument, you autistic faggot. Consider taking more testosterone supplements because the gay is coming back.
You mean unpack? I usually rip the music from cracked setups and I have never seen any with source code for the games in them, it just takes forever with some repacks because they use absurd compression settings
What your installer is doing is decompressing files like 3D models, audio, and textures for the 3D models, and placing all the files in the right folders, and creating a shortcut to the executable in your start menu. They don't compile anything. When a cracked game from the likes of fitgirl takes so much longer to install than the same game from Steam, it's simply because they're using more intensive compression methods in order to save on bandwidth. They're not compiling anything.
That makes sense. I remember seeing the word "decompiling" a lot in the logs which could've been bullshit.
 
I remember seeing the word "decompiling" a lot in the logs which could've been bullshit.
You probably read "decompressing". That's a synonym for "extract from a compressed archive", which is what an installer is actually doing.
 
You probably read "decompressing". That's a synonym for "extract from a compressed archive", which is what an installer is actually doing.
I couldn't tell you, it's been too long. I find it kind of funny that @the rat can get away with saying that you have to compile every program on Linux, but I get put on trial for confusing the words decompress and decompile.

I guess if you use Microcuck's software every day, you're bound to pick up these dishonest tactics.
 
I couldn't tell you, it's been too long. I find it kind of funny that @the rat can get away with saying that you have to compile every program on Linux, but I get put on trial for confusing the words decompress and decompile.

I guess if you use Microcuck's software every day, you're bound to pick up these dishonest tactics.
Only a handful of Linux distros bother with compiling, if he's claiming otherwise he's every bit as wrong as you were. Windows can compile, Linux can compile, most of the time you don't want to. Mostly you were "put on trial" because you were very stubborn about something you were very wrong about.
Gentoo is the famous distro that exclusively uses compilation, but you can resort to it if a precompiled binary isn't available on other distros also (as well as on Windows, but it's even more rare there). NixOS even switches to compiling automatically if no binary for that specific software package is available yet. But if you can avoid compiling, you will, because it takes up a lot of extra time and performance, and most of the time there's zero benefit to it. For some specific applications you can squeeze out a few percent more performance by applying model-specific optimisations or instructions, but usually you're just spending hours installing software that otherwise would take less than a minute.
 
Back