• Berserker79

    Berserker79

    @berserker79

    Viewing 15 replies - 226 through 240 (of 246 total)
    Author
    Replies
    • There is also this bit of interesting info:

      Addresses an issue that may result in an error when you install Features On Demand (FOD), such as .Net 3.5. The error is, “The changes couldn’t be complete. Please reboot your computer and try again. Error code: 0x800f0950.”

      Did Microsoft fix the issue that prevented installing .NET 3.5 on those machines that had received the IE patch?

    • Yeah, just noticed this update through wushowhide and decided to hide it for the moment. Looks like more MS sillyness regarding this IE patch?

      As far as I understand, this is the same IE patch as the previous out-of-band patch of September 23 and also included in the following optional update of September 24, but according to MS the new update also corrects a printing issue.

      I’m assuming the same caveats (as per Woody’s CW article) of the previous versions of the IE patch apply also to this new version.

    • in reply to: MS-DEFCON 3: Time to get the August 2019 patches installed #1941758

      That may explain whythe July CU disappeared from the hidden updates: I had not realized that upon release of the a new CU the previous month’s CU disappears. Still, that does not explain why I have not been offered the August CU.

      I confirm that the July SSU KB4509094 update has been manually installed (before installing KB4512501) and shows up among the Installed Updates.

      Think I’m going to wait and see whether I’m offered the September CU next week. If not, I can try to run the WU Troubleshooter to “repair” WU. In the worst case scenario, I’ll continue to manually install the monthly CUs, then at some point I will have to move from 1803 to a newer version and I suspect that will probably solve this problem.

    • in reply to: MS-DEFCON 3: Time to get the August 2019 patches installed #1941724

      Thanks for taking the time to re-post your message, it is very helpful.

      It does sound very reasonable that KB4507466 overrides the earlier KB4507435, so I will not install ‘435 manually. Thanks for sharing that bit of info!

      BTW, I did answer PKcano’s questions above. I did not apply any changes that may have interfered with the updates. Since I’m on Win10 1803 Home, I don’t have any Policy restricting updates. All I do is simply setting my connection to metered and use wushowhide to hide the updates until Woody brings the defcon to 4 every month.

      The only relevant “change” is that back in July MS tried to force the 1903 update on my PC, but I hid that update with wushowhide. It seems that since that attempt to force the 1903 update I was no longer offered the monthly CU updates.

      I already tried to clear out old update data before installing the August patches, but that did not seem to help. I’ll try to repair Windows Update with the Windows Update Troubleshooter and see what happens.

    • in reply to: MS-DEFCON 3: Time to get the August 2019 patches installed #1941693

      As far as I can tell, I didn’t apply any changes in the month before I stopped receiving those updates and I didn’t install anything that may have tweaked my settings, the registry or anything else. The only “update blocker” (sort of) I’m using is wushowhide and I didn’t try any third-party tools so far.

      When the 2019-07 CU KB4507435 was released I was initially offered the update, but I hid it with wushowhide. The update was visible in the list of hidden updates. However, when it came time to install the July patches, KB4507435 simply disappeared, i.e. it was no longer shown as a hidden, nor as an available update. That happened around when MS first tried to force the upgrade to 1903. Since then, I’ve not being offered the Patch Tuesday updates, but I’m regularly offered Office updates as well as other updates, e.g. Windows Malicious Software Removal Tool updates, the (stupid) KB4023057 updates or the .NET 4.8 update.

      There were two attempts to force the upgrade to 1903 on my PC and both times I hid the update with wushowhide. In both cases, WU initially gave me a yellow warning sign that the 1903 update was ready for download, but could not be downloaded since my connection was set to metered. At some point, that warning disappeared on its own and WU got back to the green sign saying the system is up to date without me taking any steps for that to happen.  Could it be that my system is somehow “flagged” as ready for 1903 and for that reason I’m not receiving the Patch Tuesday updates?

    • in reply to: MS-DEFCON 3: Time to get the August 2019 patches installed #1941261

      Thanks for your reply Anonymous 🙂

      I did take a look at KB4512509, but usually I don’t install the second monthly CUs since I understand that they are basically “previews” of the following month’s first CU. At present it seems that I don’t need to get any of the fixes of KB4512509 installed right away, so I’ll probably wait a little more before installing this one.

      And yes, I did install the latest SSU (KB4509094)  right before installing KB4507466 some weeks ago. I still have no clue what caused WU to stop showing CUs, but as long I can install them manually that’s still ok. BTW, would you recommend installing KB4507435 that I accidentally missed even if I installed KB4507466?

    • in reply to: MS-DEFCON 3: Time to get the August 2019 patches installed #1941240

      Windows 10 1803 Home here.

      Just installed all the various August Patches for Office 2013 through WU, skipped the annoying 2019-08 KB4023057 and for the time being also the .NET 4.8 update KB4486153 which I was also offered through WU, and manually installed the 2019-08 CU KB4512501 (this did not show up at all in WU).

      Computer still working correctly as far as I can tell and after installing KB4512501 I didn’t get that “Procedure call error,” message that Woody warned about in ComputerWorld, so for the time being I didn’t install KB4512509 (issues with broken VB shouldn’t be a problem on my machine).

      Question:
      Ever since July (around when WU tried to push me to 1903), WU stopped offering me the monthly CUs, so I resorted to install them manually. Turns out that back in August when the July patches were green-lighted I manually installed the 2nd July CU for 1803, i.e. KB4507466, rather than the 1st July CU, i.e KB4507435.

      Should I manually install KB4507435 at this point?

      1 user thanked author for this post.
    • Hey everyone, I was preparing to install the July patches (Windows 10 Home 1803 here) when I noticed something “unusual” upon running wushowhide to un-hide the July updates: the July CU for 1803 (i.e. KB4507435) has disappeared from the list of hidden updates (all I see in the hidden updates list are the July Office 2013 updates, the 2019-07 Windows Defender update, the 2019-08 KB4023057 update and the Feature update to 1903).

      Assuming that WU will not automatically install the July CU for 1803 with the other July updates, should I install it (and the corresponding servicing stack update) manually by downloading the relevant files from the MS Update Catalog? Or should I just skip this CU entirely?

      1 user thanked author for this post.
      KP
    • Just a heads-up to report that today on my Windows 10 1803 Home machine I was offered a new KB 4023057 update (2019-08). I suppose this update was released after woody changed the MS-DEFCON level to 4, so anyone on 1803 trying to avoid KB 4023057 better keep your eyes open when installing the July patches.

      1 user thanked author for this post.
    • Thanks PKCano. I plan to hang on to the metered connection and keep my fingers crossed. No download of 1903 took place on the metered connection so far, but I’m not too happy sitting here just waiting for it to potentially happen. I’m actually wondering whether to avoid this uncertainty I should upgrade to 1809 using the copy I downloaded back when that was suggested.

      What is really interesting, however, is that today my Windows Update screen changed back to the “All available updates installed” and it is no longer reporting the Feature Update to 1903 being pending for download:

      Screenshot_WU_20190801

      I did not take any further steps after yesterday’s notice about the pending download (except running wushowhide which reported nothing available to hide). Also, the “last checked” date did not change. It almost looks like WU tried to push 1903, failed because the connection is set to metered, then on the subsequent reboot realized that I hid the 1903 Feature Update in wushowhide. Does this sound possible?

    • Using wushowhide on July 27 I spotted on my Windows 10 Home 1803 computer the Feature Update to 1903: I promptly hid it in wushowhide, checked that it was hidden and followed the “How to clear the Windows Update queue in Win10” instructions from PKCano. After that, the Windows Update screen reported that all available updates were installed and that the last check had been performed on July 27 around 4 pm.

      Today I was surprised to receive a notification that an “update cannot be installed”, so I looked in Windows Update and found the following:

      Screenshot_WU_20190731

      It’s not in English (apologies), but it’s saying that the last check dates back to July 27 at around 4 pm (i.e. the same date when it previously reported no updated being available), but now it is reporting that the Feature Update to 1903 is pending, but cannot be downloaded due to my ethernet connection being set to metered.

      I find this extremely annoying and suspicious, since it looks like hiding Feature Update to 1903 in wushowhide was not enough to really hide the update.

      2 users thanked author for this post.
    • I just spotted the Feature update to 1903 in wushowhide and promptly hid it, since I’m not ready to install 1903 and happy to stay with 1803 for a few more months.

      I’m currently on Windows 10 Home 1803, with June updates installed, no July updates installed, no instance of KB4023057 installed and my connection set to metered. Windows Update is still showing the “Download and install now” notice and (a bit misleadingly) saying that I can install 1903 when I’m ready to do that. I assume that having the Feature update to 1903 showing up in wushowhide actually means that MS was tired of waiting for me to be ready to install and decided to not-so-gently push the update on my machine.

      Assuming things work as expected, it seems that wushowhide is the best ally for anyone running Windows 10 Home who wish to postpone the Feature update to 1903.

      1 user thanked author for this post.
    • Thanks for your reply anonymous! 🙂

      Honestly, I have no idea why they are using the Consumer Edition. Anyway, thanks for the info regarding that ‘2019-03B’ update. Also, today the computer finally completed the download of all three updates and guess what? The two 1809 updates failed to install with a certain error code, while 1903 is waiting for me to begin installation. I can only guess that there was something wrong with both 1809 and 1903 being offered at the same time, but Windows Update ultimately decided that 1903 is the feature update to install.

    • Thanks for your always timely replies, much appreciated!

      Yeah, I’d rather upgrade to 1809 when it’s me who wants to do it, rather than having MS force an upgrade to 1903 when I least expect it.

      All things considered, since I’m using Home and thus don’t have the Feature deferral setting, I’ll not take the risk of going through Windows Update to see whether I can upgrade to 1809. When I decide to do the upgrade it seems safer to rely on the ISO I previously downloaded, albeit I understand that this will require me to install updates to make 1809 current (I’m confident that with metered connections and wushowhide I’ll have at least a minimum of control on which updates get installed).

    • Is an upgrade from 1803 to 1809 recommended at this point in order to avoid the uncertainties of an upgrade to 1903? Out of precaution I downloaded a 1809 .iso when it was suggested by Woody a couple of months ago, but I never planned to actually use it and would rather stay on 1803 and skip 1809 unless the risk of a forced upgrade from 1803 to 1903 is too high. Also, will an upgrade to 1809 avoid being pushed to 1903 also for those like me who have Win10 Home rather than Pro?

      BTW, on a slightly-but-not-so-unrelated note, I just saw on wushowhide that MS is pushing yet another release (2019-06 version) of KB4023057 to 1803 users.

      1 user thanked author for this post.
    Viewing 15 replies - 226 through 240 (of 246 total)