Windows 10: KB4023814 Windows 10 display notification to install latest version

Source: https://support.microsoft.com/en-us/...stall-the-late



Tip How to Find Windows 10 Version Number


:)

 

Windows 10 keeps freezing

The update in question is "update to Windows 10 version 1607 for x64 based systems (KB4023814)"

 

Windows10 Update Assistant and KB4023814

How do I uninstall the Windows 10 Update Assistant?

　

Microsoft Support states:

"To help keep all Windows 10 systems secure and to provide the latest features and improvements, the Windows 10 Update Assistant downloads and starts the installation of the latest version of Windows 10. The Windows 10 Update Assistant will be deployed to
Windows 10 PCs that have not yet had the latest update installed."

　

I am running Windows 10 version 1511.

I am NOT ready to update to a newer version due to a compatibility issue.

I believe it was installed on my computer 9-28 in KB4023814.

　

KB4023814 cannot be found in programs and features - uninstall updates, or the Microsoft support page for Windows 10 Update History. It used to be in my update history. Searching it in Microsoft Support results in only one article which warns users of end
of service on versions 1507 and 1511, hence why I believe the assistant was installed through this update.

I hid version 1607 through the Windows show or hide updates, but cannot find version 1703 to hide.

　

In an attempt to keep the assistant from installing the newest version I've disabled the Windows Update service and cleared some catches and system files, most notably the download and delivery optimization files in the software distribution folder.

Unfortunately this must have cleared too much information. Now there are no files in my update history or in the Windows show or hide updates. The uninstall updates seems intact, but it doesn't matter since KB4023814 couldn't be found there anyway. It is
unclear if version 1607 is still hidden.

　

I am thinking about setting my WiFi to a metered connection to further block the update, but am unsure of other issues that may arise from doing so. This last step may be a redundancy anyway since disabling the update service should be enough to block it.

 

Hi,
Sort of funny the newest version is 1709 so obviously 1607 and 1703 are indeed eol *Smile

 

Woody Leonhard waxed wroth, but not profane, on this behavior over at ComputerWorld. His story on that topic is well worth a once-over: Microsoft again forced upgrades on Win10 machines specifically set to block updates. He is pretty ticked off about this, and if readers' comments on that story are any indication, lots of other folks aren't terribly happy about it, either.
--Ed--

 

Hi,
Thought his opinions were banned from tenforums and links to them *Smile

 

KB4023814 doesn't just download and install the Update Assistant, it also schedules tasks to run it at boot and every three days at a set time. Also, the setup files for the Update Assistant are retained, so if you uninstall it the Update Assistant will be reinstalled from the local files.

For those who got KB4023814 despite deferring Features Updates, the changes it makes can be undone before it has a chance to complete the update to 1709, you don't have to wait for the install then roll back.

KB4023814 has been around for a while now, this post from the end of January show the steps to take.

Block Windows 10 update assistant/all updates

I have used it successfully on my test/support machine (the one that has images for all versions of Win10) to keep it from updating itself when running the older images.

I think MS is pushing 1709 so... err... 'enthusiastically' even onto 1703 is for the reasons stated "....they must be updated to the latest versions of Windows 10 to ensure protection from the latest security threats". There's been some really nasty stuff recently and perhaps 1709 is the only version that is equipped to deal with it?

 

Bree: KB4023814 doesn't just download and install the Update Assistant, it also schedules tasks to run it at boot and every three days at a set time. Also, the setup files for the Update Assistant are retained, so if you uninstall it the Update Assistant will be reinstalled from the local files.

You tried helping the OP and I in this thread - Problems with Windows 10 Update KB4023057 -
I did a couple Teamviewer sessions with her since she was somewhat local and found out that the reason she did not get 1703 or 1709 is that she was on 10 Pro with Upgrades blocked for 365 days. But the Update Assistant designed to prod you into Upgrading was insidious, as in Brink's post 1 article; could not be uninstalled, immediately on every boot tried to install Upgrade again even with Win10 Update folder and Software Distribution contents deleted, WU, bits and Modules Installer disabled, etc. Last gasp tried your link- Block Windows 10 update assistant/all updates
This worked to the point where it intermittently send out a white window message that latest security, blah, blah window opens and tries to download but we kill it by hitting Hide so restart is not held up and device runs at normal speed now. Just waiting on 1803 now to start over fresh. Just a painful override of Pro's option to delay Upgrades !

 

...so we did...

That may be because that's not where the install files for the Update Assistant hide, they're in C:\WINDOWS\UpdateAssistant and it reinstalls from there if you uninstall it. See the post I linked to earlier for how to remove it all, it worked for my test machine.

 

Not sure when this came out, but I think it's a recent addition...

https://support.microsoft.com/help/4...07-1511-and-16

*Arrow End of servicing notification Windows 10 Versions 1507, 1511, 1607 - Windows 10 Forums

 

Thanks, Bree. Saw this in the News section and forwarded to the member that we helped. We finally got the latest update installed and by deleting the scheduled Update Assistant tasks and blocking WU, everything is running perfectly. I'll have her just dismiss this screen until 1803 is ready to install. Cheers.

 

So it is (now) *Smile I think Brink picked up on my post above (as I hoped he would) and posted a proper News announcement.

It seems less 'pushy' than KB4023814, just a full screen announcement for each user a/c at their first sign in after it has installed. It also appears in the list of updates that can be uninstalled.

 

Surprise! A new version of the Windows Update block-buster KB 4023057

Posted on March 23rd, 2018 at 07:42 woody Comment on the AskWoody Lounge
While scanning through the KBNew list, I bumped into an old f(r)iend, KB 4023057. Looks like it was re-issued on March 22 — along with about half a gazillion patches for Windows.
KB 4023057, if you don’t recall, is the patch that’s credited with busting through PC's that have Windows Update blocked. There’s a discussion here, with this description from abbodi86:

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

the main purpose or function did not change: re-allow blocked or disabled WU"
Of course, Microsoft’s official description is the usual “Nothing to see here, folks” drivel:

This update includes reliability improvements that affect the update service components in Windows 10 Versions 1507, 1511, 1607, and 1703.
This update includes files and resources that address issues that affect the update processes in Windows 10. These improvements ensure that quality updates are installed seamlessly on your device and help to improve the reliability and security of devices running Windows 10. When Windows update is available for your device, devices that do not have enough disk…
Only certain builds of Windows 10 Versions 1507, 1511, 1607, and 1703 require this update. Devices that are running those builds will automatically get the update downloaded and installed through Windows Update.
This update is also offered directly to Windows Update Client for some devices that have not installed the most recent updates. This update is not offered from the Microsoft Update Catalog.
I just wish Microsoft could speak plainly. In this case, some Win10 users (not sure which ones) are getting a patch that (apparently?) breaks their wuauserv settings. I assume that its entire reason for existence is to push more people onto the next version of Win10.

 

Hello Guys

Here an Easyfix for you or Customers:

Its a Scheduled Task from Microsoft in Microsoft\Windows\Setup\EOSNotify

do a new TaskScheduler with this options:

Program Script: C:\Windows\system32\schtasks.exe

argument: /change /TN "Microsoft\Windows\Setup\EOSNotify" /disable

We had this on Enterprise Versions and we fixed well like this.

Have a nice day

Greets