{"id":202476,"date":"2018-03-22T19:35:35","date_gmt":"2018-03-22T18:35:35","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=202476"},"modified":"2023-06-02T08:35:57","modified_gmt":"2023-06-02T06:35:57","slug":"windows-10-updates-zum-22-mrz-2018","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2018\/03\/22\/windows-10-updates-zum-22-mrz-2018\/","title":{"rendered":"Windows 10 Updates zum 22. M&auml;rz 2018"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2015\/01\/win102.jpg\" width=\"58\" align=\"left\" height=\"58\"\/>[English]Microsoft hat zum 22. M\u00e4rz 2018 eine Reihe kumulativer Updates f\u00fcr Windows 10 freigegeben. Hier eine \u00dcbersicht, was verf\u00fcgbar ist und was es sonst zu wissen gibt. <\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/ssl-vg03.met.vgwort.de\/na\/3202ce97bd4d457daff510f2dd7e0acf\" width=\"1\" height=\"1\"\/>Als ich am Dienstag nach Updates suchte, wurde ich nicht f\u00fcndig. Danke an <a href=\"https:\/\/twitter.com\/PhantomofMobile\" target=\"_blank\" rel=\"noopener noreferrer\">Crysta T. Lacey<\/a> f\u00fcr den Hinweis. <\/p>\n<h2>Update KB4089848 f\u00fcr Windows 10 Version 1709<\/h2>\n<p>Update <a title=\"https:\/\/support.microsoft.com\/de-de\/help\/4089848\/windows-10-update-kb4089848\" href=\"https:\/\/support.microsoft.com\/de-de\/help\/4089848\/windows-10-update-kb4089848\" target=\"_blank\" rel=\"noopener noreferrer\">KB4089848<\/a> wurde am 22. M\u00e4rz 2018 f\u00fcr Windows 10 Fall Creators Update (Version 1709) (erneut) freigegeben. Es handelt sich also um ein Re-Release des Pakets, welches bereits am 13. M\u00e4rz 2018 freigegeben wurde (siehe <a href=\"https:\/\/borncity.com\/blog\/2018\/03\/14\/patchday-windows-10-updates-13-mrz-2018\/\" target=\"_blank\" rel=\"noopener noreferrer\">Patchday: Windows 10-Updates 13. M\u00e4rz 2018<\/a>). Das Update enth\u00e4lt Qualit\u00e4tsverbesserungen, wobei folgendes adressiert wird.<\/p>\n<ul>\n<li>Addresses issue with a GDI handle leak in the Windows Ribbon control.  <\/li>\n<li>Addresses issue where users can't select <strong>OK<\/strong> after entering credentials in command line on Windows Server version 1709.  <\/li>\n<li>Addresses issues where Bluetooth devices fail to receive data after a restart.  <\/li>\n<li>Addresses issue where, during BitLocker decryption or encryption of a drive, files protected with the Encrypting File System (EFS) may become corrupted.  <\/li>\n<li>Addresses issue where the server may occasionally encounter an error during file transfer. The error is \"Stop D1 in tcpip!TcpSegmentTcbSend\".  <\/li>\n<li>Addresses issue where an iSCSI RESET might trigger a cluster failover.  <\/li>\n<li>Addresses issue in MPIO where pass-through SCSI requests might lead to a stop error if the disk is pending removal.  <\/li>\n<li>Addresses issue where processing of group policies may fail, and policies may be removed as a result. This occurs if the length of the Windows Defender Firewall policy rule exceeds 260 characters.  <\/li>\n<li>Addresses issue caused by a new privilege in Windows Server 2016 and Windows 10 version 1709 named \"Obtain an impersonation token for another user in the same session\". When applied using Group Policy to those computers, <strong>gpresult \/h<\/strong> fails to generate reporting data for any setting configured by the Security Configuration Engine (SCE) extension. The error message is \"Requested value 'SeDelegateSessionUserImpersonatePrivilege' was not found\". The Group Policy Management Console fails to show the privilege in the Settings tab for a GPO where the setting has been configured.  <\/li>\n<li>Addresses issue where errors may occur when accessing WebDAV files or folders on a SharePoint site if the file or folder name contains multibyte characters.  <\/li>\n<li>Addresses issue where the Remote Desktop License report gets corrupted when it exceeds the 4 KB size limit.  <\/li>\n<li>Addresses issue where an Azure point-to-site VPN connection that uses IKEv2 may fail when the user's device contains a large number of trusted root certificates<em>.<\/em>  <\/li>\n<li>Addresses rendering issue in Microsoft Edge for PDF documents with backgrounds created using various third-party publishing tools.  <\/li>\n<li>Addresses issue where a media platform stops responding when changing cameras rapidly on a device.  <\/li>\n<li>Addresses issue where a media platform stops responding, which affects media playback in Microsoft Edge, Internet Explorer, and Microsoft PowerPoint.  <\/li>\n<li>Addresses issue with spatial audio when used in connection to Dolby Atmos for Headphones.  <\/li>\n<li>Addresses issue where a credential prompt that requires administrative privileges appears when a standard user account performs the first logon to a Windows 10 device that has been deployed using Windows Autopilot.  <\/li>\n<li>Addresses issue where tiles in the <strong>Start <\/strong>menu aren't preserved when upgrading from Windows 10 version 1607 to Windows 10 version 1709.  <\/li>\n<li>Addresses issue with Spell Check and custom dictionaries.  <\/li>\n<li>Addresses issue with the press and hold feature when using a pen in Tablet mode.  <\/li>\n<li>Addresses issue with editing web password fields using a touch keyboard.  <\/li>\n<li>Addresses issue where some Bluetooth card readers don't work after a restart.<\/li>\n<\/ul>\n<p>Ein Quercheck der gefixten Punkt zeigt, dass da einige Klopper dabei sind. Vom GDI Handle Leak im Ribbon-Steuerelement von Windows \u00fcber Bluetooth-Probleme, beim Upgrade nicht \u00fcbernommenen Startmen\u00fc-Eintr\u00e4gen bis hin zu Fehlern, die das Versagen von Gruppenrichtlinien bewirken, ist alles dabei. <\/p>\n<p>Das Update wird automatisch \u00fcber Windows Update verteilt, steht aber auch im <a href=\"http:\/\/catalog.update.microsoft.com\/v7\/site\/Search.aspx?q=KB4089848\">Microsoft Update Catalog<\/a> zum Download und zur manuellen Installation zur Verf\u00fcgung. Das Update hebt Windows auf die OS Build 16299.334. <\/p>\n<blockquote>\n<p>Das Paket wird auch f\u00fcr Windows Server 2016 (V1709) bereitgestellt. Bei kumulativen Updates wird nur das installiert, was in vorhergehenden Updates noch nicht installiert wurde. <\/p>\n<p><strong>Wichtig <\/strong>Wenn Sie sowohl die SSU- (Servicing Stack Updates) als auch die LCU-Updates (Latest Cumulative Updates) \u00fcber den Microsoft Update-Katalog installieren, sollten Sie die SSU-Updates vor den LCU-Updates installieren.<\/p>\n<\/blockquote>\n<h3>Und hier klemmt es noch<\/h3>\n<p>Unsch\u00f6n ist der Umstand, dass Microsoft es seit Monaten nicht geschafft hat, den Fehler 0x80070643, der bei der Update-Installation gemeldet wird, auszumerzen. Der Bug bewirkt, dass das Paket im Updateverlauf als bei der Installation fehlgeschlagen aufgef\u00fchrt wird. Aber das Paket ist installiert. Microsoft fordert die Nutzer seit Monaten auf, nach der Updateinstallation erneut nach Updates suchen zu lassen. Wird nichts gefunden, soll man daraus schlie\u00dfen, dass das Update installiert wurde. <\/p>\n<p>Erg\u00e4nzung: Zweite Baustelle in Punkto bekannte Probleme gilt folgendes &#8211; F\u00fcr Benutzer mit Windows 10, Version 1709 Enterprise, die das Deltapaket vom Januar 2018 installiert haben, schl\u00e4gt m\u00f6glicherweise die Installation der Updates vom Februar und M\u00e4rz 2018 \u00fcber den Microsoft Update-Katalog fehl. Insbesondere kann die Installation des Deltaupdates vom Februar f\u00fcr Windows 10, Version 1709, fehlschlagen.<\/p>\n<p>Microsoft ist dieses Problem bekannt und hat deshalb am 13. M\u00e4rz 2018 die folgenden Deltaupdate-KBs f\u00fcr Windows 10, Version 1709, im Microsoft-Katalog als veraltet gekennzeichnet: <\/p>\n<ul>\n<li><a href=\"https:\/\/support.microsoft.com\/de-de\/help\/4056892\" target=\"_blank\" rel=\"noopener noreferrer\">KB4056892<\/a> \u2013 Januar 2018<\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/de-de\/help\/4074588\" target=\"_blank\" rel=\"noopener noreferrer\">KB4074588<\/a> \u2013 Februar 2018<\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/de-de\/help\/4088776\" target=\"_blank\" rel=\"noopener noreferrer\">KB4088776<\/a> \u2013 M\u00e4rz 2018<\/li>\n<\/ul>\n<p>Microsoft empfiehlt Benutzern, das Deltaupdatepaket KB4056892 vom Januar f\u00fcr Windows 10, Version 1709, zu deinstallieren und das vollst\u00e4ndige neueste kumulative Update vom M\u00e4rz 2018, <a href=\"https:\/\/support.microsoft.com\/de-de\/help\/4088776\" target=\"_blank\" rel=\"noopener noreferrer\">KB4088776<\/a>, zu installieren. Die Kunden k\u00f6nnen weiterhin Deltaupdatepakete mit dem monatlichen kumulativen Update vom April 2018 f\u00fcr Windows 10, Version 1709, verwenden. <\/p>\n<blockquote>\n<p>Irgendwie ist Windows 10 (auch zwei Jahre nach dem ersten Release) noch so richtig Baustelle \u2013 nicht zu fassen, Windows as a surprise halt eben. <\/p>\n<\/blockquote>\n<h2>Update KB4088891 f\u00fcr Windows 10 Version 1703<\/h2>\n<\/p>\n<p>Update <a title=\"https:\/\/support.microsoft.com\/de-de\/help\/4089848\/windows-10-update-kb4089848\" href=\"https:\/\/support.microsoft.com\/de-de\/help\/4088891\/windows-10-update-kb4088891\" target=\"_blank\" rel=\"noopener noreferrer\">KB4088891<\/a> wurde am 22. M\u00e4rz 2018 f\u00fcr Windows 10 Creators Update (Version 1703) freigegeben. Es handelt sich um ein neues Update, welches Qualit\u00e4tsverbesserungen enth\u00e4lt. Die folgenden Fixes sind explizit aufgef\u00fchrt. <\/p>\n<ul>\n<li>Addresses issue with a GDI handle leak in the Windows Ribbon control.  <\/li>\n<li>Addresses issue where, during BitLocker decryption or encryption of a drive, files protected with the Encrypting File System (EFS) may become corrupted.  <\/li>\n<li>Addresses issue where, when an iSCSI request contains an incomplete header in the first packet, iSCSI may not recognize when a request has been sent.  <\/li>\n<li>Adds support in <strong>stornvme <\/strong>for additional SSDs.  <\/li>\n<li>Addresses issue where the Japanese keyboard layout was not functioning properly during a Remote Assistance session.  <\/li>\n<li>Addresses rendering issue in Microsoft Edge for PDF documents with backgrounds created using various third-party publishing tools. <\/li>\n<\/ul>\n<p>Neben dem GDI-Handle-Leak f\u00fcr das Windows Men\u00fcband-Steuerelemente springen mit Bug-Fixes f\u00fcr Bitlocker (Konflikt mit EFS) sowie die iSCSI-Geschichte ins Auge. Auch beim Microsoft Edge mussten mal wieder PDF-Anzeigeprobleme gefixt werden. Selbst auf die Gefahr, mich zu wiederholen. Das ist Bastelniveau f\u00fcr den Kindergarten, aber nix, was ich produktiv einsetzen kann. <\/p>\n<p>Das Update wird \u00fcber Windows Update verteilt, kann aber \u00fcber den <a href=\"http:\/\/catalog.update.microsoft.com\/v7\/site\/Search.aspx?q=KB4088891\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Update Catalog<\/a> bezogen werden. Der Patch hebt die OS Build auf die Version 15063.994 an. Probleme sind keine bekannt. <\/p>\n<blockquote>\n<p>Microsoft hat zudem ein Update direkt f\u00fcr den Windows Update Client ver\u00f6ffentlicht, um dessen Zuverl\u00e4ssigkeit zu erh\u00f6hen. Jedes System f\u00fcr automatische Updates konfigurierte Windows 10 (auch Enterprise und Pro) wird dadurch das neueste Windows 10 Feature Update (Version 1803) erhalten. Wobei bei der Verteilung der neuen Windows 10-Version die Ger\u00e4tekompatibilit\u00e4t und die in Windows Update for Business eingestellte Richtlinie zur Update-Verz\u00f6gerung ber\u00fccksichtig wird. Einzige Ausnahme, wo keine Zwangs Feature-Upgrades erfolgen, sind die Windows 10 Enterprise LTSC-Versionen. <\/p>\n<\/blockquote>\n<h2>Update KB4088825 f\u00fcr Windows 10 Version 1703<\/h2>\n<p>Das kritische Update <a title=\"https:\/\/support.microsoft.com\/de-de\/help\/4089848\/windows-10-update-kb4089848\" href=\"https:\/\/support.microsoft.com\/de-de\/help\/4088825\/servicing-stack-update-for-windows-10-version-1703-march-22-2018\" target=\"_blank\" rel=\"noopener noreferrer\">KB4088825<\/a> wurde ebenfalls am 22. M\u00e4rz 2018 f\u00fcr Windows 10 Creators Update (Version 1703) freigegeben. Es handelt sich um ein ist ein Servicing Stack-Update, welches Verbesserungen am Servicing Stack enth\u00e4lt. <\/p>\n<h2>Update KB4088889 f\u00fcr Windows 10 Version 1607<\/h2>\n<p>Update <a title=\"https:\/\/support.microsoft.com\/de-de\/help\/4089848\/windows-10-update-kb4089848\" href=\"http:\/\/support.microsoft.com\/help\/4088889\" target=\"_blank\" rel=\"noopener noreferrer\">KB4088889<\/a> wurde am 22. M\u00e4rz 2018 f\u00fcr Windows 10 Anniversary Update (Version 1607) freigegeben. Es handelt sich um ein neues Update, welches Qualit\u00e4tsverbesserungen enth\u00e4lt. Die folgenden Fixes sind explizit aufgef\u00fchrt. <\/p>\n<ul>\n<li>Addresses issue with a GDI handle leak in the Windows Ribbon control.  <\/li>\n<li>Addresses issue where customers can't change the lock screen image from the Settings app. This occurs if the \"Force a specific default lock screen and logon image\" Group Policy is turned on and the \"Prevent changing lock screen and logon image\" Group Policy is turned off.  <\/li>\n<li>Addresses issue where, during BitLocker decryption or encryption of a drive, files protected with the Encrypting File System (EFS) may become corrupted.  <\/li>\n<li>Adds support for additional high-speed eMMC devices.  <\/li>\n<li>Adds support in <strong>stornvme<\/strong> for additional SSDs.  <\/li>\n<li>Addresses issue where UWF file exclusion failed when non-ASCII characters were used in the directory name.  <\/li>\n<li>Addresses issue where ID:55 and ID:130 might be logged when using UWF in DISK mode, which eventually requires a restart.  <\/li>\n<li>Addresses issue where the VSS API <strong>ResyncLun<\/strong> failed to find the hardware provider.  <\/li>\n<li>Addresses issue where Hyper-V replication suspends when the primary server restarts and Azure Site Recovery (ASR) is used to replicate Hyper-V virtual machines.  <\/li>\n<li>Addresses issue where an error might occur when the memory manager finds an undeleted page table space when a process terminates.  <\/li>\n<li>Addresses issue where Windows Server 2016 Domain Controllers (DC) may periodically restart after a Local Security Authority Subsystem Service (LSASS) module faults with exception code 0xc0000005. This interrupts applications and services bound to the DC at that time. DCs may log the following events:  <\/li>\n<li>Application Error event ID 1000; the faulty module is NTDSATQ.dll with exception code 0xc0000005.  <\/li>\n<li>User32 event ID 1074 and Microsoft-Windows-Wininit event ID 1015, which indicates that <strong>lsass.exe<\/strong> failed with status code 255.  <\/li>\n<li>Addresses issue where the AdminSDHolder task fails to run when a protected group contains a member attribute that points to a deleted object. Additionally, Event 1126 is logged with \"Active Directory Domain Services was unable to establish a connection with the global catalog. Error value: 8430. The directory service encountered an internal failure. Internal ID: 320130e.\"  <\/li>\n<li>Addresses issue where users may exist in a trusted domain with transitive trust (a child domain across Forest trust or AD FS in a child domain and the user is across Forest trust). However, users cannot locate a PDC or DC for the Extranet Lockout Feature. The following exception occurs: \"Microsoft.IdentityServer.Service.AccountPolicy.ADAccountLookupException: MSIS6080: A bind attempt to domain 'globalivewireless.local' failed with error code '1722'.\" A message appears on the IDP page, \"Incorrect user ID or password. Type the correct user ID and password, and try again.\" <\/li>\n<li>Addresses issue where, when Claims Provider Trust is set with OrganizationalAccountSuffix (even after performing HRD), AD FS doesn't save the HRD information. The user will always see the HRD page for any new request. This breaks the SSO request for users because they need to type a username or email and password for each request.  <\/li>\n<li>Improves the performance of AD FS MFA authentication response time by improving the utilization of Strong Authentication Service (SAS) calls.  <\/li>\n<li>Addresses issue caused by a new privilege in Windows Server 2016 and Windows 10 version 1607 named \"Obtain an impersonation token for another user in the same session\". When applied using Group Policy to those computers, <strong>gpresult \/h<\/strong> fails to generate reporting data for any setting configured by the Security Configuration Engine (SCE) extension. The error message is \"Requested value 'SeDelegateSessionUserImpersonatePrivilege' was not found\". The Group Policy Management Console fails to show the privilege in the Settings tab for a GPO where the setting has been configured.  <\/li>\n<li>Addresses issue where WMI stops responding to queries and WMI-dependent operations fail after exceeding the 256 MB <a href=\"https:\/\/msdn.microsoft.com\/en-us\/library\/aa394624\" target=\"_blank\" rel=\"noopener noreferrer\">WMI Arbitrator<\/a> memory limit. Computers that experience high WMI memory usage or that return error WBEM_E_INVALID_CLASS or WBEM_E_NOT_FOUND should install this update.  <\/li>\n<li>Addresses a threading issue that might cause the WinRM service to stop working when under load. This is a client-side solution, so it should be applied to affected computers as well as computers that communicate with it using WinRM.  <\/li>\n<li>Addresses issue with system performance that causes logons to become unresponsive with the message \"Please wait for the Remote Desktop Configuration\" because of a deadlock in the WinRM service.  <\/li>\n<li>Addresses issue where the Remote Desktop License report gets corrupted when it exceeds the 4 KB size limit.  <\/li>\n<li>Addresses a race condition in RemoteApp that occurs when an activated RemoteApp window opens behind the previous foreground window.&nbsp; <\/li>\n<li>Addresses rendering issue in Microsoft Edge for PDF documents with backgrounds created using various third-party publishing tools.&nbsp; <\/li>\n<li>Addresses issue caused by a race condition where Windows Server 2016 may restart after win32kbase.sys faults with error code 0x18.<\/li>\n<\/ul>\n<p>Auch hier bleibt mir die Spucke weg, was da an dem im Sommer 2016 freigegebenen Anniversary Update an Bugs zu korrigieren war. <\/p>\n<p>Das Update wird \u00fcber Windows Update verteilt, kann aber \u00fcber den <a href=\"http:\/\/catalog.update.microsoft.com\/v7\/site\/Search.aspx?q=KB4088889\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Update Catalog<\/a> bezogen werden. Der Patch hebt die OS Build auf die Version 14393.2155 an. Probleme sind keine bekannt. <\/p>\n<blockquote>\n<p>Microsoft hat auch hier ein Update direkt f\u00fcr den Windows Update Client ver\u00f6ffentlicht, um dessen Zuverl\u00e4ssigkeit zu erh\u00f6hen. Jedes System f\u00fcr automatische Updates konfigurierte Windows 10 (auch Enterprise und Pro) wird dadurch das neueste Windows 10 Feature Update (Version 1803) erhalten. Wobei bei der Verteilung der neuen Windows 10-Version die Ger\u00e4tekompatibilit\u00e4t und die in Windows Update for Business eingestellte Richtlinie zur Update-Verz\u00f6gerung ber\u00fccksichtig wird. Einzige Ausnahme, wo keine Zwangs Feature-Upgrades erfolgen, sind die Windows 10 Enterprise LTSC-Versionen. <\/p>\n<\/blockquote>\n<h2>Update KB4089510 f\u00fcr Windows 10 Version 1607<\/h2>\n<p>Das kritische Update <a title=\"https:\/\/support.microsoft.com\/de-de\/help\/4089848\/windows-10-update-kb4089848\" href=\"https:\/\/support.microsoft.com\/de-de\/help\/4089510\/servicing-stack-update-for-windows-10-version-1607-march-22-2018\" target=\"_blank\" rel=\"noopener noreferrer\">KB4089510<\/a> wurde ebenfalls am 22. M\u00e4rz 2018 f\u00fcr Windows 10 Anniversary Update (Version 1607) und Windows Server 2016 freigegeben. Es handelt sich um ein ist ein Servicing Stack-Update, welches Verbesserungen am Servicing Stack enth\u00e4lt. <\/p>\n<h2>Updates f\u00fcr Windows 10 Version 1803<\/h2>\n<p>F\u00fcr ausgesuchte Maschinen im Windows Insider-Programm wurden noch folgende Updates zum Testen ausgerollt. <\/p>\n<h3>Update KB4093297 f\u00fcr Windows Version vnext<\/h3>\n<p>Das Update <a title=\"https:\/\/support.microsoft.com\/de-de\/help\/4089848\/windows-10-update-kb4089848\" href=\"https:\/\/support.microsoft.com\/de-de\/help\/4093297\" target=\"_blank\" rel=\"noopener noreferrer\">KB4093297<\/a> (Update to Windows 10 version vnext for update applicability) wurde bereits am 15. M\u00e4rz 2018&nbsp; f\u00fcr eine begrenzte Anzahl an Windows Insidern f\u00fcr Testzwecke ausgeliefert. <\/p>\n<p><strong>\u00c4hnliche Artikel:<\/strong><br \/>Adobe Flash Player Update auf Version 29.0.0.113<br \/><a href=\"https:\/\/borncity.com\/blog\/2018\/03\/07\/microsoft-office-patchday-6-mrz-2018\/\">Microsoft Office Patchday (6. M\u00e4rz 2018)<\/a><br \/><a href=\"https:\/\/borncity.com\/blog\/2018\/03\/13\/microsoft-patchday-summary-13-mrz-2018\/\">Microsoft Patchday Summary 13. M\u00e4rz 2018<\/a><br \/><a href=\"https:\/\/borncity.com\/blog\/2018\/03\/13\/sicherheits-updates-fr-windows-7-8-1-13-mrz-2018\/\">Sicherheits-Updates f\u00fcr Windows 7\/8.1<\/a> (13. M\u00e4rz 2018)<br \/><a href=\"https:\/\/borncity.com\/blog\/2018\/03\/14\/patchday-windows-10-updates-13-mrz-2018\/\">Patchday: Windows 10-Updates 13. M\u00e4rz 2018<\/a><br \/><a href=\"https:\/\/borncity.com\/blog\/2018\/03\/15\/microsoft-office-patchday-13-mrz-2018\/\">Microsoft Office Patchday (13. M\u00e4rz 2018)<\/a><br \/><a href=\"https:\/\/borncity.com\/blog\/2018\/03\/16\/patchday-weitere-microsoft-updates-zum-13-mrz-2018\/\">Patchday: Windows 10-Updates 13. M\u00e4rz 2018<\/a><br \/><a href=\"https:\/\/borncity.com\/blog\/2018\/03\/15\/update-kb4087658-windows-10-version-1803\/\">Update KB4087658 Windows 10 Version 1803<\/a><br \/><a href=\"https:\/\/borncity.com\/blog\/2018\/03\/16\/patchday-weitere-microsoft-updates-zum-13-mrz-2018\/\">Patchday: Weitere Microsoft Updates zum 13. M\u00e4rz 2018<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>[English]Microsoft hat zum 22. M\u00e4rz 2018 eine Reihe kumulativer Updates f\u00fcr Windows 10 freigegeben. Hier eine \u00dcbersicht, was verf\u00fcgbar ist und was es sonst zu wissen gibt.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[185,3694],"tags":[6902,6901,6905,6900,6904,4315,4378],"class_list":["post-202476","post","type-post","status-publish","format-standard","hentry","category-update","category-windows-10","tag-kb4088825","tag-kb4088891","tag-kb4089510","tag-kb4089848","tag-kb4093297","tag-update","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/202476","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=202476"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/202476\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=202476"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=202476"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=202476"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}