Welcome to the third cumulative update for Win10 1709 this month, KB 4058258

Topic

New Reply

I went back and counted, and came up with 15 different days this month that have had Windows/Office patches, pulled patches, re-patches, and the like.
[See the full post at: Welcome to the third cumulative update for Win10 1709 this month, KB 4058258]

3 users thanked author for this post.

Tiernan, Fred, abbodi86

Reply | Quote

Replies

But it’s all Intel’s fault, Shirley? 😉

2 users thanked author for this post.

BobbyB, woody

Reply | Quote

Roger Roger

Reply | Quote

Still won’t install on any of my v1709 test system snapshots, even those that accepted prior cumulative updates.

THAT’s not Intel’s fault.

The failure is 0x800f0922, by the way, even though the system passes SFC and DISM checks.

Not quite what I’d call a “robust” update process.

-Noel

Reply | Quote

That’s the old .NET 3.5 update error code, isn’t it?

Reply | Quote

Thanks, one finds a lot of mention of that code online in network search results. Most say that it’s a servicing corruption that will be fixed by SFC / DISM commands (which have continually been reporting all’s well with my setup).

I’ve made some progress since posting the above, having succeeded using the [Check for Updates] button to get an incantation of Win 10 all the way to the message “Your device is up to date” last night. The bad news? It stopped finding new updates at 16299.125. No worries, I’ll figure it out – it’s what I do, though the necessity of using a “try and try again until something works” strategy isn’t really sustainable it if wasn’t a test VM but rather a REAL COMPUTER SYSTEM. Would it be so hard for them to just put up a simple “this is what is blocking the update” message?

Fundamentally:

This is the year 2018. Why did I have to dig and dig until I found a hex error code in C:\Windows\SoftwareDistribution\ReportingEvents.log?

As a technical person who’s always rolled up my sleeves and troubleshot Windows problems, I’d be tempted to say the serviceability of Windows is going DOWN. It’s failing cryptically and most certainly not fixing itself. Not exactly “as a service” sufficient, I’d say.

-Noel

2 users thanked author for this post.

woody, johnf

Reply | Quote

Hmmmm.. Microsoft has this to say about KB4058258

Known Issue

Windows Update History reports that KB4054517 failed to install because of error 0x80070643.

Workaround

Even though the update was successfully installed, Windows Update incorrectly reports that the update failed to install. To verify the installation, select Check for updates to confirm that there are no additional updates available.

You can also type About your PC in the Search box on the taskbar to confirm that your device is using the expected OS build.

Microsoft is working on a resolution and will provide an update in an upcoming release.

Wonder if that will confuse the hoi polloi?

1 user thanked author for this post.

Cybertooth

Reply | Quote

woody wrote:

I went back and counted, and came up with 15 different days this month that have had Windows/Office patches, pulled patches, re-patches, and the like.

When does musical chairs end?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

Ends today. Tomorrow starts a new month.

4 users thanked author for this post.

windows7wasthebest, JohnW, Elly, Noel Carboni

Reply | Quote

Heh. Heh. Heh.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

Elly

Reply | Quote

Hard to keep up anymore? Do we need to start questioning who at Microsoft really is qualified?

1 user thanked author for this post.

Elly

Reply | Quote

Sounds like it’s ready for business to me.

Funny business? Monkey business? Doing your business?

Certainly not my software engineering business.

-Noel

5 users thanked author for this post.

JohnW, Sessh, Elly, PKCano

Reply | Quote

Its not getting any better Microsoft. I thought your ideal of these updates was to reduce the number of them? It certainly hasn’t worked out that way.

1 user thanked author for this post.

Elly

Reply | Quote

Servicing Stack update KB4074608 has nothing to do with WaaSMedic or Remediation Shell
it’s just misunderstanding because @ch100 replied to comment about it

SSUs are oppressed updates and oftenly accused for OS issues, but they are innocent all the way 😀

2 users thanked author for this post.

ch100, woody

Reply | Quote

All these cumulative updates this month, and they still haven’t fixed the stupid mouse twitch bug from 1709, which causes the mouse cursor to suddenly “twitch” to upper right (or sometimes left) corner of screen, when selecting items and scrollbars are visible in the window. The bug can be reproduced at least in 7-zip, Bandizip, WinSCP and even Windows’ own Task Scheduler window. Just shrink the window, so that scrollbars are visible and then try selecting multiple items by clicking and dragging.

As this latest update seems to be non-security one, it would have been nice opportunity to get it fixed. Oh well, I guess we’ll wait some more. It’s only been several months.

1 user thanked author for this post.

woody

Reply | Quote

It’s not a bug.

It’s a funny little game called “Find the cursor”…

2 users thanked author for this post.

windows7wasthebest, woody

Reply | Quote

I suspect that with a recent microcode update Intel has finally implemented the fabled JS (Jump Somewhere) instruction and Microsoft, with an update, has made immediate use of it in the mouse pointer control subsystem. It’s a security mechanism to keep you from accidentally clicking [ OK ] on an unexpected UAC prompt.

-Noel

2 users thanked author for this post.

AlexEiffel, windows7wasthebest

Reply | Quote

ye it happens with winrar 5.50 also!

Reply | Quote

My dad sat down at his win10 computer this morning and it said “Welcome” at the bottom with a spinning circle dots thing.

Over that was a popup with a red X that says “Windows could not complete the installation. To install Windows on this computer, restart the installation.” There is only an OK button. Clicking OK just loops back to this point.

I have to assume that it is trying to install a new update and broke things. I have his computer set up for auto login, which broke things several months ago after an update so bad that I had to reinstall Windows. Should win10 updates just never be installed until months later?

1 user thanked author for this post.

AlexEiffel

Reply | Quote

Just to put things in perspective, on both my home and work computers I’ve had just two updates for 1709 this month (and one of those on each was for Adobe Flash), and both say they’re up-to-date.

So not all Windows 10 version 1709 computers have been flooded with updates this month. I’ve had none in the last three weeks.

Reply | Quote

How did you dodge the last two?

Reply | Quote

QualityCompat registry set?
Settings > Update is used for checking?

x64 only got two through WU, the one on January 3, and today’s KB4058258
x86 only got the one on January 3, today’s KB4058258 not yet

Reply | Quote

So is your QualityCompat set?

Reply | Quote

Many people who have posted on this site the last few years foresaw these types of problems with the forced updates/patching protocols rolled out for W10 (WaaS). Rather than listening to valid concerns, MS went their merry way and are now finding they have jumped the shark but have no easy way to adjust course. Many users have refused to move to W10 because they understood the issues and sensed the potential outcomes were not anything they wished to embrace. The move to cumulative ‘all or nothing’ updates for W7 and W8.1 also brought undesirable side effects which will be fully displayed before this Meltdown/Spectre patching fiasco is fully played out. I find myself spending ever more time working in my Linux virtual OS to prepare myself for the final adios. If that truly happens it will be a case where I did not leave Windows but Windows left me.

7 users thanked author for this post.

Jan K., johnf, Ascaris, Bill C., Cybertooth, ryegrass, Elly

Reply | Quote

anonymous wrote:

I find myself spending ever more time working in my Linux virtual OS to prepare myself for the final adios. If that truly happens it will be a case where I did not leave Windows but Windows left me.

I’d suggest moving to a dual-boot setup once you’ve decided on a distro.  You can begin migrating things, getting things working in Linux without having to worry if they don’t work just yet (you can just use Windows until you get it working)… and you’re making progress toward that Linux setup as you go, which you’re not in the virtual world.  There’s nothing like having the same hardware you’re using day-to-day in Linux to get a feel for the new OS, I think.

I had Linux set up on a test PC (I have more than I know what to do with) as a dual-boot with Win 10 in 2015.  The idea was that one or the other was going to be my new home eventually.  My expectation at that time was that while Windows 10 was horrible, IMO, it would certainly get better over time, as other versions of Windows have.  The much maligned Vista became a stable and decent product in time, though most people had already fled Vista-land and never realized things got better (and so the reputation is frozen at the moment of those people’s last recollection of their experience with Vista).

In time, I came to see that Win 10 was not getting better at all.  While there were some specific things that I liked about most or all of the new feature releases, my perception was (and is) that it was getting worse with each new version overall, and the sheer amount of churn in each of these versions was beyond excessive.  Too much breakage, too much change, too fast.

That was when I decided that having Linux on a test machine (a lot like a VM, I think) wasn’t good enough for the grim new reality of having to leave MS-land, my home for more than a quarter of a century.  If it wasn’t a choice I had to make at boot time to use Windows or Linux, if it wasn’t on the same hardware that I was already intimately familiar with, it would be too easy to just fall into a pattern of using Windows as I had always done, not giving Linux anything more than the occasional boot for giggles.  I had to work toward making my computer… my main computer as capable under Linux as it was in Windows.

I’m mostly there.  A lot of the little utilities that are so useful that exist only in Windows versions (like the MMtool.exe editor for AMI BIOS) run perfectly under Linux using WINE.  It’s a little scary doing BIOS editing like that, but as far as MMtool is concerned, it’s just a data file.  I haven’t actually flashed one yet for the ultimate test, but I’ve built them and taken them apart again under Windows and found everything to be as expected– the orom and microcode binary blobs are extracted perfectly, validated using SHA256 hash checks.

Overall, Windows is still ahead of Linux overall in terms of the usability and sophistication of the GUI, but that doesn’t do me any good if I decide to abandon 7 and 8.1… 10 is not in the list of options, so I might as well prepare for the future as it appears.  Should Microsoft change its mind about all that I find wrong with 10, I will re-evaluate, but lemme tell ya, a lot of trust has been lost.  I’ll never go back to Windows only; I think Linux is here (on my PCs) to stay, but whether Windows continues to get a seat at the table into the future is very much uncertain.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon 6.2
XPG Xenia 15, i7-9750H/32GB & GTX1660ti, Kubuntu 24.04
Acer Swift Go 14, i5-1335U/16GB, Kubuntu 24.04 (and Win 11)

4 users thanked author for this post.

Cascadian, Elly, Cybertooth, johnf

Reply | Quote

First sentence from the article:

Microsoft told us three weeks ago that Win10 Fall Creators Update, version 1709, was ready for enterprise deployment.

I would love to see the definition of “ready” in Microsoft’s dictionary…

1 user thanked author for this post.

Elly

Reply | Quote

One feature-not-a-bug of old dead tree publishing is you had to be careful to get it right the first time. Admitting you were wrong and republishing a corrected copy was prohibitive in both cost and reputation.

The bug-not-a-feature of electronic publishing is you can do what you like, change on a whim, and confuse the evidence there was ever a contradictory position; all at the push of a button. This makes it very difficult to track back to where a difficulty began.

I visualize a Microsoft dictionary as printed with that weird ferrofluid that moves in strange ways. When the usage changes, so does the definition.

3 users thanked author for this post.

Jan K., windows7wasthebest, Elly

Reply | Quote

Jan K. wrote:

I would love to see the definition of “ready” in Microsoft’s dictionary…

Unfortunately I don’t think they’ve precisely defined the term. It’s usage appears to be shorthand for the more-honest-but-longer phrase “Well, it’s been a few months since we first released it, so we’re thinking maybe it’s ready… to send out to a larger group of beta-testers.”

1 user thanked author for this post.

Cybertooth

Reply | Quote

With all these patches on patches investing in deckchairs on the Titanic might give better survival odds.

1 user thanked author for this post.

windows7wasthebest

Reply | Quote

Welcome to the New Year, this is WaaS, Windows as a Service.

Those are not bugs, they are  Features.

 

Reply | Quote

I really hope that Microsoft wakes up and changes course regarding Win10 update strategy.  It’s about time!

Windows 10 Pro 22H2

1 user thanked author for this post.

Cybertooth

Reply | Quote

All those patches delivered in January are previews (even if Microsoft didn’t say so) and if permissions to install preview releases have been denied via group policies, none of them are installed.

Reply | Quote

b wrote:

But it’s all Intel’s fault, Shirley? 

0

Being a convicted to be a test-monkey-user(without trial) since Windows-01 I keep my fingers crossed, while imaging the b***** thing again.

Thank Woody for the headsup 🙂

* _ ... _ *

Reply | Quote

Hello to the good people at AskWoody…I have a new-ish Windows 10 Dell computer on 1709. Yesterday I updated to the latest cumulative update (KB4058258).

Upon restarting, it did it’s initialization of telling me it’s doing the update, then it brought me to the usual Win10 desktop photo (log-in screen). After logging in, the screen went black except for a small rectangular pop-up in the upper left corner.

The content of the pop-up states Personalized Settings (Not Responding). After a minute or two, the desktop loaded as normal. I did a restart and the problem did not occur (went straight to desktop after logging in).

Results from a Google search on this issue shows that many people have had this happen. Windows forums give all sorts of ways to fix this. However, the fixes suggested do not seem to permanently help people (the issue comes back on future updates).

Honestly, I do not understand this. I don’t want to mess with Registry settings or run commands that I don’t understand in Task Manager. I am so frustrated. What happens on the next cumulative update? Will the computer just hang at this screen forever? Aggggghhhhhh!!!

Any advice/explanations would be much appreciated.
Thanks!!!!

Reply | Quote

Bit off subject, but still Microsoft and Woody’s favorite machine! Right?

The Register this AM reports continuing and wide ranging problems on Surface 4 with screen flickering making the system unusable. Some owners have had the screen replaced 3-4 times, but the problem always recurs.

1 user thanked author for this post.

woody

Reply | Quote

Yep, The Reg ran something about that this morning.

I think it’s very similar to what I’ve been whining about for a year now:

https://www.computerworld.com/article/3237144/microsoft-windows/microsoft-promises-fixes-for-several-long-standing-surface-problems.html

 

Reply | Quote

My computer found the new 1709 CU (KB4058258) yesterday after I turned it on and began downloading it.  It downloaded and installed fine before the restart.  The restart took a couple minutes longer than usual, but everything seemed to go as normal.

When it finished the restart process, it had a message in the sidebar saying that “we couldn’t finish installing updates.”  Clicking this message opened the WU history page.  It showed the new CU with the phrase “restart required to finish installing this update” underneath (implying that the previous restart didn’t do the trick).  However, when I checked my settings, my computer is now on build 16299.214.  Both the new CU and the accompanying servicing stack update are listed in the Control Panel.  If I click “Check for Updates,” it says everything is “up to date.”

Is this a variation of the known bug with the last couple updates (including this one) in which you get an error message saying the update failed even though it actually installed successfully?  I have no intention of uninstalling/reinstalling the update at this point because all signs indicate that it DID install properly.  The only unusual part is the “restart required” phrase that still shows up in the update history.

Reply | Quote

See quote from Microsoft pages at #163544 above.

Reply | Quote

Just to clarify…I should good to go (based on the Workaround from Microsoft)?

Everything checks out except for the “restart required” message.  I didn’t get the exact same error message as the one mentioned in the notes, but “About your PC” and “Check for Updates” both came back with the new information.

1 user thanked author for this post.

woody

Reply | Quote

Remember when Microsoft said after Windows 8.1 that their new Windows was going to be so great and so different and so much better they had no choice but to call it Windows One instead of Windows 9…

How funny this can be understood in a direction rather than the other…

Since Windows 8 first big patch, Microsoft went to new heights of treating its customers like they are very stupid.

Oh, you don’t like having no start menu? Start Menu is back, look, there is a button. Yes, it still opens that full screen tile you hate so much, and that hide your current work, but there is a Start Menu button, right?

Oh, you want to know what we collect about you? Look a the encrypted data using a packet sniffer. No? You are so difficult. How about looking at a dump file in hexadecimal and finding what we get there? Or maybe we could give you a huge list of things we could possibly collect and drown you with details so you might just give up and let us have it our way?

Oh, you want privacy? Here’s some new switches to appease you. Yeah, we made it a fun game of try to find them all. We have hidden some in unexpected places for your pleasure, plus each new update can bring exciting surprises, like resetting some of those. Plus, you know what? The settings are there, but sometimes we don’t respect them, just for fun, come on be a good sport! You have something to hide? And if you want to control what we collect about you, you need to allow your browser to receive a Microsoft cookie, log in with a Microsoft account and then tell us you don’t want us to track you online. We will respect your wish, promise. If we don’t save your name, it doesn’t count, right?

What? You want some control over updates? You don’t need it. We don’t make mistakes. We have solved the age old problem of not doing a clean install with Windows when we decided we would be perfect and now you can upgrade Windows twice a year with no issues. You still want some control for stability of your user experience? You will miss some exciting new features, like VR tools, more Cortana and Edge latest features! Ok, ok, we have some switches in group policies to delay feature upgrades. Yes, they work, it is just that we changed the names of the new features updates, so technically, 1709 is not current branch but semi-annual channel targeted so we respected your wish to not have current branch installed right away, you got semi-annual targeted. Why you get so mad at us? We only want the best for you.

Yeah, we know about issues with some third-parties that struggle to keep up with our excellency. If your software stops working after our Windows updates and there is no quick fix, you need to find better software partners. This is how it works with WaaS. You shouldn’t tolerate anything less than absolute excellence. Our engineer can explain to you how the process of managing your computer works in just a bit more than 20-30 pages (thanks David da Neve, nothing personal, I appreciate the effort). This is the way everyone works now in the software industry, get on board with the contemporary times and stop whining. We don’t get what you don’t get. It’s so obvious!

 

9 users thanked author for this post.

windows7wasthebest, flackcatcher, SkipH, Cascadian, Elly, MikeFromMarkham, dononline, Cybertooth, MrBrian

Reply | Quote

so far so good these updates… finally

* _ ... _ *

Reply | Quote

Is this KB available in WSUS? I have not yet seen it. Thx

Reply | Quote

I haven’t seen it in WSUS yet either.

Reply | Quote

Just in case update KB4058258 is failing with error 0x80073715 – I’ve addressed the whole mess in Windows10: Update KB4058258 causes error 0x80073715.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

2 users thanked author for this post.

satrow, woody

Reply | Quote

kb4058258   failed with  error  x8007025d

check update always has Restart  required

Restart Insignia tablet  showing same error

Since this error occurred lost Audio device and no sound

please note that kb4058258  installed successfully on my HP desktop and laptop.

best,

alex

please help

Reply | Quote

Known issue is noted on the Microsoft pages for the KB.

See #163544 above.

Reply | Quote

KB4058258 was failing for me too, effectively resulting a Windows Update boot loop. I was able to resolve the failure installing KB4058258 by first uninstalling KB4056892. I also had to run “wuauclt.exe /detectnow” to force a Windows update scan so that Windows Update realized the cumulative patch had now been installed correctly. YMMV.

Reply | Quote

if Microsoft will just give us back full control on windows updates, we then can set the list of problematic update to ignore, or turn off windows updates completely, i dont care if its Intel’s or Amd’s fault, its Microsoft fault for removing the ability for us to decide for our selfs when and what to update , microsoft.  they made the s**t mandatory updates, gave more control on updates on windows 10 pro, and less on windows 10 home…….

Edit to remove content
Please follow the –Lounge Rules– no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

1 user thanked author for this post.

Elly

Reply | Quote

Download “wushowhide” from microsoft and  you can “Hide” (Exclude) updates….

Reply | Quote

If you download “wushowhide” from microsoft you can exclude updates…

Get it here:
https://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-10-fall-creators-update/83a713d9-3cd1-4ad3-9421-6763897ad7a6?auth=1

I do this with KB4058258, because my computer went into an endless loop of download OK, install OK, download OK Install OK ….

Reply | Quote

KB58258 is strange…….

it download ok
it install ok
it reboot and update oK
build no is not updatted to 214 🙁

So then it

it download ok again
it install ok again
it reboot and update oK again
build no is not updatted to 214 again 🙁
So then it

it download ok again
it install ok again
it reboot and update oK again
build no is not updatted to 214 again

……

So now I hide it and wait for a new branch on:

https://technet.microsoft.com/en-us/windows/release-info.aspx

P.s
I am actually think windows 10 is the best windows until now…..

Reply | Quote