Hello,
We recently deployed a fleet of 400 workstations running Windows 10 version 2004. The WUA component of WAPT is no longer functioning correctly. Updates are detected in the "Windows Update List," and after scanning for Windows updates on the workstations, the WAPT agent indicates pending updates, but there are no options for installing, declining, pending, or critical updates. The workstations remain in "pending updates" without any prompt to install them.
We created a WUA package with the updates we authorized, but even pushing this package doesn't change the status of the workstations, which remain in "pending update" and ultimately end up with an "Error" status for an unknown reason.
One last thing: there is no update menu for Office 2019.
On a test workstation running version 1909, there are no issues; updates are managed correctly, and the workstation is updated by WUA.
Could we have missed a step? Or, is this a bug related to Windows 10 version 2004? I saw some posts on the forum about it.
Thank you for your feedback.
********
Wapt: 1.8.2 (latest server and client version)
Debian 10.
Windows 10 x64 r.2004
[SOLVED] WUA with Win X v.2004
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
indeed the bug in Windows 10 version 2004 is still present.
We are in contact with Microsoft, and the problem definitely originates on their end.
We were supposed to receive a patch (a KB update) last week, but Microsoft has fallen behind schedule.
Microsoft has now announced a release date for this patch: August 27, 2020. When it is available, it will be installable with a WAPT package that we will put on the Microsoft Store.
Regarding Office 2019, Microsoft has also changed its operating method; Office 2019 updates are no longer managed by the Windows Update agent (and therefore no longer managed by the WSUS server either). More information: https://social.technet.microsoft.com/Fo ... e2016ITPro
This will therefore need to be managed with a WAPT package.
Sincerely,
Simon Fonteneau
indeed the bug in Windows 10 version 2004 is still present.
We are in contact with Microsoft, and the problem definitely originates on their end.
We were supposed to receive a patch (a KB update) last week, but Microsoft has fallen behind schedule.
Microsoft has now announced a release date for this patch: August 27, 2020. When it is available, it will be installable with a WAPT package that we will put on the Microsoft Store.
Regarding Office 2019, Microsoft has also changed its operating method; Office 2019 updates are no longer managed by the Windows Update agent (and therefore no longer managed by the WSUS server either). More information: https://social.technet.microsoft.com/Fo ... e2016ITPro
This will therefore need to be managed with a WAPT package.
Sincerely,
Simon Fonteneau
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
For your information, we have new information from Microsoft.
We were able to preview KB4571744, and it does indeed resolve the issue.
When the KB is officially released by Microsoft, we will publish a WAPT package on our store that will allow users to install it.
We were able to preview KB4571744, and it does indeed resolve the issue.
When the KB is officially released by Microsoft, we will publish a WAPT package on our store that will allow users to install it.
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
The cumulative update has been available for download on the MS Update Catalog for a few days now. But it should arrive naturally tomorrow, the second Wednesday of the month, with Patch Tuesday 
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hello,
You can now deploy the KB via the following package to resolve the WUA issue.
https://store.wapt.fr/store/tis-kb4571744
Regards,
Jimmy
You can now deploy the KB via the following package to resolve the WUA issue.
https://store.wapt.fr/store/tis-kb4571744
Regards,
Jimmy
