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

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
VMware/Hyper-V
Assuming we're talking about VMware Workstation, know that it won't work well when you also have Hyper-V enabled. Hyper-V hogs all the CPU virtualization instructions which leads to Workstation not having access to them, and it needs access to them to not run like complete shit because it's a type 2 hypervisor while Hyper-V is a type 1 hypervisor, but if the OS you want to run wouldn't run on bare metal then you need a type 2 one.

Or in other words: fuck Microsoft for designing their OS virtualization features like this and fuck VMware for being even more pajeetified than Microsoft and refusing to implement a proper solution for it even though Microsoft already extended a helping hand for any virtualization software that struggles from those instruction hijacks.
 
  • Like
Reactions: Moist Boys
Hey guys, I have an issue. Just got a call from a company offering me fucked ass god-like benefits (80-90k salary, 4 weeks PTO, 6% 401k match) and they want to interview tomorrow. The problem is, I barely know anything about Windows System Administration. Any suggestions on what to learn?

Looking into:

Microsoft Configuration Manager
AD U&C account creation
Windows Server OS
VMware/Hyper-V
Backup/recovery such as RAID

I have some experience with AD and know about raid but would like to learn more.
Unless you plan to lie about your credentials and what you know you don't have enough time to learn anything before the interview.
 
Hey guys, I have an issue. Just got a call from a company offering me fucked ass god-like benefits (80-90k salary, 4 weeks PTO, 6% 401k match) and they want to interview tomorrow. The problem is, I barely know anything about Windows System Administration. Any suggestions on what to learn?

Looking into:

Microsoft Configuration Manager
AD U&C account creation
Windows Server OS
VMware/Hyper-V
Backup/recovery such as RAID

I have some experience with AD and know about raid but would like to learn more.
Windows server setups tend to be more tied to certs and specific software suites + vendors. If you want to BS it you're best off looking into their specific stack of software and trying to appeal there. Try to find out what they're actually using and that's going to be your best bet
 
Oh that's fine then, nothing important would directly impact people
Not to worry regardless, they didn't win the contract so they cancelled an hour and half ago :(

Now that I'm not pressed for time, any suggestions on what to learn?
 
Assuming we're talking about VMware Workstation, know that it won't work well when you also have Hyper-V enabled. Hyper-V hogs all the CPU virtualization instructions which leads to Workstation not having access to them, and it needs access to them to not run like complete shit because it's a type 2 hypervisor while Hyper-V is a type 1 hypervisor, but if the OS you want to run wouldn't run on bare metal then you need a type 2 one.

Or in other words: fuck Microsoft for designing their OS virtualization features like this and fuck VMware for being even more pajeetified than Microsoft and refusing to implement a proper solution for it even though Microsoft already extended a helping hand for any virtualization software that struggles from those instruction hijacks.
It gets worse: Even if you remove the Hyper-V role from Windows, whatever bits and pieces of Hyper-V responsible for interfacing with the processor's virtualization features still get left installed and running on the system - the only way to recover is to wipe your Windows install and start over from fresh. Ask me how I know...
 
It gets worse: Even if you remove the Hyper-V role from Windows, whatever bits and pieces of Hyper-V responsible for interfacing with the processor's virtualization features still get left installed and running on the system - the only way to recover is to wipe your Windows install and start over from fresh. Ask me how I know...
Not really, it's a couple of other dependencies in OptionalFeatures.exe that hog the virtualization extensions that are also utilized by shit like Windows Sandbox and WSL so they get installed by default. Unchecking anything related to virtualization there and then rebooting should unhog them and you can verify it via HWiNFO64. Alternatively force install all of them and then force uninstall them. I had my issues with undoing Hyper-V and I found that that's usually the issue.
 
Not really, it's a couple of other dependencies in OptionalFeatures.exe that hog the virtualization extensions that are also utilized by shit like Windows Sandbox and WSL so they get installed by default. Unchecking anything related to virtualization there and then rebooting should unhog them and you can verify it via HWiNFO64. Alternatively force install all of them and then force uninstall them. I had my issues with undoing Hyper-V and I found that that's usually the issue.
Could have been a weird bug I encountered then, I'm pretty sure I was on a fairly early Windows Insider build of 10 back when I tried it. All I know is I haven't tried to install Hyper-V on anything since.
 
What? Defender rarely goes over 150MB of RAM usage on my machine. How shitty is your PC that it effects performance?
That isnt how its making the PC slow down.

Its because it has to scan every single file you load up, more than once. If you loads a large video file, its quick. But if you run a program that uses lots of smaller files, well then its going to slow right the fuck down. Its not a ram issue, you cannot solve it with brute forcing more "power" at it, its just the way the system is.

Enjoy not being able to turn off defender though, not in a way that stops it from coming back on to slow shit down again.
 
That isnt how its making the PC slow down.

Its because it has to scan every single file you load up, more than once. If you loads a large video file, its quick. But if you run a program that uses lots of smaller files, well then its going to slow right the fuck down. Its not a ram issue, you cannot solve it with brute forcing more "power" at it, its just the way the system is.

Enjoy not being able to turn off defender though, not in a way that stops it from coming back on to slow shit down again.
This and "modern" explorer.exe opening all files in a directory to extract metadata ("working on it") makes it miserable to use Windows 10 & 11. Fucking chugs, doesn't matter how fast my NVME is, doesn't matter that I'm accessing a NAS over 10gbit ethernet, the pajeets managed to ruin the most basic tasks such that a 25 year old PC can run circles around it.
 
Ahh, what a wonderful weather to not go outside, sit at home and shitpost on my -puter. Surely, nothing can ruin thi-
1745680048681.webp
...i-is that a le heckin' forced updaterino?
 
This and "modern" explorer.exe opening all files in a directory to extract metadata ("working on it") makes it miserable to use Windows 10 & 11. Fucking chugs, doesn't matter how fast my NVME is, doesn't matter that I'm accessing a NAS over 10gbit ethernet, the pajeets managed to ruin the most basic tasks such that a 25 year old PC can run circles around it.
best part: this can fuck up too of course to literally list files at one entry per second. didn't happen in a while but I think not even restarting all explorer instances fixes it.

funny bonus: imagine grabbing all that data and then not being able to calculate folder/free size for easy display (got removed in 10 I think, maybe earlier).
 
This and "modern" explorer.exe opening all files in a directory to extract metadata ("working on it") makes it miserable to use Windows 10 & 11. Fucking chugs, doesn't matter how fast my NVME is, doesn't matter that I'm accessing a NAS over 10gbit ethernet, the pajeets managed to ruin the most basic tasks such that a 25 year old PC can run circles around it.
you think that's bad, try attaching a floppy drive but don't put a disk in it. Windows Explorer will just randomly shit the bed
 
you think that's bad, try attaching a floppy drive but don't put a disk in it. Windows Explorer will just randomly shit the bed
You don't even need to go that far, I think it does that with CD drives.
Microsoft has begun publicly rolling out its controversial Recall feature for Copilot+ PCs
I wonder if it'll be a massive disaster or if they've learned their lesson and actually got their 'jeets to sit down and refine it a bit instead of shitting it out ASAP so that they can show their investors they're doing an AI thing so that they'll give them AI money to do AI stuff for AI. Did I mention AI already?
From what I've read, they've done all they can to make it as good as possible (needs authentication repeatedly, data encrypted on rest, data is only per user,...) . The problem is that it being AI powered spyware combined with there being no goodwill towards Microsoft leaves it with a very low ceiling right off the bat, so "as good as possible" is still pretty fucking miserable.
 
  • Agree
Reactions: TooManyKittens
funny bonus: imagine grabbing all that data and then not being able to calculate folder/free size for easy display (got removed in 10 I think, maybe earlier).
I have never understood why explorer is so goddamned slow compared to ls -l and du -sh in Linux.
 
AI powered spyware
A double buzzword, nice. First of all, just because something is AI doesn't mean it's the antichrist. This so-called "AI" is just fancier math. All of the telemetry in Windows wasn't AI and that didn't change jackshit about what it did. There is no reason to bring it up as an important negative unless you have zero idea what those two letters are actually supposed to mean in this context.

Second of all, Windows, by default, has been keeping track of what you're doing locally for decades. I remember that the "recent files" list existed at least since Windows 2000, and Windows 10, by default, since 2015, kept track of all the programs you were running so that if you pressed Win+Tab you'd not only get the history of what you were opening, but also what you were using.

I do not recall (heh) anyone bitching about those two being evil spyware for all those years everyone was using Win10. Well, people were bitching that all of Win10 was spyware, but those same people now bitch that Win10 was the last best Windows and will run LTSC IoT for as long as they can, even though it's still the same spyware they've rebelled against back in 2015.

Here's the thing about Recall: it wasn't some Machiavellian plan to harvest data on everything you're doing on your computer for Microsoft to sell. Microsoft already had all kinds of telemetry baked into Win10 for years that did similar user behavior tracking, and Microsoft could silently add even more nefarious trackers in the backend. But only when it was this combination of Windows 11 (bad) and AI (bad) is when everyone started shitting their pants.

But if you were to look at that initial implementation of Recall, and pay attention to how the tech companies operate since 2020, it would become very clear that Recall was just an investor appeasement project. Now, the more "AI" a company is, the more money they get from investors. This was the main push behind Windows 11 becoming a thing, first it's to refresh the dated Win10 UI, second is to use that refresh to then add a bunch of "AI" stuff so that investors see this flashy new OS with flashy new "AI" tools and invest into MS stock.

Why was Recall so insecure that it was saving all of those screenshots as unencrypted PNGs and kept all of the analyzed data in an unencrypted database? It's because Microsoft wanted to push it out as soon as possible just to show their investors that they're doing an AI thing. They could've taken care of making it properly secure, since after all, they do have the entire Windows Hello framework that isn't as half-assed as Recall, but they didn't care about it. They didn't even care about all the sites you browse, they already know all that shit and that wasn't the main intention behind Recall. It was always investor fluffing.


The bottom line is this: Microsoft invested way too much in their CoPilot+ AI branding to completely back out of Recall, but my hope is that they've improved it in one major way: it is as mandatory as Hyper-V. Meaning that it's a toggle in OptionalFeatures.exe that once unchecked, is gone from the OS. And from what I'm seeing, that's probably what they did, so it will be a non-issue to me. When it's gone, it's gone, and that's all I care about.

This whole "Recall is malice on Microsoft's side to spy on you" argument is bogus. Microsoft was always able to spy on you to this extent. Why did no one make a fuss about it? The same fucking reason everyone is now bitching about 11, but X years down the line will defend 11 as the "last best Windows" while demonizing 12. Happened with every Windows release, and every time people act like they're not mouthbreathing retards with the memory span of a goldfish and that they are rebelling against Microsoft and they're totally gonna switch to Linux this time.

Seriously, the amount of parallels you could draw between the 2015 Windows 10 bitching and the current Windows 11 bitching juxtaposed with the current glazing of 10 is insane. People don't know jackshit about Windows, they just get outraged at news headlines with zero understanding of what's going on under the hood, then forget about it all once it's out of the news cycle. Same as it ever was.
 
Back