![\"\"](\"https:\/\/softantenna.com\/blog\/wp-content\/uploads\/2025\/04\/s_20250409_101606.jpg\")
<\/p>\n<\/p>\n
Microsoft\u306f4\u67088\u65e5(\u73fe\u5730\u6642\u9593)\u3001\u6bce\u6708\u7c73\u56fd\u6642\u9593\u306e\u7b2c2\u706b\u66dc\u65e5\u306b\u63d0\u4f9b\u3057\u3066\u3044\u308b\u6708\u4f8b\u66f4\u65b0\u306e\u4e00\u74b0\u3068\u3057\u3066\u3001Windows 11 Version 24H2\u7528\u306e\u7d2f\u7a4d\u30a2\u30c3\u30d7\u30c7\u30fc\u30c8KB5055523<\/a>\u7b49\u3092\u30ea\u30ea\u30fc\u30b9\u3057\u307e\u3057\u305f\u3002<\/p>\n \u66f4\u65b0\u30d7\u30ed\u30b0\u30e9\u30e0\u306f\u4e3b\u306b\u30b7\u30b9\u30c6\u30e0\u306e\u54c1\u8cea\u3092\u6539\u5584\u3057\u3001\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u554f\u984c\u3092\u4fee\u6b63\u3059\u308b\u3082\u306e\u3067\u3059\u3002<\/p>\n \u81ea\u52d5\u7684\u306b\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3055\u308c\u307e\u3059\u304c\u3001Windows Update\u307e\u305f\u306fMicrosoft Update Catalog\u3092\u5229\u7528\u3057\u3066\u624b\u52d5\u3067\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3059\u308b\u3053\u3068\u3082\u3067\u304d\u307e\u3059\u3002<\/p>\n \u305d\u308c\u305e\u308c\u306e\u5909\u66f4\u70b9\u306f\u4ee5\u4e0b\u306e\u901a\u308a\u3067\u3059(\u30ad\u30e5\u30ea\u30c6\u30a3\u30a2\u30c3\u30d7\u30c7\u30fc\u30c8\u306e\u5185\u5bb9\u306f\u65e5\u672cMicrosoft\u306e\u30d6\u30ed\u30b0<\/a>\u3067\u53c2\u7167\u3067\u304d\u307e\u3059)\u3002<\/p>\n Windows 11 Version 24H2\u7528\u306e\u66f4\u65b0\u30d7\u30ed\u30b0\u30e9\u30e0KB5055523<\/a>\u3067\u306f\u30013\u670827\u65e5\u306b\u516c\u958b\u3055\u308c\u305fKB5053656<\/a>\u306e\u5185\u5bb9\u306b\u52a0\u3048\u3001\u7279\u306bKerberos\u3092\u4f7f\u7528\u3057\u3066\u3044\u308b\u74b0\u5883\u3067Credential Guard \u3092\u6709\u52b9\u306b\u3057\u3066\u3044\u308b\u5834\u5408\u306b\u767a\u751f\u3057\u3066\u3044\u305f\u30e6\u30fc\u30b6\u30fc\u8a8d\u8a3c\u306b\u95a2\u3059\u308b\u554f\u984c\u304c\u4fee\u6b63\u3055\u308c\u3066\u3044\u307e\u3059\u3002\u30c1\u30ea\u306e\u30a2\u30a4\u30bb\u30f3\u5730\u57df\u306e\u30b5\u30fc\u30de\u30bf\u30a4\u30e0\u5909\u66f4\u3078\u306e\u5bfe\u5fdc\u3084\u3001PcaUiArmUpdate\u6a5f\u80fd\u306b\u5f71\u97ff\u3059\u308b\u554f\u984c\u3078\u306e\u5bfe\u51e6\u3082\u884c\u308f\u308c\u3066\u3044\u307e\u3059\u3002<\/p>\n \u30ea\u30ea\u30fc\u30b9\u30ce\u30fc\u30c8\u306f\u4ee5\u4e0b\u306e\u901a\u308a\u3067\u3059\u3002<\/p>\n This update addresses security issues for your Windows operating system.\u00a0<\/p>\n<\/blockquote>\n [Authentication]\u00a0<\/b>This update addresses an issue affecting machine password rotation in the Identity Update Manager certificate\/Public Key Cryptography for Initial Authentication (PKNIT)<\/a> path. This issue occurred particularly when Kerberos was used and Credential Guard was enabled, potentially causing user authentication problems. The feature Machine Accounts in Credential Gurad<\/b>, which is dependent on password rotation via Kerberos, has also been disabled, until a permanent fix is made available.<\/p>\n<\/li>\n [Daylight Saving Time (DST)]<\/b>\u00a0Update for the Aysen region in Chile to support the government DST change order in 2025. For more info\u00a0about DST changes, see\u00a0the\u00a0Daylight Saving Time & Time Zone Blog<\/a>.<\/p>\n<\/li>\n [PcaUiArm]<\/b> This update addresses an issue affecting the\u00a0PcaUiArmUpdate feature, which results\u00a0in unexpected behavior in specific scenarios.<\/p>\n<\/li>\n<\/ul>\n<\/blockquote>\n \u66f4\u65b0\u30d7\u30ed\u30b0\u30e9\u30e0\u306b\u306f\u4ee5\u4e0b\u306e3\u4ef6\u306e\u65e2\u77e5\u306e\u4e0d\u5177\u5408\u304c\u5b58\u5728\u3057\u307e\u3059\u3002<\/p>\n We\u2019re aware of an issue where players on Arm devices are unable to download and play Roblox from the Microsoft Store on Windows.<\/p>\n<\/div>\n<\/div>\n Roblox is working on a resolution to address this issue. Please refer to the Roblox support site for updates. Until the resolution is available, players on Arm devices can play Roblox by downloading the title directly from www.Roblox.com<\/a>.<\/p>\n<\/div>\n<\/div>\n<\/div>\n Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with\u00a0Citrix Session Recording Agent (SRA)<\/a>\u00a0version 2411. The 2411 version of this application was released in December 2024. Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix\u2019s documentation<\/a>.<\/p>\n Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.\u00a0\u200b\u200b\u200b\u200b\u200b\u200b\u200b<\/p>\n<\/div>\n<\/div>\n<\/div>\n We're aware of an edge case of Windows Hello issue affecting devices with specific security features enabled. After installing this update and performing a Push button reset<\/a> or Reset this PC<\/b> from Settings<\/b> > System<\/b> > Recovery<\/b> and selecting Keep my Files<\/b> and Local install<\/b>, some users might be unable to login to their Windows services using Windows Hello facial recognition or PIN. Users might observe a Windows Hello Message saying \"Something happened and your PIN isn't available. Click to set up your PIN again\" or \"Sorry something went wrong with face setup\".<\/p>\n Note:\u00a0<\/b>This issue only affects devices where System Guard Secure Launch<\/a> or Dynamic Root of Trust for Measurement (DRTM)<\/a> feature is enabled after installing this update. Devices with Secure Launch or DRTM enabled prior to this update, or those with these features disabled, are not impacted by this issue.<\/p>\n<\/p><\/div>\n<\/p>\n<\/div>\n<\/div>\n To login using PIN, follow the Set my PIN<\/b> prompt on the logon screen to re-enroll into Windows Hello.<\/p>\n<\/li>\n To use Face Logon, re-enroll in Windows Hello Facial recognition<\/b>\u00a0go to\u00a0Settings<\/b> > Accounts<\/b> > Sign-in options <\/b>> Facial recognition (Windows Hello)<\/b>, and select\u00a0Set up<\/b>.\u00a0Follow\u00a0the on-screen instructions.<\/p>\n<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/blockquote>\n \u66f4\u65b0\u30d7\u30ed\u30b0\u30e9\u30e0\u306fWindows Update\u306e\u4ed6\u3001Microsoft Update Catalog<\/a>\u3001Windows Server Update Services(WSUS)\u3092\u5229\u7528\u3057\u3066\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002<\/p>\n Windows 11 Version 23H2\/22H2\u7528\u306e\u66f4\u65b0\u30d7\u30ed\u30b0\u30e9\u30e0KB5055528<\/a>\u3067\u306f\u3001\u30c1\u30ea\u306e\u30a2\u30a4\u30bb\u30f3\u5730\u57df\u306e\u30b5\u30de\u30fc\u30bf\u30a4\u30e0\u306e\u5909\u66f4\u3078\u306e\u5bfe\u5fdc\u3084\u3001OS\u306e\u5185\u90e8\u6a5f\u80fd\u306b\u5bfe\u3059\u308b\u96d1\u591a\u306a\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u6539\u5584\u304c\u884c\u308f\u308c\u3066\u3044\u307e\u3059\u3002<\/p>\n \u30ea\u30ea\u30fc\u30b9\u30ce\u30fc\u30c8\u306f\u4ee5\u4e0b\u306e\u901a\u308a\u3067\u3059\u3002<\/p>\n [Daylight Saving Time (DST)<\/b>]\u00a0Update for the Aysen region in Chile to support the government DST change order in 2025. For more info\u00a0about DST changes, see\u00a0the\u00a0Daylight Saving Time & Time Zone Blog<\/a>.<\/p>\n<\/li>\n<\/ul>\n<\/blockquote>\n This update makes miscellaneous security improvements to internal OS functionality. No additional issues were documented for this release.<\/p>\n<\/li>\n<\/ul>\n<\/blockquote>\n \u66f4\u65b0\u30d7\u30ed\u30b0\u30e9\u30e0\u306b\u306f\u4ee5\u4e0b\u306e2\u4ef6\u306e\u65e2\u77e5\u306e\u4e0d\u5177\u5408\u304c\u5b58\u5728\u3057\u307e\u3059\u3002<\/p>\n Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update. This issue was observed on devices with\u00a0Citrix Session Recording Agent (SRA)<\/a>\u00a0version 2411. The 2411 version of this application was released in December 2024. Citrix has documented this issue, including a workaround, which can be performed prior to installing the January 2025 Windows security update. For details, see Citrix\u2019s documentation<\/a>.<\/p>\n Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available.\u00a0\u200b\u200b\u200b\u200b\u200b\u200b\u200b<\/p>\n<\/div>\n<\/div>\n<\/div>\n Audit Logon\/Logoff events in the local policy of the Active Directory Group Policy might not show as enabled on the device even if they are enabled and working as expected. This can be observed in the Local Group Policy Editor or Local Security Policy, where local audit policies show the \"Audit logon events\" policy with Security Setting of \"No auditing\".<\/p>\n<\/p>\n This issue might only manifest as a reporting inconsistency. It\u2019s possible that logon events are correctly being audited on the device. However, the \u201cAudit logon events\u201d policy will reflect that this is not the case. Home users are unlikely to be affected by this issue, as logon auditing is generally only necessary in enterprise environments.<\/p>\n<\/div>\n<\/div>\n Adjustments to the Windows registry will prevent this issue.<\/p>\n Important:\u00a0<\/b>This workaround contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, see How to back up and restore the registry in Windows<\/a>.<\/p>\n<\/p><\/div>\n Open the Windows registry editor and navigate to the following\u00a0key: Right-click\u00a0\u00a0AccessRights <\/b>>\u00a0Permissions<\/b>, select\u00a0Advanced<\/b>. Then, change owner to Administrators<\/b>, check Replace owner on subcontainers and objects<\/b>, select\u00a0Apply <\/b>and OK<\/b>.<\/p>\n<\/li>\n In the Permissions window, select Administrators<\/b>, check Full Control<\/b>\u00a0under \u201cAllow\u201d, select\u00a0Apply<\/b> and OK<\/b>.<\/p>\n<\/li>\n Modify the GUID key to the following value: Enable the subcategory with the correct GUID using the following command (open a Run dialog, then type the following command and press enter): Reverse the permission changes: Right-click AccessRights <\/b>>\u00a0Permissions<\/b>, select\u00a0Advanced<\/b>. Then, change owner to \"NT SERVICE\\TrustedInstaller\u201d, check Replace owner on subcontainers and objects<\/b>, select\u00a0Apply<\/b> and OK<\/b>.<\/p>\n<\/li>\n In the Permissions window, select Administrators<\/b>, check Read<\/b>\u00a0under \u201cAllow\u201d, select\u00a0Apply<\/b> and OK<\/b>.<\/p>\n<\/li>\n<\/ol>\n Next Steps<\/b><\/p>\n \u200b\u200b\u200b\u200b\u200b\u200b\u200b<\/b>Microsoft is working on a resolution and will provide more information when it is available.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/blockquote>\nApril 8, 2025\u2014KB5055523 (OS Build 26100.3775)<\/h2>\n
\u30cf\u30a4\u30e9\u30a4\u30c8<\/h3>\n
\n
\u6539\u826f\u3068\u4fee\u6b63<\/h3>\n
\n
\n
\u65e2\u77e5\u306e\u4e0d\u5177\u5408<\/h3>\n
\n
\n\nRoblox(All users)<\/div>\n\nSymptom:<\/div>\n\n\nWorkaround:<\/div>\n\n\nCitrix(All users)<\/div>\n\nSymptom:<\/div>\n\n
\n\u00a0
\nAffected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when restarting the device to complete the update installation, an error message with text similar to \u201cSomething didn\u2019t go as planned. No need to worry \u2013 undoing changes\u201d appears. The device will then revert to the Windows updates previously present on the device.\u00a0
\n\u00a0
\nThis issue likely affects a limited number of organizations as version 2411 of the SRA application is a new version. Home users are not expected to be affected by this issue.\u00a0<\/p>\n<\/div>\n<\/div>\n\nWorkaround:<\/div>\n\n\nWindows Hello(All users)<\/div>\n\nSymptoms:<\/div>\n\n\n\nWorkaround:<\/div>\n\n\n
April 8, 2025\u2014KB5055528 (OS Builds 22621.5189 and 22631.5189)<\/h2>\n
\u30cf\u30a4\u30e9\u30a4\u30c8<\/h3>\n
\n
\n
\u6539\u826f\u3068\u4fee\u6b63<\/h3>\n
\n
\n
\u65e2\u77e5\u306e\u4e0d\u5177\u5408<\/h3>\n
\n
\n\nCitrix(All users)<\/div>\n\nSymptom:<\/div>\n\n
\n\u00a0
\nAffected devices might initially download and apply the January 2025 Windows security update correctly, such as via the Windows Update page in Settings. However, when restarting the device to complete the update installation, an error message with text similar to \u201cSomething didn\u2019t go as planned. No need to worry \u2013 undoing changes\u201d appears. The device will then revert to the Windows updates previously present on the device.\u00a0
\n\u00a0
\nThis issue likely affects a limited number of organizations as version 2411 of the SRA application is a new version. Home users are not expected to be affected by this issue.\u00a0<\/p>\n<\/div>\n<\/div>\n\nWorkaround:<\/div>\n\n\nActive Directory Group Policy: Events in local policy<\/div>\n\nSymptom:<\/div>\n\n\nWorkaround:<\/div>\n\n\n\n
\n\t\u00a0HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Audit\\SystemPolicy\\LogonLogoff\\AccessRights<\/p>\n<\/li>\n
\n\t\u00a0{0CCE924B-69AE-11D9-BED3-505054503030}<\/p>\n<\/li>\n
\n\tauditpol \/set \/subcategory:{0CCE924B-69AE-11D9-BED3-505054503030} \/success:enable \/failure:enable<\/p>\n<\/li>\n