I see it all over the forums. "Windows messed up my partition.". "Windows fragmented my drives.". Windows did this and that and blah blah blah. Everything is messed up because of Windows. Look, here's the thing. No. Ever stop to think that Windows isn't at fault? Maybe it turns out you're either stupid, or just made a mistake, and you're looking to blame the easiest thing other than yourself? I've seen about five posts in the past week complaining about WinOS fragmenting drives. Holy crap, are you that ignorant? 1: Transferring multiple, large sets of data at once is going to be an issue; ESPECIALLY if it's around hundreds of gigabytes of data in all. It's not the OS causing the problem. The OS is doing what it was coded to do. You're the one being idiotic, pushing it to do something you very well know ISN'T in its job description, and then blaming it for doing a poor job. 2: Fragmentation? Are you kidding me? Most of the time Windows reports high fragmentation, it's VERY inaccurate. Some tests have shown most fragmentation estimates to be about 35% LESS than the number given. And on top of that, you would have to have done a really poor job with data management to fragment a drive so bad, that it hits the read/write accessibility like a truck. Windows isn't to blame. You are. Yes, Windows isn't very good at shit like this. The point is that YOU KNOW IT ISN'T and then blame the operating system AFTER YOU DID IT. YOU DID IT, not Windows.
So... Don't blame an OS for its deficiencies? That's what it sounds like.
No, blame the OS for the deficiencies, sure. But if you are aware of the deficiency, and then do it anyway... Blaming the OS for it is just stupid. It's one thing not to know. It's another thing to know there's a problem, and then throw everything in the world at it, and then be like, "Wow! You messed up!"
A good tradesman never blames his tools.
Good man!
Windows is actually quite nice in its installation process, and even using multiple OS's is not that difficult if people configure their boot loaders correctly.
But if you are a windows 10 user and concerned somewhat about its background processes then there are a few guides and videos available to switch off anything that you may consider to be intrusive in your windows experience.
The question of meta data being sent without peoples knowledge and generally reporting user behavior to microsoft is not something that you cannot control, just as they switch on this stuff you have a option to switch it off.
Oh and windows power-shell is really good too. So people who like command line based use within their OS should have no problems in transition when working with either windows or linux
Every Linux Shrill is Triggered Right now.
At this point, I've got my popcorn... Now I wait.
I came here expecting "Microsoft isn't to blame for the Windows 10 security bullshit, you people are for adopting it".
I am disappointed. That being said, I do have a bone to pick.
Windows 7, when first installed, will apparently do something to boot records in any drive installed, during the installation, that requires ALL of the drives to be installed in order for the OS to work.
Example: My moms work PC that I built for her.
OS installed on SSD, HDD for storage. She retired, having barely even touched the SSD's 128g (it still had around 70g free) I decided to take the HDD out and put it in my PC because I needed the space.
But NO, Windows 7 for some reason, requires the drive that the OS ISN'T FREAKING INSTALLED ON, to be present in order for the system to boot.
Should I have known this? Probably (I should have known that when you install Windows, you only have 1 drive installed physically. Lesson learned.). But that doesn't excuse MS for this blatantly idiotic design choice. It serves no actual fucking purpose, to my knowledge. Unless Windows is for some reason installing part of the OS on the storage drive and not the main OS drive, which would just be asinine.
Seriously, tell me why this is apparently a thing?
"The definition of insanity is doing the same thing over and over and expecting a different result."
Even worse is when someone asks you to "fix" their computer, you look at it, see how messed up they are using it and do what you can. A month later that same person, that you told to stop watching PopcornTime and porn on his wife's laptop, says "You messed up my computer."
NO. I fixed it. It was fixed when I left. Obviously you broke it. AGAIN.
Next time anyone comes to me for help I'm saying "Call Geek Squad."
I haven't had any problems from watching porn, for a few years now.
Then again, I stopped torrenting it and starting streaming it. Using adblock and a subscription based Anti-Virus program. It's blocked multiple threats, and prevented any harm.
Meh.
See! That's the thing! That's Windows (7 in this case) not being very practical. You didn't know, and even then, you acknowledge that it'd be a bad idea to do it again. But I see no point in arguments where people in turn, blame the Operating system after the fact.
That should be with any system. how many new people on the forum you know of that complained a year or so back blaming Microsoft for Linux deleting their shit after they installed it on their second hard drive. damn near all of them.
if anything I've learned is if you are using an HDD make a separate partition STRICTLY for the OS.. it saves you the headache later when you want to jump to an SSD.
I'd honestly be willing to throw money into starting a tech solutions company that does nothing but answer phones and say "Have you tried calling Geek Squad?".
I feel bad for those few poor souls who work at geeksquad and actually know what they're doing. I would have a stroke after fixing so many technology-inept people's broken ass laptops.
As have I, but it's still a fucking stupid thing to have happen. If the OS drive is there, and all the files for said OS are on that drive, it should boot regardless. At worst, give a popup at the start saying "A drive is missing or damaged, some files and or programs may be missing or not work properly".
This would make sense, in case the storage drive failed. Instead, if the storage drive fails, it tanks your entire system with it.
@Schyken I should have known, because it's considered a "best general practice" to only have one drive installed when you install the OS.
But that doesn't excuse a MULTI-BILLION DOLLAR CORPORATION from such an obvious fucking design flaw. For aforementioned reasons.
You should see the shit we deal with.
I fix laptops for a company that provides IT services for local school systems. We service 30k+ chromebooks and notebooks.
Some of them, have fucking GUM jammed into the heatsinks. Some are left in toilets, some look like the kids enganged in melee combat with their chromebooks.
On average, I fix about 20 a day. More if we do chromebooks, less if we do notebooks. About 20 if we do a mix.
No OS is perfect.
Look at GNU / Linux, it's so fucking fragmented with thousands of distros in existance. though the package managers are to blame for that. but it's annoying. why do you think Android is so successful? there's only one. OEMS just add their bloatware to it.
If you really have issues with dual OS with windows 10 and linux etc booting then just buy a $30 hotswap drive, 2 SSD's install windows on 1 for all your triple AAA gaming and MS Office needs and linux on the other 'just cos its fricken linux why not!'
And then switch out either drive with your hot swap based on what you need it for.
As for looking after windows there are many available tools to deal with defrag, optimization, registry cleanups, safe un-installers, and security apps. I do not think I have ever owned a computer since Windows 98 that had significant issues with BSOD, crashing or general bloatware..
Maintenance is your responsibility it is like how you shower every day to keep yourself clean, the same goes for looking after your OS, you gotta maintain it to get the best out of it.
To any client that bitches to me about Windows being crappy, I install linux on their machine, if they bitch at me about that, I put windows back on charge them a great deal of money and ask them 'Now what have we learned from this experience'? By that time most of them realize its their own error thats the problem not the OS.