The following is even simpler: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection] "AllowTelemetry"=dword:00000000 "DisableOneSettingsDownloads"=dword:00000000 Firewall > Allow "mousocoreworker.exe" and "taskhostw.exe" and reboot. Edit to fix a typo.
In my case changing only "DisableOneSettingsDownloads" from 1 to 0 did the trick and now the EoS message is finally gone! Edit: and the "culprit" for that as someone else earlier said was indeed the O&O ShutUp 10++ which have the Disable downloading of OneSettings configuration settings (User behavior settings) as recommended to disable.
many thanks it solve the issue on LTSC 2021... EDIT : I tried also on 22H2, but it doesn't solve the issue, but it must be different problem...got ESU activated on 22H2...
Just noticed that after "solving" the EOS message issue then the following error appears at every boot. Spoiler: Event ID 86 Log Name: Application Source: Microsoft-Windows-CertificateServicesClient-CertEnroll Date: 19/10/2025 11:42:28 Event ID: 86 Task Category: None Level: Error Keywords: Classic User: SYSTEM Computer: Description: SCEP Certificate enrollment initialization ... failed GetCACaps GetCACaps: Not Found Has anyone else experienced this after getting rid of the EOS message? After restoring a previous image that error just disappeared. Edit to remove useless data.
To remove the EOS-Message you can just insert "ESODATESTRING":"2055-10-15T00:00:00", before "DISABLEIMAGESONTOASTS":"True" which is the last entry in the file C:\ProgramData\Microsoft\Windows\OneSettings\UsoSettings.json The 3 last entries in my system are: "INSTALLCALLBACKTIMEOUTINMS":"14400000","ESODATESTRING":"2055-10-15T00:00:00","DISABLEIMAGESONTOASTS":"True"}}
Thank you very much, I had tried all the previous methods, and none of them had worked for me, and I had to make this modification that you indicate in the UsoSettings.json file, and without even restarting, the message disappeared.
Thanks yet again good people! Obviously, there are a few things that could trigger the No Update/EOS problem with Windows 10 IoT Enterprise LTSC 21H2 x64. In my case it was the O&O ShutUp thing. All I had to do was go into O&O, search for OneSettings, then disable it. In O&O, it is under Local Machine/User Behavior/. Problem is instantly fixed, even without a reboot. Then I rebooted anyway to test. Still good and no error messages. Thanks to all here! Edit: I will say that the OneSetting option is an O&O Recommended setting, their "safest", most recommended level. This means a lot of people will have this issue. You can click in the software there to get a writeup of what that setting does. We will see how O&O handles this going forward.
I just solved the Event ID 86 error caused by the EOS message removal procedure by performing the following workaround. I extracted the "C:\ProgramData\Microsoft\Windows\OneSettings" folder (which was previously empty, but after the procedure filled up with 11 files) from the image file and copied it to the image before the procedure. Then I deleted all the files inside it except both "config.json" and "UsoSettings.json". After doing this, the EOS message disappears even on the previous image, and so does the Event ID 86 error too. What I like most is that the above solves the EOS issue without making any other changes to your machine, not even the firewall.
To get rid of the incorrectly shown EOS message on 2021 LTSC (if it still is not fixed like on x86) I would just use the vivetool or registry version: https://forums.mydigitallife.net/posts/1894118 If people running "privacy" tools could test this too.
Windows 10 IoT Enterprise LTSC 2021 x64 installed through the original "Slimdown10.cmd" here. Just tested both ways. ViveTool command does work without restart Windows. Registry "FeatureManagement\Overrides\8\3108581004" does not work even restarting Windows.
How many times will we see that sentence about using the slimdown10.cmd? The shown registry keys are the keys changed by vivetool.
I'm doing so to provide accurate information for readers who only read this post and not my previous ones. You were the one who mentioned "privacy" tools, so sorry if I just provide the results you requested. Is there a problem with "Slimdown10" that I'm unaware of? While I couldn't care less about mentioning "Slimdown10"; I can - for what it's worth - only thank the author for his excellent work.
If what you say is correct, and I certainly have no reason to doubt it, so there must be something else in ViveTool job, since I've done the test with great accuracy.
Please note that I hate to point this out, but my experience here is very different. What I've observed here, where the Slimdown10 batch file has disabled, deleted, and prevented the installation of a huge amount of data compared to a regular clean install, is that the following ViveTool command changes only 1 entry in the Windows Registry. "ViVeTool /disable /id:48796508" From this one Code: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\HostActivityManager\CommitHistory\Microsoft.Windows.Search_cw5n1h2txyewy!ShellFeedsUI] "Mixed"=hex(b):49,16,d0,02,00,00,00,00 to this one Code: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\HostActivityManager\CommitHistory\Microsoft.Windows.Search_cw5n1h2txyewy!ShellFeedsUI] "Mixed"=hex(b):0b,a8,36,03,00,00,00,00 and I can confirm that it works without restarting Windows, even by simply manually adding it to the registry by double-clicking the attached ".reg" file without run ViveTool at all.
In other words, please note that the following entries seem unrelated to ViveTool's job, at least here. Code: reg add "HKLM\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3108581004" /v "EnabledState" /t REG_DWORD /d "1" /f reg add "HKLM\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3108581004" /v "EnabledStateOptions" /t REG_DWORD /d "0" /f https://forums.mydigitallife.net/posts/1894118 Edit to add: I can confirm one more time that the above entries, at least here, do not work.