• Terry Muench

    Terry Muench


    Viewing 11 replies - 1 through 11 (of 11 total)
    • in reply to: So should I go directly to KB5001649 for March patches? #2353255

      KB5000802 WOES — DO NOT INSTALL

      For those who have not researched KB5000802 it is one of the worst Cumulative Updates in recent memory. BSODs, printer woes, etc., etc, … It’s so bad Microsoft released TWO Out-Of-Band fixes. The second one no doubt fixed the first fix. I made the mistake of applying KB5000802 after upgrading v1909 => v2004. I have had nothing but problems on one of my four PCs since.

      On this one machine (my daily driver) I had black screens after rebooting more than once. Also, this one PC hung consistently after waking up from sleep. How bleeped up is this??

      I had to uninstall KB5000802 using WUSA so I could get some work done. I plan to install KB5001649 this weekend.

      **DO NOT** INSTALL KB5000802. If you are not offered KB5001649 get if from the Microsoft Catalog..

    • I agree: Windows 10 20H1 aka v2004 should be pulled IMMEDIATELY. It is untested garbage. You only need to look on askWoody.com to see dozens of issues reported. As per usual, Microsoft is releasing a MAJOR OS upgrade without full testing.

      I had MAJOR problems with upgrading v1903 to v1909; I had to install from the downloaded (ISO) Win10_1909_English_x64.iso instead of installing from WUP (Windows Update). Why? Because v2004 had already dropped on this machine, replacing the v1909 which was available only a few days earlier. I was able to install v1909 using WUP on only one machine; it took TEN MINUTES because all that is involved is “flipping a switch” as v1903 and v1909 share a common code base.

      When I upgraded my desktop machine using the ISO it took almost THREE HOURS> And, it died after being stuck at 91%. The error was

      0x8007042B – 0x4000D
      The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation

      Here’s what I did – after a lot of research – to get the upgrade to work

      1. Run DISM

      DISM.exe /Online /Cleanup-Image /Restorehealth

      2. Run SFC

      sfc /scannow
      Windows Resource Protection found corrupt files and successfully repaired them.

      3. disconnect from Internet

      disable your Wi-Fi/Ethernet adapter

      4. disable Malwarebytes A-V

      5. disable unneeded startup items in Task Manager

      for example, I disabled Epson FAX send/receive as I don’t FAX

      This time the upgrade was done in 2 hours w/o errors. After reboot, I had to re-enable MWB and re-enable any wanted startup items. I had one unusual thing happen after the final reboot: I could create folders under my /Documents root, but could not create/write files as the folder was marked Read-Only; the R/O attribute could not be cleared. Yes, my account has the Administrator tag.


      The above link shows you how to fix the problem.

      1 user thanked author for this post.
    • https://greatis.com/stopupdates10/

      No, StopUpdates10 is not from Microsoft. Get it at the link above. I should note that Microsoft finally gave Windows 10 users the ability to pause updates in v1903 aka 19H1. However if I have a choice between Microsoft and a 3rd party tool which probably works, I will choose the 3rd party tool!


    • Well, Microsoft has done it again — force fed me KB4551762 (CVE-2020-0796) re: the SMBv3 security hole. Last night I left my PC asleep; this morning I came in to find my PC “ON” and updated without my permission. I am now at 18362.720. I am using StopUpdates10 to Pause updates. This has never happened since I’ve been using StopUpdates10 (a great tool by the way).

      I realize KB4551762 is a critical update but @askWoody has said there are no known exploits. I don’t appreciate Microsoft again ignoring its own rules and NOT honoring my wishes to pause Updates.

    • in reply to: MS-DEFCON 4: It’s time to get patched #1999708

      I have been very happy with StopUpdates10 altho it did not work on one of my 3 home PCs which were all on v1803 at the time. After upgrading all three to v1903, StopUpdates10 works everywhere. Before StopUpdates10 I was using WUShowHide and a Metered Cxn to block updates; then recently I found updates were not blocked — so not much of a help!?! I have only used PAUSE and RESUME; I have not installed the background Service.

      Yes, v1903 now includes PAUSE/RESUME which I haven’t tried. For one thing it is limited to 7 days (?) while StopUpdates10 can PAUSE for any time period. If I have a choice between Microsoft and a tool I know works, guess which one I will use?

    • in reply to: After updates paused unable to resume updates #1985937

      If I understand correctly, @rfinney has W10 Pro v1809 and, after Pausing updates, tried to Resume updates. Which should be easy. You should immediately upgrade to v1903. Version 1809 was one of the worst Microsoft upgrades ever. Early releases of the upgrade deleted user’s files. I skipped v1809 and went directly from v1803 to v1903.

      In the future I suggest you do not trust Microsoft if there is another option. In this case there is: StopUpdates10 which I heard about on @AskWoody. You can not only Pause/Resume updates (I have done both) but also Disable updates completely. Highly recommended.

    • Thank you Microsoft for force-feeding me W10 v1903. I have been blocking it (first v1809) for months using WUShowHide. On Sat 10/19/2019 I got the DREADED (We’re here to help you) UpdateAssistant popup giving me a few minutes to save my work before starting the Upgrade. Fortunately I was able to Cancel. I checked the #4 UpdateAssistant Tasks in Task Scheduler — which I had Disabled — and Microsoft had re-Enabled them. I Disabled them AGAIN and thought I was set.

      No such luck. Later in the day I got the popup again, and cancelled again. Yet later I was remoting to another machine to backup an Oracle VBox VMDK (virtual drive) and forgot about UpdateAssistant. When I checked back on the Desktop it was too late — the Upgrade was underway. I think KB4023814 was responsible for UpdateAssistant running amok.

      I hope others can learn from this. MICROSOFT IS GOING TO PUSH those on v1803 — which ‘expires’ on Nov 12 — to Upgrade to v1903. By any means necessary.

      • This reply was modified 3 years, 7 months ago by Terry Muench.
      1 user thanked author for this post.
    • in reply to: New AskWoody support for Apple products #1965109

      I SUGGEST putting ‘askWoody/Apple’ on a separate page separate from Windows. This is nothing to do with Apple, rather (to me) a logical separation. Apples and Oranges?



    • in reply to: Patch Lady – Windows 10 update facilitation service #199587

      A new post says about KB4056254 aka “Windows Update Facilitator”

      I’m on 1709 and have just been offered this update (needless to say I blocked it). I checked the MS page for KB4056254 and it still clearly states “Only certain builds of Windows 10 Versions 1507, 1511, 1607, and 1703 require this update.”, no mention of 1709.”

      The poster is absolutely correct; when this KB appeared in Feb it was to force feed us v1709; this version which appeared in June apparently wants to force feed us v1803. As reported, this is cojoined with Update Assistant V2 — the V2 obviously meaning for the next (v1803).

      I despise Microsoft for this.

      Edit to remove HTML

      1 user thanked author for this post.
    • in reply to: March 2018 Patch Tuesday #175661

      Supposedly (KB4023814 => Windows 10 Update Assistant) cannot be uninstalled, at least not easily.

      I have seen many posts on how to disable the totally obnoxious Update Assistant; yes you use the Task Scheduler, but no need to get into triggers or anything else; simply disable the three tasks listed below

      > Microsoft > Windows > UpdateOrchestrator




      So far on my three home PCs, Microsoft has not yet re-enabled these tasks. Don’t be surprised if they do, so check regularly.


      1 user thanked author for this post.
    • in reply to: Another complaint about KB 4023057 #167754

      As if the Spectre/Meltdown nightmare wasn’t enough to deal with …

      I want to thank the author also for this excellent post re: the WUP ‘enhancements’ that M$ won’t divulge any details about. This is the first post I have found that explains the recent flood of KBs with Remediation, new Service ‘osrss’, etc.

      The author says “you do not need any of those updates if you intend to stay on your current Windows 10 version, or want to upgrade on your terms.” Be warned that if you install KB4023057 and KB4056254 you won’t be able to uninstall them. At least, I have not found a way.


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