[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re: Win10 upgrade news
- Subject: Re: Win10 upgrade news
- From: J R FOX jr_fox@xxxxxxxx
- Date: Fri, 27 May 2016 00:00:35 +0000 (UTC)
I had installed v. 1720 of the Control Panel to a few computers. Now I see that it was up to at least v. 1740. Not sure what is in the changelog, but it may be time to update this protection.
Jordan
From: Michael Norman
To: xywrite@xxxxxxxx
Sent: Thursday, May 26, 2016 12:56 PM
Subject: RE: Win10 upgrade news
Jordan,
You’re right. My WIN7 machine is six+years old at this point, and I spend at least three-five hours a week chasing after this anomaly or that. BTW, turns out that GWX Control Panel and Never10 don’t get all the W10 updates M$ sends, tsunami-like, our way. Take a look here:
Found seven of the updates on his list.
Michael
From: xywrite-bounce@xxxxxxxx [mailto:xywrite-bounce@xxxxxxxx] On Behalf Of J R FOX
Sent: Thursday, May 26, 2016 2:46 PM
To: xywrite@xxxxxxxx
Subject: Re: Win10 upgrade news
I think there are just inherent defects in most editions of Windows to date, some more serious than others, and some more luck of the draw depending on your particular history and configuration. I help out an XP user who has recurrent USB port / device recognition problems. The latest on that seems to be that the system keeps losing track of drive letter assignments. If that proves to be correct, it will be more on-the-spot fixable, but a continuing annoyance. 64-bit W7 can't reliably copy large files on its own without corruption, necessitating use of a third-party utility like TeraCopy. I have a couple W7 systems where Windows Update has ceased working, and just hangs interminably. There is a nice series of fix-it videos for this on YT, but so far none of them has solved this problem for me. I suppose I may have to try to uninstall / re-install Win Update. There even seems to be a KB expressly for this, but I would probably need to download it separately and try to apply it manually. (One incidentally good thing about this is that if no updates can get processed, all these sneaky, underhanded attempts by MS to slide W10 under the door can't get in either !)
Your lengthy shutdowns seem like another such anomaly -- one I think I've seen before -- which may indicate that something is munged in the OS on that computer.
Thanks, Daniel.
I ran both Never10 and GWX Control Panel, both of which were easy to use and
seemed effective. As it turned out, I'd managed to avoid letting M$ install
any W10 components on my W7/64 Pro machine, which, in turn, suggested that
my long shut-downs had nothing to do with a lurking W10 process. I've tried
every protocol I could find - disabling services and programs with msconfig,
sweeping for malware. There's seems to be a lot of misinformation on this
problem (several normally reliable sites suggesting registry edits from on
XP -- keys that do not exist in Win7. "Stopping services" still takes 31
seconds. I think my next stop is Windows Performance Toolkit to try to find
out which process is taking so long. At all events, thanks again for the W10
blocking suggestions.
Michael
>-----Original Message-----
>From: mailto:xywrite-bounce@xxxxxxxx [mailto:mailto:xywrite-bounce@xxxxxxxx] On
Behalf
>Of Daniel Say
>Sent: Tuesday, May 24, 2016 7:54 PM
>To: xywrite@xxxxxxxx
>Subject: Re: Win10 upgrade news