• howardagoldberg

    howardagoldberg

    @wshowardagoldberg

    Viewing 15 replies - 1 through 15 (of 100 total)
    Author
    Replies
    • in reply to: Issue with KB5001716 #2646064

      Turns out … this is being reported elsewhere:

      https://www.youtube.com/watch?v=NZXp9U7BNFs

      https://www.youtube.com/watch?v=vN1nwAtSSjs

      https://www.tenforums.com/windows-updates-activation/211685-issue-kb5001716-update-march-5-2024-a.html

      https://www.windowslatest.com/2024/03/07/microsoft-rolls-out-windows-10-kb5001716-and-it-fails-with-0x80070643/ > This article seems to indicate the issue is that after the 03-2024 version is installed, WU then tries to install the 10-2023 version thus triggering the error.

      At any rate, feel pretty confident this is a MS server-side issue and not something that can be fixed locally (although I guess one could hide the update, but this is a KB that is occasionally re-released so you don’t want to hide this one indefinitely).

       

    • in reply to: Issue with KB5001716 #2646052

      I don’t believe the issue is with Windows Update. This behavior is reproducible on two (fully-patched) Win 10 Pro machines. The issue is with the update and/or the update not registering correctly after it is first applied. Resetting WU won’t fix that.

      I can ‘fix’ the issue by uninstalling the update. Then WU will reinstall it with seemingly no issue. If you then ‘check for updates’ again, the error occurs because WU is trying to install the same update again that has already been installed. WU is not seeing that the update was already applied successfully.

    • in reply to: Issue with KB5001716 #2646038

      See attached screenshot. I also sent a message to the Patch Management list with screenshots.

      1 user thanked author for this post.
    • Since when are drivers installed in a cumulative update? If this is so, it is disturbing news. With that said …

       

      I think the driver was being updated yesterday morning (at least on the system the suffered the temporary USB system failure as described in the original post). It very much behaved as an incomplete driver install that resolved with a reboot.

      I install the cumulative updates the day they are released, so I was not installing any Windows Updates at the time that I discovered this issue.

      2 users thanked author for this post.
    • Drivers should not be updated as part of a cumulative update. There is no record in device manager or Windows Update that there was a driver update.

    • Yes, correct. Only driver update history is from nearly three years ago (06/17/2020), and nothing noted in Windows Update.

    • in reply to: Doing a bit of re-organizing #2370653

      Susan, thank you. IMHO this is a huge improvement. The links in the right-hand menu make everything much more accessible, less unwieldy, and the site does seem to pop (especially as compared to before this change). I like it!

    • On my 10+ year old Dell XPS 15, the 21H1 update was offered nearly the moment of release. Installed and not seeing any issues.

      On my 4 year old Inspirion 7353 – which ‘suffered’ the Conexant driver nonsense, but did finally get to 20H2 a few weeks ago, has not been offered the 21H1 update yet. Conexant driver issues are not noted by MS, and not public block is shown. But I wonder if I am going to have to go through these for every new update going forward …

    • in reply to: Conexant and the 2004 saga continues #2363713

      All I can say is … ARGHHH! Given that when *offered* the update, WU just stalled at 61% (while still in Windows, not during a reboot or rollback) as you detailed my experience in an earlier post.

      So now that I am on 20H2 … will I get 21H1 without issue? That is the next unanswered question. I cannot even imagine what the issue is. And to your point, why MS cannot (at this point) silently uninstall the driver at the beginning of the update process, and then reinstall silently during one of the reboots …

      I think we deserve some type of technical explanation, if for no other reason, I cannot imagine that those of us with Conexant drivers will not continue to face this issue for all subsequent (at least major) updates.

    • in reply to: So can you fix line spacing please? #2361388

      Not to be contrary … but actually, overall, I really enjoy the Office 365 Word experience (dark mode!), and find the Ribbon to be superior to the ‘older’ drop down menu navigation.

      The bullet/numbering/outline issues can be a pain at times, and agree with Susan that the presumed line-spacing is never what I want (I usually set to single space or 1.15, and adjust spacing between paragraphs by changing the font size for the blank line – far more control that way as one may want different spacing between major sections vs. paragraphs within a section, etc). Of course, that approach comes with its own challenges (like remembering what spacing I choose to be consistent through the document).

      Through the 1990s and early 2000s, I used WordPerfect. The one thing I continue to dearly miss is ‘Reveal Codes.’ That was/is a very powerful feature. It dismays me to this day that Word still does not have a similar feature. So many formatting mysteries could be resolved quickly and without much fuss if one could see the formatting codes, and just delete the offending ‘code.’

      I know WordPerfect is still out there, but working with colleagues around the world – using that software would certainly introduce its own share of challenges with regard to formatting, etc.

    • in reply to: Edge appears to be having a Friday meltdown #2358167

      I posted this in the browsers forum earlier today, also asking about the new update policy language being dispayed:

      https://www.askwoody.com/forums/topic/edge-90-0-earlier-versions-update-check-fails/

    • in reply to: Let’s get Mikey to try it #2351604

      unfortunately some users using Win10 version 2004 or 20H2 are experiencing installation errors trying to install the KB5001649 update – see this Ten forums topic.

      DON’T PATCH with this new update

      • This reply was modified 4 years, 1 month ago by EP.

      Yup … just tried 3 times on my 20H2 system, and failed exactly as described in the comments in the article you referenced. Not going to install manually, will wait until MS sorts this out. Also, as per Susan’s advice, I am not impacted by the printing issue – so … probably better I just leave it alone for now.

      2 users thanked author for this post.
    • in reply to: Bleeping computer reports Flash patch force installed #2344353

      Susan,

      Generally, I agree with you regarding ‘check for updates.’ In this case though, there should be an ‘optional updates’ section where this would fall.

      And with my 20H2 machine, as I said, it was installed with zero user interaction. Any time I checked for updates, the update was not offered, and the result of the check was ‘up to date.’ The Flash removal KB was installed completely silently.

    • in reply to: Bleeping computer reports Flash patch force installed #2344313

      On my 1909 system, when clicking ‘Check for Updates’ last night, it was downloaded and installed – no option given.

      On my 20H2 system – last night, the ‘Flash’ settings app was still in the Control Panel (legacy), and check for updates showed nothing. Just now, checked for updates again, nothing. But went to the Control Panel, and the Flash settings app was gone. Going to ‘View History’ in WU, under ‘other updates,’ it shows the removal update (KB4577586) was installed today (sometime between 6:30 a.m. and 1:00 p.m.) – completely silently, and no reboot requested/required.

      So … does not seem like an optional update. More so, on my 20H2 system, it installed without any user interaction whatsoever.

      It’s good by me Flash is gone – but this is not the behavior MS describes as the update should follow. And of course, continues begging the question how much control over updates we really have regardless of our settings.

    • in reply to: 1909 get out of band KB5001028 #2342961

      And like magic – with no obvious updates pushed or manually installed – this morning WU looks and behaves normally. (I power down at night, and cold boot each morning – fast boot is disabled.)

      I’m guessing some sort of MS server-side voodoo ..

    Viewing 15 replies - 1 through 15 (of 100 total)