Entry type: FAQ, Entry ID: 18752994, Entry date: 06/25/2015

Which Microsoft Patches ("Security Patches" and "Critical Patches") have been tested for compatibility with SIMATIC WinCC?

  • Entry
  • Associated product(s)
Microsoft regularly rectifies security gaps in its products and makes these fixes available to its customers in the form of official patches.

These updates/patches are usually issued every second Tuesday in the month, on so-called "Patch Tuesday". Microsoft divides up the updates into numerous different classifications:


However, you only have to install "Security Patches" and "Critical Patches" to ensure that SIMATIC WinCC operation is secure and stable. For this reason, a WinCC test configuration has been set up in order to test the compatibility of the WinCC software with the above-mentioned patch classifications ("Security Patches" and "Critical Patches"). This system always features the very latest of the released versions of WinCC and Microsoft products released for operating these versions of WinCC. Keeping pace with the updates published by Microsoft, compatibility tests with the latest released versions of WinCC are performed on the test system.
The attached table in xls format provides precise information about the Microsoft "Security Patches" and "Critical Patches" which are tested for compatibility. As far as possible, this is updated within two weeks after publication of the latest updates of the named classifications.
It reflects the Microsoft products installed in the WinCC test configuration. Therefore, a discrepancy between this list and the products installed in the project cannot be excluded. If a system requires more updates than contained in the published list, these updates are requested according to the additional installed products / software components. In this case, it is up to the user to install these updates.
We recommend installing all the available updates of both the named classifications to ensure that the system is protected.
However, we cannot say anything about the compatibility of such updates that we have not tested. Therefore, we recommend installing all the updates in separate project-specific test environment prior to rolling out the updates in the productive environment.

Excel file
Registration required security_patches.xls (805.5 KB)

Packed XML and model files
Registration required security_patches_xml.zip (73.1 KB)

In rare cases an update might have a negative effect on our software in our tests. This is noted in the "Comment" field in the list above. Furthermore, we inform you as fast as possible by newsletter of any indications and the resulting remedies.

Recommended procedure for patch management with the Microsoft Windows Server Update Service (WSUS)
These instructions assume that you have a WSUS installed for your WinCC plant. How to proceed with the WSUS is described in Entry ID: 38621083.

No. Procedure
1 WSUS configuration
In the "Products and Classifications" dialog you select the "Products" tab and then all the Microsoft products relevant for the plant.
2 WSUS configuration
In the "Products and Classifications" dialog you select the "Classifications" tab and then "Definition Updates", "Security Updates" and "Critical Updates".

Fig. 01

3 WSUS configuration
Create the project-specific groups for distribution of the updates in the plant.
4 Download the "Security_Patches.xls" Excel table above onto your computer.
5 Open the table and set the filter to "Failed" in the "Test Result" column.
6 Check the "Comments" column to see whether these updates have been replaced.
7 WSUS administration
Select all the available updates in the "Critical Updates" and "Security Updates" categories and then deselect the non-released patches as in the list above. Release the patches for installation in the groups created.
8 Log in on the clients connected to the WSUS using an administrative account (the clients were configured to receive the updates from the WSUS).
9 Execute the updates offered.

You can find more precise information about Industrial Security in connection with WinCC software in the WinCC Security Concept in Entry ID: 60119725.
For more detailed explanations about Microsoft Updates and the WSUS visit the following Microsoft sites.


  • To find out which Microsoft Patches are installed on the PC, refer to Entry ID: 48844294.
  • These guidelines apply only for WinCC V6.0 SP4 and higher.

The procedure described above does not apply for new Microsoft Service Packs which still require an explicit release for use. If the patches require a higher version of the Microsoft software, then refer to the "WinCC Install Notes" or Entry ID 21927773, to check whether these higher versions of the software or Service Packs are released for SIMATIC WinCC.

Additional Keywords
Windows Update Service, Security Patch