![\"Windows](\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2015\/02\/Update.jpg\" "\\"Update\\"")
Im Umfeld des Dezember-Patchday (13. Dezember 2016) hat Microsoft eine Reihe von Security Bulletins aus dem Oktober und November mit einer neuen Revisionsnummer versehen. Hier ein paar Infos dazu.<\/p>\nIm Umfeld des Dezember-Patchday (13. Dezember 2016) hat Microsoft eine Reihe von Security Bulletins aus dem Oktober und November mit einer neuen Revisionsnummer versehen. Hier ein paar Infos dazu.<\/p>\n
<\/p>\n
Microsoft gibt folgende Security Bulletins an, denen am 9. Dezember 2016 eine neue Revisionsnummer zugewiesen wurde.<\/p>\n
Oktober
* MS16-118 – Critical
* MS16-120 – Critical
* MS16-122 – Critical
* MS16-123 – Important
* MS16-124 – Important
* MS16-126 – Moderate<\/p>\n
November
* MS16-130 – Critical
* MS16-131 – Critical
* MS16-132 – Critical
* MS16-134 – Important
* MS16-135 – Important
* MS16-137 – Important
* MS16-138 – Important
* MS16-139 – Important
* MS16-140 – Important
* MS16-142 – Critical<\/p>\n
Der Grund f\u00fcr die Revision ist eine ge\u00e4nderte Detektion im Supersedence-Schema f\u00fcr Rollups, die per WSUS oder SCCM verteilt werden. Ich hatte im Blog-Beitrag Neues Update-Schema f\u00fcr Windows 7\/8.1\/Server ab Dezember 2016<\/a> \u00fcber diese \u00c4nderung berichtet. Microsoft hat noch folgende Details zu den Revisionen mitgeteilt und dort auch die betroffenen Updates genannt: <\/p>\n – Reason for Revision: V2.0 (December 9, 2016): Revised bulletin Revisions to bulletins released in November<\/p>\n – Reason for Revision: V2.0 (December 9, 2016): Revised bulletin Die genannten Updates d\u00fcrften also im WSUS erneut auftauchen. Diese enthalten dann die ge\u00e4nderten Metadateien f\u00fcr die \u00fcberarbeitet Supersedence-Logik. <\/p>\n \u00c4hnliche Artikel:<\/strong> Im Umfeld des Dezember-Patchday (13. Dezember 2016) hat Microsoft eine Reihe von Security Bulletins aus dem Oktober und November mit einer neuen Revisionsnummer versehen. Hier ein paar Infos dazu.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[185,301],"tags":[4315,4325],"class_list":["post-185006","post","type-post","status-publish","format-standard","hentry","category-update","category-windows","tag-update","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/185006","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=185006"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/185006\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=185006"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=185006"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=185006"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
to announce the following updates have been rereleased with a
detection change that addresses a supersedence issue that
certain customers experienced when attempting to install the
October Security Only updates.
–Security Only update 3192391<\/strong> for all supported releases of
Windows 7 and Windows Server 2008 R2<\/strong>. For more information,
see Microsoft Knowledge Base Article 3192391.
–Security Only update 3192393 for Windows Server 2012<\/strong>. For
more information, see Microsoft Knowledge Base Article 3192393.
–Security Only update 3192392 for Windows 8.1 and Windows
Server 2012 R2<\/strong>. For more information, see Microsoft Knowledge
Base Article 3192392.
These are detection changes only. There were no changes to the
update files. Customers who have already successfully installed
any of these updates do not need to take any action. For more
information, see the Microsoft Knowledge Base article for the
respective update.
– Originally posted: October 11, 2016
– Updated: December 13, 2016
– Version: 2.0<\/p>\n
to announce the following updates have been rereleased with a
detection change that addresses a supersedence issue that
certain customers experienced when attempting to install the
November Security Only updates.
–Security Only update 3197867<\/strong> for all supported releases of
Windows 7 and Windows Server 2008 R2<\/strong>. For more information,
see Microsoft Knowledge Base Article 3197867.
–Monthly Rollup 3197868<\/strong> for all supported releases of
Windows 7 and Windows Server 2008 R2<\/strong>. For more information,
see Microsoft Knowledge Base Article 3197868.
–Security Only update 3197876 for Windows Server 2012<\/strong>.
For more information, see Microsoft Knowledge Base Article
3197876.
–Monthly Rollup 3197877 for Windows Server 2012<\/strong>. For more
information, see Microsoft Knowledge Base Article 3197877.
–Security Only update 3197873 for Windows 8.1 and Windows
Server 2012 R2<\/strong>. For more information, see Microsoft Knowledge
Base Article 3197873.
–Monthly Rollup 3197874 for Windows 8.1 and Windows Server
2012 R2<\/strong>. For more information, see Microsoft Knowledge Base
Article 3197874.
These are detection changes only. There were no changes to the
update files. Customers who have already successfully installed
any of these updates do not need to take any action. For more
information, see the Microsoft Knowledge Base article for the
respective update.
– Originally posted: November 11, 2016
– Updated: December 13, 2016
– Version: 2.0<\/p>\n
Neues Update-Schema f\u00fcr Windows 7\/8.1\/Server ab Dezember 2016<\/a>
Microsoft Patchday 11. Oktober 2016<\/a>
Microsoft Patchday 8. November 2016<\/a>
Updates KB3207752, KB3205394 (Windows 7) und KB3205401, KB3205400 (Windows 8.1)<\/a>
Windows 10: Dezember 2016 Updates (KB3205383, KB3205386, KB3206632)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"