This entire project is a huge waste of time lmao #5015
Replies: 3 comments 9 replies
|
Pricing Tiers (Official OEM Channels)Microsoft determines the cost of Windows IoT Enterprise based on the capability of the processor installed in your device. Entry (Value/Low-end processors): Typically ranges from $30 to $45. the cost is based on your processor?? Seriously??? tell us your employed by microslop without telling us your employed by microslop |
|
*You're |
|
Calling me a "microslop shill" for actively pointing out Microsoft's own blatant apathy toward consumer licensing is certainly... a choice.... It's especially ironic considering the Windows build I'm advocating for is deliberately stripped of the slop. What went through your head typing out that response? I have to know. It couldn't have been anything intelligent. |
|
Your opinion was not asked for, nor was your post disparaging this repo and its creator. Since you are so knowledgeable in the world of micro$oft, what does each of the improvements provided my Mr. Titus break in the windows configuration? What do each of the improvements prevent from working, thus crippling the OS? Pour forth your vast expertise in micro$oft windows upon us feeble mortals and enrich our lives with your ever reaching knowledge. |
|
Go get em tiger ✌️ |
Aggressive debloat tools notoriously sever dependencies for the Microsoft Store, cripple the Windows Update pipeline, and break core background services that third-party applications actually rely on. It doesn't take "vast expertise" to recognize that forcefully ripping integrated components out of a proprietary OS is a fundamentally unstable way to run a daily driver. If you want an operating system that isn't bloated with telemetry out of the box, use LTSC or switch to Linux instead of pretending to be a cyber-rebel while actively corrupting your own registry. The amount of LARP in here is actually massively embarrassing. This is your legacy, Chris; a wholly illiterate user base that you've convinced you are God or something just because you can break an operating system. The irony of these people saying that I'm glazing when any one of them would promptly drop to their knees and orally pleasure you is astounding. Every single one of you is fighting for dear life defending the most unstable existing solution to a problem that never existed to begin with, yet I'm the one out of line. Make any of that make sense. Toodles. 🤡 |
|
Reading this made me chuckle really hard. That's all I'll say. Thanks for making my night. |
Awwwh you're so cute for thinking these things~! You're just glazing a greedy ass company(please mind my language) that wants to milk its customers. |
|
Acknowledging the technical reality that aggressive third-party PowerShell scripts break core Windows dependencies is not "glazing." It is basic systems administration. Microsoft absolutely is a profit-driven company that wants to milk its consumers—which is exactly why they herd everyone onto Windows Home and Pro to push telemetry, forced Edge prompts, and pre-installed bloatware. Recommending IoT LTSC is advocating for the exact version of the OS that natively prevents them from doing any of that. If you truly want to spite Microsoft and refuse to play their game, the logical solution is to install Linux. Running a frankensteined, script-mangled version of a proprietary consumer OS and pretending it is a rebellion is just a recipe for a corrupted registry on patch Tuesday. |
|
You are literally 13 years old. You don't know anything about anything. Literally every word that comes out of your mouth is roleplay and practice for adulthood. Shut the actual fuck up and get back to writing hello world in every language in existence instead of ever actually coding anything useful. 🤦 |
|
Been running my, in your words, 'frankensteined, script-mangled version of a proprietary consumer OS and pretending it is a rebellion' for years now and I think I'm doing fine? This is really funny, and William, the best thing you can do is ignore him and move on. The dude wants his engagement bait 😆 |
Uh oh!
There was an error while loading. Please reload this page.
You are trying to solve a problem that already has an official, stable solution. Aggressively stripping down consumer Windows builds to mimic a lightweight environment completely ignores the fact that Windows IoT Enterprise LTSC achieves this natively—without relying on unstable, third-party modifications.
Running "debloat" tools like this introduces severe and unnecessary points of failure; these scripts frequently break underlying dependencies, Windows Update functionality, and core system features—which can leave users with a fragmented, unpredictable setup. Promoting this to an audience where many lack the technical depth to troubleshoot a corrupt registry or a broken install is concerning; it puts users' daily-driver machines at risk for minimal tangible benefit.
Someone with a strong technical background knows the dangers inherent in heavily modifying an operating system with automated scripts. Presenting a tool like this as the definitive fix—rather than educating the community on how to acquire and install a naturally bloat-free release like LTSC—seems like a major oversight.
If the goal is genuinely a clean, efficient computing experience, the community deserves to be pointed toward stable, native solutions rather than a script-based band-aid that can actively compromise system reliability over time.
All reactions