Microsoft releases new version of Win10 patch KB 4023057

Topic

New Reply

Many people are blaming the KB 4023057 patch for all of the forced-upgrade-to-1709 woes. Guess what? Microsoft released a new version of the KB articl
[See the full post at: Microsoft releases new version of Win10 patch KB 4023057]

4 users thanked author for this post.

Elly, bobcat5536, SteveTree, MrBrian

Reply | Quote

Replies

I really can’t believe the forced upgrades were any more of an “accident” than GWX was.

Forcing a known defective upgrade on your customers is criminal IMO.

10 users thanked author for this post.

Elly, flackcatcher, HiFlyer, Cybertooth, Karlston, dononline, lanceboil, bobcat5536, fk5353, woody

Reply | Quote

Isn’t it great that software companies are apparently immune from lawsuits. 🙁

-lehnerus2000

1 user thanked author for this post.

HiFlyer

Reply | Quote

Probably another case of employee inattentiveness… too busy checking their cellphones for the latest tweet, FB meme, snapchat bla-bla, or playing Candy Crush on that shiny-new-already-broken-latest Win10 release.  I see this kind of employee / people behaviour all the time nowadays –  too “busy” to work diligently and “keep their nose to the grindstone” so to speak.

Maybe its not so bad… as long as the nurses mind the cardiac monitors in the ICU instead of thinking “d**n alarm, I’ll check it in a minute, I’m busy chatting with my friends”.

Reply | Quote

After this latest episode of stupidity, I have hardened my opinion that Microsoft deserves a spot in the Virus Hall Of Fame. I have never had to protect my PC against any virus or malware as hard as I’ve had to protect it from Microsoft. I’m sitting here with my hard wired PC set to wireless, several services disabled, an AB switch installed so I can kill my internet in a nanosecond and current image ready to go just in case the demon strikes and I miss it. This is not a rant, it’s today’s reality. I stopped by the local PC shop yesterday and they told me the repair business was very good and picking up steam. Lots of frustration and stress out there.

4 users thanked author for this post.

CADesertRat, LH, HiFlyer, Cybertooth

Reply | Quote

I believe the nasty in KB4023057 was the Windows 10 Installation Assistant, which after uninstalling from Add/Remove will almost immediately reinstall itself and start the install over. If in fact this is the monster that they pulled and it can be confirmed that it is gone, someone let us know and we can get back to putting things in order. Not to late to redo Feb. updates before catching the March ones. If not, I’ll wait for March Defcon 3 and catch back up since they’re cumulative.

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

Strange, I just hid that update for a computer not very long before before composing this comment.

Reply | Quote

My concern is which update or updates come with that nasty piece of malware call Windows 10 Update Assistant. For me anyway, it was in the Feb. updates. I didn’t have it on my PC until after I updated earlier this week.

Reply | Quote

So was this a intentional thing that Microsoft realized was going over like a lead balloon? Or was it simply a mistake somehow that caused the upgrades? I’ve run Windows since 3.11 and some of what Microsoft has done with Windows of late has given me pause to consider if I should not be running something else for a OS. In fact I have converted two older PC’s to Mint and if my laptop wasn’t so new and still in warranty I would probably switch it too. But as anyone who has tried calling technical support at a OEM knows. They are rather clueless dealing with Linux. Maybe a duel boot is in order to avoid all the Microsoft BS.

Reply | Quote

Jescott,

Are you certain that your laptop would be a problem with Linux because it is under warranty?

I bought a new laptop during one of the Christmas sales.  It is a low-end Dell with a measly 32 GB eMMC “hard drive,” which really is not big enough for the Windows 10 Home with which it came.  As Ms. Bradley noted, people have had issues with Windows 10 1709 being too big for 32 GB Windows 10 machines to install (as was discussed in another thread).

I recently had reason to call Dell tech support.  Something happened with the micro SD card reader, where it would no longer spring the card back out when I pushed it.  The card went in with little or no resistance, and it worked once it was in, mostly.  To get it out, I had to use a piece of tape to stick to the bit of the micro SD that was accessible and pull it out that way.

The little laptop by then had Mint on it, with Windows 10 having been wiped to make room.

I contacted Dell via the web chat application on their site, and the agent first suggested that I update the firmware (what that has to do with a card reader that obviously had some kind of physical defect, I don’t know).  This was before the Spectre and Meltdown vulnerabilities had become known to the world, and I’d already installed the new firmware before switching to Linux.  I told the agent it was already updated, and then he tried to get me to install a remote access program so he could poke around my PC.

What, exactly, did he think he could learn about my card reader by doing that?

I told him the PC no longer had Windows on it, so it would not be able to run the program he wanted.  He had no problem with that, and proceeded to verify my information to make sure the RMA info would be correct.

The computer was RMA’d and repaired without any problem.  I did, after the RMA was issued, decide to put Win 10 back on it before sending it off… I was going to wipe my drive one way or another, as my stuff is mine and I don’t want anyone pawing through it if I can avoid it, so I may as well return it to factory condition, I thought.  I wiped it again and restored my Linux image once I got it back.

The take-aways from this are that Dell, at least, has no problem with the user wiping the factory OS and putting on Linux in terms of the warranty, and also that the supposed tech support people aren’t just clueless with Linux… they’re clueless, period, if you go by this experience at least.

I’ve never contacted tech support for a PC OEM for anything other than hardware issues.  Having seen how qualified they are in general did not fill me with confidence in diagnosing something as potentially thorny as Windows… I’ve always thought the odds were better talking to my techie friends or compatriots or searching on the internet (when it became available as a mainstream resource) than trying to get help from someone who would think “BIOS upgrade” when the complaint was “my card reader won’t eject the card when I push it.”

YMMV, of course…

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/16GB & GTX1660ti, KDE Neon

Reply | Quote

just FYI – quite a lot (if not all) of manufacturers accepts laptops for RMAs with removed hard drive (failing hard drive would be the one exception… obviously) 😉

Reply | Quote

On the last 3 updates, including the one released yesterday, this note is included.

Windows Update Improvements
Microsoft has released an update directly to the Windows Update client to improve reliability. Any device running Windows 10 configured to receive updates automatically from Windows Update, including Enterprise and Pro editions, will be offered the latest Windows 10 Feature Update based on device compatibility and Windows Update for Business deferral policy. This does not apply to long-term servicing editions.

Sounds like as of yesterday, it’s still there ??

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

That would be the 16th release or so

1 user thanked author for this post.

HiFlyer

Reply | Quote

Any indication if there are new files – or new behaviors?

Reply | Quote

Not particular

it evolved from just fixing registry to restore tasks and fix drivers DB, and compatibilty for UAC management..

the main porpose or function did not change: re-allow blocked or disabled WU

1 user thanked author for this post.

HiFlyer

Reply | Quote

Sounds like they just fiddled a bit with good old KB 3035583 and – Voila!

1 user thanked author for this post.

HiFlyer

Reply | Quote

I am sure that this was a decision that had been agreed to in a meeting at Microsoft. The minds in the meeting had to have discussed the business need feeding the decision as well as the fallout it would produce. It appears they accepted that risk.

I wish I was a fly on the wall in an enterprise that got blindsided by this. There must be a lot of pent-up rage over it. It is Friday – the walls must be leaning in.

Home users find it frustrating especially when it takes 3 tries for the update to successfully complete. I have Pro but also a metered connection so my reaction was more like a flailing fish on a hook. Why have user preferences if they are not going to be honored?

I want Windows 10 to succeed, not because I like Microsoft, but because the OS is capable of providing value. In this case it is not the product that failed, it is the Overlords who broke a trust. They devalued the ‘service’. Their response to the [issue] was as feeble as the decision itself.

2 users thanked author for this post.

flackcatcher, Karlston

Reply | Quote

I’m flabbergasted not only at the practices they’ve invented to get people to use Windows 10, but also at the results and the fact that they keep doing the same things but they’re not expecting the same results.

Windows 10 really is a fantastic OS; as advertised, it really is the best release of Windows.

But it has baggage, number one. I’m most concerned about the lack of choice and control over updates, even though (knock on wood) this has not caused me issues (yet) on 1703 or 1709. Yes there are obviously other questionable things…telemetry collection and all the other “opt out” features, but stripping away all update control is asinine.
Number two, doing this type of stuff (forced updates, sticking “suggested apps” places and popping up ads or “recommendations”) is just really ticking people off and pushing them away.

MS needs to realize they are not the only game in town and haven’t been for years. Yes for the most part they are in enterprise, but even there depending on the environment, they’re ticking people off there too. Linux is no longer a command line rose bush full of black widow spiders and evil creatures. Mint and Ubuntu have done wonders for the usability (and decrease in difficulty) in installing and using Linux.

Right now, I’m a Win10 advocate. Again, so far, I haven’t had any problems on 1703 and 1709 since finally diving in head first several months ago. However, the minute something fruity happens, it will be dropped dead and I will go back to 7.

Reply | Quote

It may be safe to turn on update-relevant services again. However, the dust needs to settle first. The last thing we need is more time fighting an enforced update.

Meanwhile, it does seem to have been pulled from the update catalog

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4023057%20

Group A (but Telemetry disabled Tasks and Registry)
Win 7 64 Pro desktop
Win 10 64 Home portable

Reply | Quote

Since it has been explained to me what this was at least one plus year ago and the others like it which arrive, they have never been available for download from the update catalog.

Reply | Quote

It’s happened again and it’s pushing me to 1709. If I get sent to 1709, I’ll do the method said and return to 1703, but will I get the same message again about the upgrade?

https://support.microsoft.com/en-us/help/4023814/some-versions-of-windows-10-display-a-notification-to-install-the-late

Reply | Quote

Yes, it you roll back to 1703 it will keep happening unless you take the preventative measures. You have the link for Windows update Blocker Free. After you roll back, use to block the upgrade.

Reply | Quote

Possibly useful for some (untested – I now have update switched off and bad patches removed.)

https://www.askvg.com/fix-how-to-stop-automatic-forced-upgrade-to-feature-updates-in-windows-10/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+AskVG+%28AskVG%29

Group A (but Telemetry disabled Tasks and Registry)
Win 7 64 Pro desktop
Win 10 64 Home portable

1 user thanked author for this post.

bobcat5536

Reply | Quote

After updating earlier in the week, I was forced to put an image back on. I just tried again and so far so good. It didn’t install the Windows 10 Update Assistant ( YET ). I have all the regular Feb. updates done and set paused to 35 days before the March ones hit. It did not install KB4023814, but did install KB4023057. I went to uninstall it as recommended and it didn’t show up in the installed updates in Add/Remove. A lot of the updates it just installed didn’t show up.

I hope Woody was right in thinking it got yanked. I’ll watch it for a day or two and if it shows, I’ll use the reg file fix they gave in your article to kill it. ( Fingers Crossed )

Reply | Quote

Still there, it was pushed out to my system last night, trashed my monitor driver and now it wont let me reinstall it. Ignores the driver even though it installs and now many other device and performance issues. System just crashed.

My nice 4K monitor now rendered useless.

Thanks Microsoft, wonderful job you are doing alienating even your best supporters with this forced alpha testing process.

4th time in 2 months ive had to spend days, rebuilding, reinstalling troubleshooting your pushed and buried updates you cant find, fix or remove. Bye.

Reply | Quote

Woody, Maybe you can set up a poll about what folks think about Win 10? Would be interesting to see the outcome. Thanks!

Reply | Quote

Just checking (w/wushowhide) for new updates to hide on Windows 10 1709, and noticed MS has issued a new 2018-06 version of KB4023057.

This may nave been mentioned elsewhere, but I just thought I would add it to this thread.

Hid.  Again.

Windows 10 Pro 22H2

1 user thanked author for this post.

bjm

Reply | Quote

Received the KB4023057 update on 7/6/2018, Toshiba Satellite laptop, Windows 10 Pro version 1709, build 16299.492.

Through Group Policy I have “notify first, and ask to download and install updates” enabled.

Some of the new processes must have been thrown into an endless loop, as all laptop processing slowed to a crawl. A rollback fixed the problem.

This is the first update to Windows 10 to have caused any problems on this machine.

Anyone else encounter this?

millipede2

Reply | Quote

KB4023057 is not a Cumulative Update. It is the Remediation Shell and has to do with Win10 Upgrades. See @abbodi86 ‘s description here. I’m wondering if what you experienced was an attempted forced upgrade to v1803. If it was downloading and attempting an install, that would explain the slowing of your conputer.

Reply | Quote

Thanks, yes, I know the description. Since the update is supposed to facilitate automatic updates, it may conflict with the Group Policy override of automatic installs. But if it is trying to force to the next version, and so interfering with functionality, that would be totally unacceptable. While there have been earlier reports of forced updates, I saw no indications that it was doing that. Many users, especially IT managers, set Group Policy to notify and approve updates first, in order to review, install and test before proceeding. If this update conflicts with that, then it needs to be fixed. But if other users have encountered a similar problem, and another explanation, and a workable way and reason to install this update, it would be good to know.

Anyway, for now, I’ll skip this update and proceed with later ones and see how that goes.

Reply | Quote

As a general rule now, I hide all Win 10 updates, except for the Cumulative Updates, Flash updates, and MSRT.

MS seems to keep re-releasing those upgrade facilitation patches, so even if you have hidden them once, you have to keep checking and hide them every time they appear again.

I have automatic updates disabled by group policy, so when I manually click on “Check for updates”, I will download and install everything that is NOT hidden.  I can control what and when that way.  I just make sure that these “other” patches stay hidden.

Running Win 10 Pro 1709.

Windows 10 Pro 22H2

Reply | Quote

JohnW, thanks, this is good advice how to proceed. KB4023057 was the first update to cause a problem for me, and I was unfamiliar with the tool to hide updates. I hid it, and went on to install the next cumulative update, KB4284822. Everything is now working well.

Reply | Quote

I’m not sure blaming KB 4023057 for forced updates to 1709 is valid because I JUST RECEIVED this patch TODAY but I’ve been on 1709 for months.

Reply | Quote