Quote:
Originally Posted by Hitch
<expletives omitted>
WINDOWS10!!!!
</rant>
|
What's
your gripe?
I have three Windows10 machines here. My SO's laptop, a travel laptop, and my desktop.
The two laptops behave fine. The desktop has been "Windows 10 BSODs - collect the whole set", and I have been.
The most recent issue was the machine popping up a BSOD window talking about REGISTRY_ERROR if left unused for 4+ minutes. This is apparently a Known Problem related to background maintenance, but suggested fixes found online didn't cure the problem here.
It currently has a new quirk. A Windows svchost.exe processing is pegging one core of the CPU. That svchost instance handles Windows Update and a few other things. I have no idea what it's doing, save that it doesn't appear to be doing harm, It's simply consuming resources.
The backhanded good part is that at least the machine doesn't BSOD with REGISTRY_ERROR, because it's
not sitting idle, but I'm not sure I'd call that a "fix."
The real fix is likely doing a Windows Refresh, which will restore Win10 to default status while preserving user files, and will place a list of what it removed on the desktop. Most stuff I care about keeping is on a different drive and wouldn't be touched in any case, so it would mostly be an investment of time to do it and then restore my desired setup.
Meanwhile, the desktop dual-boots Win10 and Ubuntu Linux, and I can boot into Linux and do most stuff from it.
But the process of migrating to Win10 has been "Oh, no! Not another learning experience!"
<edit>And while was was posting the above and continuing on, I got another BSOD: BAD_POOL_HEADER. I am so thrilled.</edit>
______
Dennis