KB890830 Windows Malicious Software Removal Tool x64 - v5.106
EcoStruxure Geo SCADA Expert Forum
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2023-05-1805:46 AM
KB890830 Windows Malicious Software Removal Tool x64 - v5.106
In October 2022 the 890830 KB/Update was approved for GeoSCADA Expert 2021, but in the following months Microsoft continues to update the version (latest v5.113 as of May 2023) but with the same KB number. However, I don't see any further testing/approvals by GeoSCADA on later versions. Is further testing going to be done on this KB or is it safe for us to assume that since the KB number is the same that the updated versions are safe as well?
Link copied. Please paste this link to share this article on your social media post.
Posted: 2023-05-1906:00 AM
The MSRT is 'built in' to windows and MS appear to use the KB number to refer to updates to it. A patched Windows includes any updates to MSRT and the tests performed are on fully patched Windows.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2023-05-1908:01 AM. Last Modified: 2023-05-1909:32 AM
Ok, I guess I didn't realize that since it was only called out one time in the approved updates. In WSUS it is a separate approval each time for the newer versions even though the KB is the same number. I just didn't want to approve it for install since it was specifically called out in the MS Update testing sheet by version number and newer versions were not there.