• Getting ready (or not) for Windows 10

    Home » Forums » Newsletter and Homepage topics » Getting ready (or not) for Windows 10

    Author
    Topic
    #505710

    Patch Watch

    Getting ready (or not) for Windows 10

    By Susan Bradley

    There’s strong evidence that some systems are being force-fed the Windows 10 upgrade — and it’s breaking customer trust.

    Plus, more on the issue of extremely slow Windows Update scanning on Win7 systems.


    The full text of this column is posted at windowssecrets.com/patch-watch/getting-ready-or-not-for-windows-10/ (opens in a new window/tab).

    Columnists typically cannot reply to comments here, but do incorporate the best tips into future columns.

    Viewing 11 reply threads
    Author
    Replies
    • #1565312

      Real evidence of forced Windows 10 upgrades

      I thought you were going to give us some.

      … at this time I’m simply waiting for the system to reboot.
      I’ll see if, somewhere along the way, I’m asked to accept the official Win10 EULA — and what happens if I decline it.

      Please remember to let us know?

      • #1565315

        “For now, the best workaround is to ensure that Windows Update is set to “Download updates but let me choose whether to install them.””

        Unfortunately, using this setting is the same as leaving updates on Automatic for most Users. What happens is all the checked updates get downloaded in the background (including the checked optional update “Upgrade to Win 10”). An “!” appears in the Start/Shutdown button, and the updates get installed on the next shutdown/reboot. The average user (in my support experience) does not use Control Panel/Windows Update, does not know anything about settings, does not uncheck/recheck updates, does not know that options exist and can be changed. So the effect is – the User shuts down the computer and the updates get installed the same as if on Automatic.

        The only safe choice is “Search for updates but let me decide whether to download and install them.” But now we’ve thrown the average User another curve – they become responsible for the updates they know nothing about.

        Microsoft has intentionally trained the average User to take the defaults in ignorance. And that is how they can get away with the evil they are doing.

    • #1565335

      Susan,
      I just logged in to thank you for the most useful column I’ve run across in ages. I have an older Win7 PC that has been used only rarely since I switched the home mostly to Apple products. Its hardware is easily good enough to run Windows 10, so I have been intending to boot it and update it for that upgrade. However, I absolutely dreaded the task of installing all the updates from the last 18 months. I think that your tips will greatly simplify that task. Whew!
      My question involves the recently-released Microsoft’s recently-released “cumulative rollup pack.” I’ve downloaded that, but I’ve yet to run it. At this point, would you advise just doing that, OR should I first manually install the five updates listed on the Dalai page that you referenced?

      Thanks

    • #1565338

      A very informative article. Thank you. Now I know why a friend’s PC was updating without permission. I, too, thought she had overlooked something.

      Yes, the “Get Windows 10” app is supposed to check for compatibility, but it’s far from perfect…

      Depends on your definition of “far.” If you mean light years, I agree. The compatibility check is nowhere near as comprehensive or accurate as the previous Windows Upgrade Advisors were and I made the mistake of trusting it. My advice is to check your hardware, drivers, and software before accepting Win 10, although it seems that may be harder to do now.

      • #1565352

        I have a question for Susan: My wife and I moved back to the U.S. from Switzerland last year. I had purchased my computer there several years before. It is a desktop with Win 7 Professional (American English language) pre-loaded. After unpacking our household goods here in the states, I simply swapped out my computer’s 220 volt power supply for a 110 volt version, and everything has continued to function perfectly. (By the way, I have Windows Update set to notify me, and I determine which upgrades to allow.) Now, after reading this article, I am wondering what the situation is in Europe regarding forced upgrades. More important, how does Microsoft view my system? My IP address obviously identifies me as a user living in the U.S., but is my system still registered with Microsoft as a European version of Windows 7, and will they leave me alone with this forced upgrade nonesense?

        • #1565399

          but is my system still registered with Microsoft as a European version of Windows 7, and will they leave me alone with this forced upgrade nonesense?

          In a word, no. European users are upgraded in the same way.

          cheers, Paul

    • #1565365

      In the article you mention both GWX Control Panel and Never 10 and in () it has site, but they are not linked. Also, Never 10 DOES check for the folder and gives you the opportunity to remove the Win10 upgrade folder.

    • #1565368

      I have been having issues with kb3163207. A few of my clients with Win 7 or 8 have had it fail. When they restart, it tells them that t is installing the update, after a while it says something like “update failed, undoing update” and sits there for awhile uninstalling the update before the machine finally reboots. Then a few days later they got the same thing again. Is there any known issue that might be causing this and this an important update?

    • #1565370

      Hi Susan,

      As far as controlling auto-updates, as long as one keeps an eye out for that auto-checked Optional item in the WU list of items, one can always uncheck it before getting the Important/Critical ones.

      However, I decided to bite the bullet the other day and allow the Win10 upgrade to my Win7 main household computer. It got the point of the first reboot, and then said it was “Installing features … etc”, and it only got as far as 32%, then hung forever. I had to hold down the power switch until it hard-powered off. Upon re-start it backed out the upgrade and I was left where I started with my Win7 system.

      I tried everything I could find on this issue, i.e. switch off anti-virus before kicking off the upgrade, disconnect any and all USB connected devices, run a sfc / scannow, etc., but each time I try it still only gores as far as that 32% before hanging indefinitely. I have now created a bootable DVD using the Media Creation tool, but when the computer is booted using this disk, the only option it gave me was “Install”. I was reluctant to click the button as I wasn’t sure whether this was going to do a clean install (and then I’d lose all my apps, files, etc.) or give me the option of an upgrade. Note that I do have both a Full Disk Image backup and a Files backup using the ToDo EaseUS s/w.

      Any advice/assistance would be greatly appreciated, Thanks.

    • #1565371

      On Auto Win10 updates, I have to wonder if Microsoft is using some past action as “permission”. For example, if someone long ago “reserved” Win10 when requested, then later got concerns and didn’t go ahead with the process. Is MS taking that reservation as approval? I have to wonder if they have some fall-back excuse like that.

      But I fully agree. Making major changes to someones computer is something that should have explicit current permission.

      I had no trouble controlling when I upgraded my machines but discovered by accident that a friends laptop had a scheduled update they where not aware of initiating. If they hadn’t happen to open it for me then they would not have been aware it was about to take place and likely it would have happened the next time they booted it. ie: you have to boot the computer prior to the scheduled time to get the scheduled notice. People who use their computers only ever few days may not get a notice.

    • #1565377

      Patch Watch

      Getting ready (or not) for Windows 10

      By Susan Bradley

      There’s strong evidence that some systems are being force-fed the Windows 10 upgrade — and it’s breaking customer trust.

      Plus, more on the issue of extremely slow Windows Update scanning on Win7 systems.


      The full text of this column is posted at windowssecrets.com/patch-watch/getting-ready-or-not-for-windows-10/ (opens in a new window/tab).

      Columnists typically cannot reply to comments here, but do incorporate the best tips into future columns.

      Just wondering a couple of things:

      1. is there any way to tell, by KB number (or something else) what the update is about? (I noticed that certain numbers, 311xxxx, I think, seemed to apply to MS Office updates…) and
      2. is there any way to list the KB numbers in numeric order, so that one can find the KB item more easily? Now one has to closely read the list, because the list is not in numeric order, and it’s a frustration, to say the least, and
      3. at some point in the near past you said to skip KB 3139923. I don’t see it in the list currently, so I don’t know what to do with it. This is not the first time that an item was held and then not followed-up on. I know it would help me (and I must assume, others) more if you made sure that any update you suggested as a HOLD was closely followed until it was safe to install and then take it off the list, altogether.

      Many thanks for all of your hard work, Susan……

      • #1565382

        Just wondering a couple of things:

        1. is there any way to tell, by KB number (or something else) what the update is about? (I noticed that certain numbers, 311xxxx, I think, seemed to apply to MS Office updates…) and
        2. is there any way to list the KB numbers in numeric order, so that one can find the KB item more easily? Now one has to closely read the list, because the list is not in numeric order, and it’s a frustration, to say the least, and
        3. at some point in the near past you said to skip KB 3139923. I don’t see it in the list currently, so I don’t know what to do with it. This is not the first time that an item was held and then not followed-up on. I know it would help me (and I must assume, others) more if you made sure that any update you suggested as a HOLD was closely followed until it was safe to install and then take it off the list, altogether.

        Many thanks for all of your hard work, Susan……

        As to KB 3139923, this is from March and April patchwatch:

        March patchwatch
        Do I really need this nonsecurity fix?
        Microsoft released a batch of updates a few days after March’s regular Patch Tuesday — and they’ve mostly left me scratching my head. Many make sense only if you have a Win7 virtual machine hosted in Azure, if you’re managing a network, or you’re running into various other problems fixed by the updates.
        Most of us can skip these updates. But here’s the quick summary:
        Windows 7
        3139923 – MSI repair fails after installing MS14-049
         3318901 – Access to Internet fails due to overwritten proxy settings
         3137061 – Azure VMs don’t recover after network outage

        April patchwatch
        Office updates post release issues
        In the first April Patch Watch column, I noted problems with KB 3114566 (MS16-039), a security fix for Office 2010 SP2. But there are reports that other April Office updates had issues, too — in particular KB 3114888 for Excel 2010 and KB 3114993 for Word 2010 (MS16-042).
        After installing those patches, launching Office apps might pop up the error “The Windows installer service could not be accessed” — if July 2015 security update KB 3072630 isn’t already installed. (I didn’t see this Office 2010 error on my systems.)
        Note that a nonsecurity Office patch, KB 3114996, might show up in Windows Update in the important category. According to its notes, it too might cause Office to pop up the aforementioned error message if KB 3072630 isn’t installed.
        An alternative for fixing this issue is to uninstall update KB 3139923, a nonsecurity hotfix that was released in March. With that patch removed, Office should function normally again.
        What to do: Install KB 3114566 along with KB 3114888 and KB 3114993 as soon as possible, but look for unwanted side effects in Office.

        Don't take yourself so seriously, no one else does 🙂
        All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • #1565415

      “Plus, more on the issue of extremely slow Windows Update scanning on Win7 systems”

      With Windows 8.1 selected updates download and install immediately once selected.
      The checking of update validity and sequence can only take splits of a second.

      When W7 SP1 after all the recommended updates and service stopping etc takes 4 hours or more and then does not find all important or optional downloads the proposition that W7 SP1 needs a lot of pre-checking does not seem at all plausible. Microsoft have messed this up intentionally or otherwise. After 3 days I have managed to download important updates by setting on automatic but unimportant downloads do not download even when it says they are ready to download. I cannot install any updates manually. One of my W7 Thinkpads has now got the W10 upgrade into the important update lists so I cannot use automatic, or W10 installs.

      We really need a W7 SP2 to sort this whole mess out or people will just abandon trying to keep their security up to date.
      Alternatively what users may prefer is a Chromebook system where Microsoft provide an up to date working OS at each boot up.

      • #1565450

        Regarding this quote from the article:

        “This new process is a mixed blessing: On one hand, we’ll no longer have to manage numerous patches; on the other hand, there’ll be no way to bypass a specific problematic patch without skipping all patches in the rollup update.”

        And there apparently won’t be any way to bypass a push-Win10 update in the rollup without foregoing the rest, either. I’ve studiously hidden any and all push-Win10 updates thus far and so seem to have avoided the problems with the increasingly aggressive forced upgrades. Now Microsoft seems to be moving towards a Windows 10 bundled-update methodology for the older versions as well: Take it or leave it.

      • #1565464

        ”Plus, more on the issue of extremely slow Windows Update scanning on Win7 systems”

        IIRC, MS pulled the same stunt with a previous version of the OS, choking the update process by reducing the available bandwidth so as to encourage people to believe there was something wrong with their system that an upgrade might fix… MS eventually restored the available bandwidth.

        Cheers,
        Paul Edstein
        [Fmr MS MVP - Word]

    • #1565455

      Now Microsoft seems to be moving towards a Windows 10 bundled-update methodology for the older versions as well: Take it or leave it.

      That does hint at another aggressive step in MS’s quest to get rid of W7/8/8.1 in favor of upping the W10 upgrade numbers. Unfortunately many will forgo the updates since the trust in MS is pretty much shot now.
      Just have to wait and see.

      Don't take yourself so seriously, no one else does 🙂
      All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

    • #1566374

      Susan’s article says “There have been several Windows Update Client patches that should have helped solve the slow update scans. KB 3102810 (Nov. 3, 2015) was followed by March’s KB 3138612. Ensure that you have both installed; and check out a Dalai site that lists other patches that can help improve update-scanning speed.”

      The Dalai website she linked to says “The following update is (most likely) not required if the Windows Update Client of December 2015 or later is already installed: KB3102810, reduces Update Agent’s CPU load.”

      Could Susan clarify if this update is really needed, given what the Dalai website says?

      • #1566380

        Susan’s article says “There have been several Windows Update Client patches that should have helped solve the slow update scans. KB 3102810 (Nov. 3, 2015) was followed by March’s KB 3138612. Ensure that you have both installed; and check out a Dalai site that lists other patches that can help improve update-scanning speed.”

        The Dalai website she linked to says “The following update is (most likely) not required if the Windows Update Client of December 2015 or later is already installed: KB3102810, reduces Update Agent’s CPU load.”

        Could Susan clarify if this update is really needed, given what the Dalai website says?

        The Dalai site is not definitive. They are hedging their bet. Just install them both and don’t worry about it. Install the older one first.

        --Joe

        • #1566401

          The Dalai site is not definitive. They are hedging their bet. Just install them both and don’t worry about it. Install the older one first.

          KB3102810 is currently not installed on my computer, but KB3138612 is. The concern I have is when I run Windows Update, KB3102810 doesn’t show up as Important, Recommended, or Optional. Since it doesn’t show up at all in Windows Update, that would seem to indicate it doesn’t belong on my computer.

          • #1566403

            KB3102810 is currently not installed on my computer, but KB3138612 is. The concern I have is when I run Windows Update, KB3102810 doesn’t show up as Important, Recommended, or Optional. Since it doesn’t show up at all in Windows Update, that would seem to indicate it doesn’t belong on my computer.

            If it doesn’t show up it is not needed on your system. Don’t worry about it.

            --Joe

            • #1566738

              If it doesn’t show up it is not needed on your system. Don’t worry about it.

              Thanks, I’ll go with that. “If it’s not broken, don’t fix it” seems to apply here.

      • #1566982

        Susan’s article says “There have been several Windows Update Client patches that should have helped solve the slow update scans. KB 3102810 (Nov. 3, 2015) was followed by March’s KB 3138612. Ensure that you have both installed; and check out a Dalai site that lists other patches that can help improve update-scanning speed.”

        The Dalai website she linked to says “The following update is (most likely) not required if the Windows Update Client of December 2015 or later is already installed: KB3102810, reduces Update Agent’s CPU load.”

        Could Susan clarify if this update is really needed, given what the Dalai website says?

        The KB3102810 & KB3138612 updates for Win7 SP1 did little or nothing to improve Windows Update scans.

        What DID work was to install the newest WIN32K.SYS security updates KB3145739 and KB3153199, which Susan was not aware of (but Woody was aware though – some readers contacted him about manually downloading & installing the newest win32k.sys updates like KB3145739 and KB3153199 to actually speed up WU scans).

        Using outdated versions of the WIN32K.SYS file on Win7 SP1 seem to cause very long Windows Update scans. So to speed up Windows Update scans bigtime on Windows 7 SP1, try installing the very latest WIN32K.SYS security updates, reboot and then try running Windows Update again.

        • #1567221

          Well, this was a good thread, and the entry about Win32k.sys was most interesting. I took a look at my own Win 7 Pro SP1, which seems to be working better lately in regard to installing patches.
          I discovered that the following are already installed:
          KB3102810
          KB3138612
          KB3145739
          KB3153199
          and then I was curious about the date on WIN32K.SYS

          so I was very surprised to see that my system has 122 files named WIN32K.SYS; when I sort them by date modified, the oldest is 07/13/2009, and the newest is from 04/09/2016.
          They are all in directories with names like
          c:windowswinsxsamd64_microsoft-windows-win32k_31bf3856ade35_6.1.7681.xxxxxxxxx

          The part before xxxxxxx is the same for all the files, the xxxxxx part is different.

          These are all system files, so I would be hesitant to delete any of them, but I cannot understand why there are so many versions.

          Can anyone shed light on this situation? Thank you.

          • #1567223

            Well, this was a good thread, and the entry about Win32k.sys was most interesting. I took a look at my own Win 7 Pro SP1, which seems to be working better lately in regard to installing patches.
            I discovered that the following are already installed:
            KB3102810
            KB3138612
            KB3145739
            KB3153199
            and then I was curious about the date on WIN32K.SYS

            so I was very surprised to see that my system has 122 files named WIN32K.SYS; when I sort them by date modified, the oldest is 07/13/2009, and the newest is from 04/09/2016.
            They are all in directories with names like
            c:windowswinsxsamd64_microsoft-windows-win32k_31bf3856ade35_6.1.7681.xxxxxxxxx

            The part before xxxxxxx is the same for all the files, the xxxxxx part is different.

            These are all system files, so I would be hesitant to delete any of them, but I cannot understand why there are so many versions.

            Can anyone shed light on this situation? Thank you.

            These are the backup files for patches in case you want to uninstall a patch. If your system is running well, you may wish to delete these backup files. Open Control Panel, type “disk cleanup” in the sesrch box, click on “free up disk space by deleting unnecessary files”, let it run (you may have to click on the Windows partition C: to get it to run), then click on the “clean up system files” button (you may have to select the partition again). Then select the categories of files to delete making sure that Windows Update is selected. Confirm you want to delete the files.

            --Joe

    • #1570215

      Yes, Miss Bradley, you were naive to assume that Microsoft was noble.

      You can be forgiven. It is much like strange little religions; the indoctrinated will believe anything.

      Microsoft is attempting to seduce or bully everyone into accepting Windows 10.

      Now that your eyes are open, note that there have also been reports of Microsoft updates resetting user-selected settings.

      Microsoft is also attempting to seduce or bully everyone into accepting cloud-based MS Office applications with all of our data stored on Microsoft servers.

      Microsoft will succeed in these attempts.

      At some stage, one might reasonably predict that MiniSquashed will introduce a new “improved” MS Office file format that can not be read by older Office versions, such as are often used by pre-Windows-10 machines, or that require MS cloud-based applications or services.

      The first step in this march to conquer the computer world was more subtle and came years ago when MS ceased to provide documentation with its Office applications and required users to go to the MS website to get information. This was subtle enough that MS may actually have had innocent intentions; it is unlikely that MS was smart enough to have forseen what would follow.

      Microsoft would be well advised to tread lightly. Long before MiniSquashed, IBM tried to conquer the computer world using similarly ungentlemanly tactics. The customer base took advantage of technological developments to take IBM to task by switching, en mass, to microprocessors (hence, the rise of MiniSquashed). Today, MiniSquashed may wake up one morning and find everyone using Unix and Libre Office.

    Viewing 11 reply threads
    Reply To: Getting ready (or not) for Windows 10

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: