• Ian Gerald

    Ian Gerald

    @mailiang

    Viewing 11 replies - 1 through 11 (of 11 total)
    Author
    Replies
    • Sticking with 2004 for now. I usually don’t update until the current version is no longer supported. Usually by that time most of the bugs have been eliminated.

      IGS

    • Haven’t updated to 20h2 yet. Currently using an HP Office jet printer. Should I be be concerned about this if I
      finally take the update plunge? Thanks

      IGS

    • 2018? I believe you meant November 2019 which is when support for 1803 may end.

      IGS

    • The way I see it, if it ain’t broke why fix it. I’m currently happy with 1803. Two out of my three laptops have had at least one issue with a feature update, some of those where rather benign and others were a pain. When 1803 is no longer supported, then and only then will I have a need to update to 1903.

      IGS

    • in reply to: FYI: 1903 update #1967144

      For the last two days it says I’m all up to date. The combination of using a metered connection and the wushuhide delayed the need to download 1903 at this time.

      IGS

    • in reply to: FYI: 1903 update #1965808

      Update! No pun intended. The windows update utility now show I’m up to date again. It seems that when you re-boot, it says you are are missing updates, but since I hid 1903, it eventually shows my laptop as up to date. What a mess.

      IGS

    • in reply to: 1709 metered forced 1803 update #212429

       Windows is now forcing 1803 on those applications that
      are currently using build 1709. I did my 1709 cumulative updates today
      on my metered connection. 1803 was hidden using the wushuhide as usual.
      Windows update utility showed my PC was current, after I
      installed the updates. However, a few hours later, with out warning,
      Windows started installing feature update 1803! My settings have always
      been on manual not automatic. Nor did I chose any time settings except active hours which are set to start at 8am and end at 2am. The update occurred around 7pm, well within that time frame. I’m
      using Home, but I wouldn’t be surprised if this occurs with Pro, since
      they did pulled a similar stunt with the previous Fall Creators build.

      IGS

    • in reply to: So how DO you block the upgrade to Win10 1709 #174017

      The only credible solution to MS’s forced update issue is a class action suit, which if they lost, would be a pr disaster for them. Although it may take some time to implement, the individual law suits that have currently been settled are chum change for MS and utterly useless

      IGS

      3 users thanked author for this post.
    • I have Windows home and have delayed the Fall Creators update 1709 using the wushuhide until today when it was forced on me using the latest cumulative update. Fortunately the only issue so far was the same I had with the 1703 upgrade. I had to  reinstall both my graphics and web camera drivers on my Lenovo Ideapad 500 laptop. My wife’s older HP Pavilion, which was originally upgraded from Windows 8 to 10, has yet to have any problems with 1511, 1703 and 1709 upgrades. (skipped the anniversary 1607 update on both).

      IGS

    • I have two laptops. A Lenovo Ideapad and a HP Pavilion. I use the MS update toll wushuhide on both for preventing feature updates until they have been tested and proven reliable. I am currently running build 1703 and plan to continue using that build until it is no longer supported. My previous build was 1511 and I never bothered with the anniversary update 1607. As a result, I have never has any issues with my cumulative updates each month.

      IGS

    • No issues with the July update which was done on both my Lenovo and HP laptops, Both are sporting Windows version 1511.

      IGS

    Viewing 11 replies - 1 through 11 (of 11 total)