How To
See other How To Articles
Title: Windows 10 = Maze of Slow, Intrusive Garbage. Need Help in Un-Bloating and Speeding Up
Source:
Me
URL Source: [None]
Published: Jan 2, 2018
Author: Me
Post Date: 2018-01-02 11:15:46 by Liberator
Keywords: Windows 10, Intrusive, Garbage
Views: 24387
Comments: 92
To you Computer tech-heads, just got a Win 10 HP piece of crap that is running in quicksand. It's not a brand new machine... Firefox is running, but preventing the LF page from opening without permission. Took forever to load youtube as well as all other pages. Have loaded CCleaner and Avast. There seems to be a mountain of bloatware and intrusive programs running in the background. I'm a Win 7 guy, so this is all Greek to me. It's like a selfish Monster has hijacked the machine. The Settings are nothing like the simplicity of Win 7. Very convoluted. How do I take back this machine? And stop the intrusive stuff and updates? Any constructive suggestions are appreciated. Thanks...
Post Comment Private Reply Ignore Thread
Top • Page Up • Full Thread • Page Down • Bottom/Latest
Begin Trace Mode for Comment # 18.
#12. To: Liberator (#0)
A decent downgrade guide, covers the issues pretty well. How to Downgrade Preinstalled or Upgraded Windows 10 Installation to Windows 7/8.1
How would Liberator downgrade when he bought a used computer with Win-doze 10 pre-installed? There is no traceability to a license agreement with Microsoft and therefore no warranty per your dumb ass suggestion.
He only needs an existing Win7 Pro license to install an old version. Since he is mourning the loss of his old OS, he has a good chance of already owning a Win7 that he could install on this Win10 Hellmachine. I never suggested he had any warranty. You made that up. Dumb ass.
With the Win7 PRO that I know of (fully licensed of course) from the original install, it will read the CPU registration and lock to the machine. Win 7 is not transferable to other boxes is what I am suggesting. You are simplifying the issues into silliness.
You get stupider by the day. Win7 and others never lock to a CPU. The OEM versions of newer versions of Windows will lock to a particular motherboard and its components. For these, you must stay with the same computer or at least a motherboard with the same components. However, you can install different CPUs with no problem. For OEM versions, the OS is locked to the first computer (motherboard configuration) you install it on and you cannot upgrade previous versions of Windows with it. If you have a full licensed copy of Win7, you can install it where you like and it can upgrade old versions of Windows (and it has direct support from Microsoft, not the OEM). It does "lock" to a particular configuration of motherboard/RAM/drives/video cards during the registration process with Microsoft. This can temporarily inhibit any component changes, even while still using a computer with the same CPU/mobo/video card. Microsoft will accept new configurations but it takes a little more fuss. In no case is the OS ever locked to a particular CPU or hardware configuration or motherboard. You don't seem to know much about Windows OEM vs. full versions. You shouldn't be offering advice to anyone. Liberator might be better off just trying to clean up his Win10 machine to make it usable. The presence of creepy bloated spyware is discouraging but with some effort, he should be able to get a clean Win10. And keep in mind that this Win7-Forever thing is going to turn out just like the WinXP-Forever did. When the manufacturers of the components and Microsoft stop building drivers for new components and motherboards for an old OS like WinXP or Win7, that OS's days are numbered. Microsoft ended all non-subscribed (paid corporate) support for Win7 in January 2015, two years ago. Even the paid corporate bigwigs will receive support only through January of 2020, only two years from now. And even the subscribed support corporate types get only security patches and minor updates. Microsoft is not producing any new device driver support for these corporate machines so they lack the ability to use many newer components appearing on the market due to lack of drivers. You may want to reconsider making much effort or incurring expense to make a Win10 HP into a Win7 HP with only two years left in the Win7 support cycle. I know this isn't happy advice for you to hear but you need to be coldblooded about it and recognize the reality of what happens when Microsoft sunsets and then drops support for one of its OSes. Ignore buckwheat's advice.
#19. To: All, buckwheat, Liberator (#18)
A bit of fresh news on the issue of ongoing OS support from Slashdot today:
Top • Page Up • Full Thread • Page Down • Bottom/Latest
#13. To: Tooconservative, Liberator (#12)
#15. To: buckeroo (#13)
How would Liberator downgrade when he bought a used computer with Win-doze 10 pre-installed? There is no traceability to a license agreement with Microsoft and therefore no warranty per your dumb ass suggestion.
#17. To: Tooconservative (#15)
He only needs an existing Win7 Pro license to install an old version. Since he is mourning the loss of his old OS, he has a good chance of already owning a Win7 that he could install on this Win10 Hellmachine.
#18. To: buckeroo, Liberator (#17)
With the Win7 PRO that I know of (fully licensed of course) from the original install, it will read the CPU registration and lock to the machine. Win 7 is not transferable to other boxes is what I am suggesting.
Replies to Comment # 18.
So the chances are that an HP machine a few years old will be vulnerable to these problems and the only fix is to slow down its performance with a new kernel (OS core functions). And no one is likely to go back and fix those issues properly for Win7. The corporates will stick with their Win7 through 2020 but apply stricter security inhouse to those machines.
According to The Register, "A fundamental design flaw in Intel's processor chips has forced a significant redesign of the Linux and Windows kernels to defang the chip-level security bug." From the report:
The report goes on to share some details of the flaw that have surfaced. "It is understood the bug is present in modern Intel processors produced in the past decade," reports The Register. "It allows normal user programs -- from database applications to JavaScript in web browsers -- to discern to some extent the contents of protected kernel memory. The fix is to separate the kernel's memory completely from user processes using what's called Kernel Page Table Isolation, or KPTI." Programmers are scrambling to overhaul the open-source Linux kernel's virtual memory system. Meanwhile, Microsoft is expected to publicly introduce the necessary changes to its Windows operating system in this month's Patch Tuesday: these changes were seeded to beta testers running fast-ring Windows Insider builds in November and December. Crucially, these updates to both Linux and Windows will incur a performance hit on Intel products. The effects are still being benchmarked, however we're looking at a ballpark figure of five to 30 per cent slow down, depending on the task and the processor model. More recent Intel chips have features -- specifically, PCID -- to reduce the performance hit. Similar operating systems, such as Apple's 64-bit macOS, will also need to be updated -- the flaw is in the Intel x86 hardware, and it appears a microcode update can't address it. It has to be fixed in software at the OS level, or buy a new processor without the design blunder. Details of the vulnerability within Intel's silicon are under wraps: an embargo on the specifics is due to lift early this month, perhaps in time for Microsoft's Patch Tuesday next week. Indeed, patches for the Linux kernel are available for all to see but comments in the source code have been redacted to obfuscate the issue.
#20. To: Tooconservative, buckeroo (#18)
You get stupider by the day.
Yep, and every time I break wind from the
beans the sound it makes is: "Buckeroo."
End Trace Mode for Comment # 18.
[Home] [Headlines] [Latest Articles] [Latest Comments] [Post] [Mail] [Sign-in] [Setup] [Help] [Register]