Windows 11

Operating Systems

Cumulative and preview updates for Windows 11, from the KB update history.

Latest 28000.2525 · by MicrosoftWebsiteRSS

Branches

28000
28000.2954
26200
26200.9168
22631
22631.7219

Release activity

Release activity — 33 releases across 19 days since Jan 29, 2026. Each cell is one day; darker means more releases that day. Nothing is recorded before Jan 29, 2026. Older weeks are hidden at this screen width.
JunJulAugSep
SundayNo releases on May 24, 2026No releases on May 31, 2026No releases on Jun 7, 2026No releases on Jun 14, 2026No releases on Jun 21, 2026No releases on Jun 28, 2026No releases on Jul 5, 2026No releases on Jul 12, 2026No releases on Jul 19, 2026No releases on Jul 26, 2026No releases on Aug 2, 2026No releases on Aug 9, 2026No releases on Aug 16, 2026No releases on Aug 23, 2026No releases on Aug 30, 2026No releases on Sep 6, 2026
MondayNo releases on May 25, 2026No releases on Jun 1, 2026No releases on Jun 8, 2026No releases on Jun 15, 2026No releases on Jun 22, 2026No releases on Jun 29, 2026No releases on Jul 6, 2026No releases on Jul 13, 2026No releases on Jul 20, 2026No releases on Jul 27, 2026No releases on Aug 3, 2026No releases on Aug 10, 2026No releases on Aug 17, 2026No releases on Aug 24, 2026No releases on Aug 31, 2026No releases on Sep 7, 2026
Tuesday1 release on May 26, 2026No releases on Jun 2, 20263 releases on Jun 9, 2026No releases on Jun 16, 20262 releases on Jun 23, 2026No releases on Jun 30, 2026No releases on Jul 7, 20262 releases on Jul 14, 2026No releases on Jul 21, 20262 releases on Jul 28, 2026No releases on Aug 4, 20262 releases on Aug 11, 2026No releases on Aug 18, 2026No releases on Aug 25, 2026No releases on Sep 1, 20261 release on Sep 8, 2026
WednesdayNo releases on May 27, 2026No releases on Jun 3, 2026No releases on Jun 10, 2026No releases on Jun 17, 2026No releases on Jun 24, 2026No releases on Jul 1, 2026No releases on Jul 8, 2026No releases on Jul 15, 2026No releases on Jul 22, 2026No releases on Jul 29, 2026No releases on Aug 5, 2026No releases on Aug 12, 2026No releases on Aug 19, 2026No releases on Aug 26, 2026No releases on Sep 2, 2026No releases on Sep 9, 2026
ThursdayNo releases on May 28, 2026No releases on Jun 4, 2026No releases on Jun 11, 2026No releases on Jun 18, 2026No releases on Jun 25, 2026No releases on Jul 2, 2026No releases on Jul 9, 2026No releases on Jul 16, 2026No releases on Jul 23, 2026No releases on Jul 30, 2026No releases on Aug 6, 2026No releases on Aug 13, 2026No releases on Aug 20, 20262 releases on Aug 27, 2026No releases on Sep 3, 2026No releases on Sep 10, 2026
FridayNo releases on May 29, 2026No releases on Jun 5, 2026No releases on Jun 12, 2026No releases on Jun 19, 2026No releases on Jun 26, 2026No releases on Jul 3, 2026No releases on Jul 10, 2026No releases on Jul 17, 2026No releases on Jul 24, 2026No releases on Jul 31, 2026No releases on Aug 7, 2026No releases on Aug 14, 2026No releases on Aug 21, 2026No releases on Aug 28, 2026No releases on Sep 4, 2026No releases on Sep 11, 2026
SaturdayNo releases on May 30, 2026No releases on Jun 6, 2026No releases on Jun 13, 2026No releases on Jun 20, 2026No releases on Jun 27, 2026No releases on Jul 4, 2026No releases on Jul 11, 20261 release on Jul 18, 2026No releases on Jul 25, 2026No releases on Aug 1, 2026No releases on Aug 8, 2026No releases on Aug 15, 2026No releases on Aug 22, 2026No releases on Aug 29, 2026No releases on Sep 5, 2026

33 releases since Jan 29, 2026, busiest day 3

Changelog

What changed from 26200 to 28000
Filter releases by branch
33 of 33 releases
28000.2804Pre-release

August 27, 2026—KB5120996 (OS Build 28000.2804) Preview

View originalPermalink
How 28000.2804 went
26200.9278Pre-release

August 27, 2026—KB5120998 (OS Builds 26200.9278 and 26100.9278) Preview

View originalPermalink
How 26200.9278 went
28000.2704

August 11, 2026—KB5121000 (OS Build 28000.2704)

View originalPermalink
How 28000.2704 went
26200.9168

August 11, 2026—KB5121003 (OS Builds 26200.9168 and 26100.9168)

View originalPermalink
How 26200.9168 went
28000.2608Pre-release

July 28, 2026—KB5101681 (OS Build 28000.2608) Preview

  • July 28, 2026 — Added a highlight for mobile device management (MDM)
View originalPermalink
How 28000.2608 went
26200.8973Pre-release

July 28, 2026—KB5101684 (OS Builds 26200.8973 and 26100.8973) Preview

View originalPermalink
How 26200.8973 went
26200.8894

July 18, 2026—KB5121767 (OS Builds 26200.8894 and 26100.8894) Out-of-band

View originalPermalink
How 26200.8894 went
28000.2525

July 14, 2026—KB5101649 (OS Build 28000.2525)

Deprecated 1
  • Picture password is no longer available for new enrollment, though existing configured picture passwords can continue to be used for sign-in
Security 1
  • Picture password has been restricted to enhance security, with a recommendation to use Windows Hello PIN, facial recognition, or fingerprint recognition instead

From Windows 11

  • August 5, 2026 — Update added: [Picture password] To help enhance security, picture password is no longer available for new enrollment. Users who have already configured a picture password can continue to use it to sign in to Windows. If a picture password is removed, disabled, or not previously configured, it cannot be set up again. We recommend using Windows Hello PIN, facial recognition, or fingerprint recognition where available.
View originalPermalink
How 28000.2525 went
26200.8875

July 14, 2026—KB5101650 (OS Builds 26200.8875 and 26100.8875)

Deprecated 1
  • Picture password is no longer available for new enrollment; users with existing picture passwords can continue to use them for sign-in, but cannot reconfigure if removed or disabled
Security 1
  • Enhanced security by restricting picture password to existing users only and recommending Windows Hello PIN, facial recognition, or fingerprint recognition instead

From Windows 11

  • July 15, 2026 — Amended the announcement, "Update temporarily unavailable for some devices with Intel IPF drivers"
  • August 5, 2026 — Update added, [Picture password] To help enhance security, picture password is no longer available for new enrollment. Users who have already configured a picture password can continue to use it to sign in to Windows. If a picture password is removed, disabled, or not previously configured, it cannot be set up again. We recommend using Windows Hello PIN, facial recognition, or fingerprint recognition where available.
View originalPermalink
How 26200.8875 went
28000.2340Pre-release

June 23, 2026—KB5095091 (OS Build 28000.2340) Preview

Changed 2
  • Change Windows Driver Policy enforcement type to restore recovery and disk replacement scenarios while maintaining driver security protections for enforced devices
  • Improve disk space usage for the CapabilityAccessManager.db-wal file
Fixed 1
  • Fix an issue where the Windows Driver Policy could prevent recovery, reimaging, or booting from older recovery media

From Windows 11

  • July 23, 2026 — Update added (normal rollout): [Windows Driver Policy] Fixed: This update fixes an issue where the Windows Driver Policy could prevent recovery, reimaging, or booting from older recovery media. The update changes the policy enforcement type, restoring recovery and disk replacement scenarios while maintaining the driver security protections for enforced devices.
  • June 29, 2026 — Update added (normal rollout): [Storage] This update improves disk space usage for the CapabilityAccessManager.db-wal file.
View originalPermalink
How 28000.2340 went
26200.8737Pre-release

June 23, 2026—KB5095093 (OS Builds 26200.8737 and 26100.8737) Preview

Changed 3
  • Change Windows Driver Policy enforcement type to restore recovery and disk replacement scenarios while maintaining driver security protections
  • Improve disk space usage for the CapabilityAccessManager.db-wal file
  • Improve File Explorer responsiveness when mounting disk images
Fixed 3
  • Fix an issue where the Windows Driver Policy could prevent recovery, reimaging, or booting from older recovery media
  • Fix an issue where notification badge counts for some applications such as Microsoft Teams and WhatsApp might not refresh correctly
  • Fix an issue where the OneDrive shortcut in File Explorer stops working when File Explorer is run with administrative mode

From Windows 11

  • July 22, 2026 — Update added (normal rollout): [Windows Driver Policy] This update fixes an issue where the Windows Driver Policy could prevent recovery, reimaging, or booting from older recovery media. The update changes the policy enforcement type, restoring recovery and disk replacement scenarios while maintaining the driver security protections for enforced devices.
  • July 14, 2026 — Update added (gradual rollout): [Notification badges (known issue)] Fixed: This update addresses an issue where notification badge counts for some applications such as Microsoft Teams and WhatsApp, might not refresh correctly. As a result, badge indicators might continue to display outdated notification counts until the application is restarted or badge count is refreshed.
  • July 14, 2026 — Update moved to normal rollout: [File Explorer] This update fixes an issue where the OneDrive shortcut in File Explorer stops working when File Explorer is run with administrative mode.
  • June 29, 2026 — Update added (normal rollout): [Storage] This update improves disk space usage for the CapabilityAccessManager.db-wal file.
  • June 23, 2026 — Update added (gradual rollout): [File Explorer] This update improves File Explorer responsiveness when mounting disk images.
View originalPermalink
How 26200.8737 went
22631.7219

June 9, 2026—KB5093998 (OS Build 22631.7219)

Added 1
  • Folder customization capability
Fixed 3
  • OneDrive shortcut in File Explorer now works in administrator mode
  • Deleting from Recycle Bin no longer displays an internal file name
  • Microsoft Office applications now open correctly from third-party apps

From Windows 11

  • June 23, 2026 — Known issue added: "OneDrive shortcut in File Explorer might not work in administrator mode".
  • June 18, 2026 — Known issue added: "Deleting from Recycle Bin displays an internal file name".
  • June 16. 2026 — Known issue added: "Microsoft Office applications might fail to open from certain third-party apps".
  • June 10, 2026 — Update: Folder customization added.
View originalPermalink
How 22631.7219 went
26200.8655

June 9, 2026—KB5094126 (OS Builds 26200.8655 and 26100.8655)

Added 1
  • Added folder customization
Fixed 2
  • Fixed an issue that could cause the Deployment Image Servicing and Management (DISM) tool to fail with error 0x800f0915 when running the /RestoreHealth command on some Windows 11, version 24H2 devices
  • Fixed an issue where deleting from Recycle Bin displays an internal file name

From Windows 11

  • July 14, 2026 — Added release note: [DISM (Known issue)] Fixed. This update addresses an issue that could cause the Deployment Image Servicing and Management (DISM) tool to fail with error 0x800f0915 when running the /RestoreHealth command on some Windows 11, version 24H2 devices. As a result, component store repair operations could fail and prevent successful servicing recovery.
  • June 23, 2026 — Known issue update: Added resolution for "Deleting from Recycle Bin displays an internal file name".
  • Juen 18, 2026 — Known issue added: "Deleting from Recycle Bin displays an internal file name".
  • June 16. 2026 — Known issue added: "Microsoft Office applications might fail to open from certain third-party apps".
  • June 10, 2026 — Update: Folder customization added.
View originalPermalink
How 26200.8655 went
28000.2269

June 9, 2026—KB5095051 (OS Build 28000.2269)

Added 1
  • Folder customization
Fixed 1
  • Resolved issue where deleting from Recycle Bin displays an internal file name

From Windows 11

  • June 23, 2026 — Known issue update: Added resolution for "Deleting from Recycle Bin displays an internal file name".
  • June 18, 2026 — Known issue added: "Deleting from Recycle Bin displays an internal file name".
  • June 16. 2026 — Known issue added: "Microsoft Office applications might fail to open from certain third-party apps".
  • June 10, 2026 — Update: Folder customization added.
View originalPermalink
How 28000.2269 went
28000.2179Pre-release

May 26, 2026—KB5089570 (OS Build 28000.2179) Preview

View originalPermalink
How 28000.2179 went
28000.2113

May 12, 2026—KB5089548 (OS Build 28000.2113)

View originalPermalink
How 28000.2113 went
22631.7079

May 12, 2026—KB5087420 (OS Build 22631.7079)

Added 1
  • Add a new SecureBootfolder under C:\Windows on eligible devices

From Windows 11

  • June 09, 2026 — Known issue revision: Updated workaround for "Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key"
  • May 20, 2026 — Corrected the Microsoft Update Catalog link to point to the May 12, 2026 update instead of the April 14, 2026 update.
  • May 13, 2026 — Added Secure Boot release note: This update adds a new SecureBootfolder under C:\Windows on eligible devices.
View originalPermalink
How 22631.7079 went
26200.8328Pre-release

April 30, 2026—KB5083631 (OS Builds 26200.8328 and 26100.8328) Preview

Added 1
  • Windows Push Notification Services (WNS) added

From Windows 11

  • June 23, 2026 — Update: Windows Push Notification Services (WNS) added (normal rollout).
  • May 12, 20226 — Known issue revision: Updated workaround for "Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key".
View originalPermalink
How 26200.8328 went
28000.1896Pre-release

April 30, 2026—KB5083806 (OS Build 28000.1896) Preview

View originalPermalink
How 28000.1896 went
28000.1836

April 14, 2026—KB5083768 (OS Build 28000.1836)

Added 1
  • Known issue: Warnings related to Remote Desktop might not display correctly
Changed 1
  • Updated commands (MSU strings) under Catalog
Fixed 1
  • Updated workaround for warnings related to Remote Desktop that might not display correctly

From Windows 11

  • May 26, 2026 — Updated commands (MSU strings) under Catalog
  • April 30, 2026 — Know issue revision: Updated workaround for "Warnings related to Remote Desktop might not display correctly"
  • April 27, 2026 — Know issue update: Title revision for known issue "Warnings related to Remote Desktop might not display correctly
  • April 23, 2026 — Known issue added: "Warnings related to Remote Desktop might not display correctly"
View originalPermalink
How 28000.1836 went
22631.6936

April 14, 2026—KB5082052 (OS Build 22631.6936)

Fixed 1
  • Warnings related to Remote Desktop might not display correctly
Security 1
  • Vulnerable driver blocklist improvement added

From Windows 11

  • June 09, 2026 — Known issue revision: Updated workaround for "Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key"
  • May 12, 2026 — Know issue revision: Updated workaround for "Warnings related to Remote Desktop might not display correctly"
  • May 1, 2026 — Improvement added: [Vulnerable driver blocklist]
  • April 27, 2026 — Know issue update: Title revision for known issue "Warnings related to Remote Desktop might not display correctly"
  • April 23, 2026 — Known issue added: "Warnings related to Remote Desktop might not display correctly"
  • April 21, 2026 — Known issue updated: "Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key"
  • April 14, 2026 — Known issue added: "Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key"
View originalPermalink
How 22631.6936 went
26200.8117

March 31, 2026—KB5086672 (OS Builds 26200.8117 and 26100.8117) Out-of-band

Fixed 1
  • Corrected the x64 and arm64 .msu update strings on the Catalog tab for KB5086672

From Windows 11

  • June 4, 2026 — Corrected the x64 and arm64 .msu update strings on the Catalog tab for KB5086672 (this update)
View originalPermalink
How 26200.8117 went
26200.8116Pre-release

March 26, 2026—KB5079391 (OS Builds 26200.8116 and 26100.8116) Preview

Fixed 1
  • Corrected the x64 and arm64 .msu update strings on the Catalog tab for KB5079391

From Windows 11

  • June 4, 2026 — Corrected the x64 and arm64 .msu update strings on the Catalog tab for KB5079391 (this update)
  • March 31, 2026 — Added a note at the top of this article that this update is no longer being offered to new devices due to an installation issue identified after release. The issue has been addressed in the March 31, 2026—KB5086672 (OS Builds 26200.8117 and 26100.8117) Out-of-band update that is now available.The known issue, "Rollout of this update is temporarily paused due to installation error 0x80073712", has been updated and retitled to "Installation of this update might fail with error 0x80073712".
  • March 30, 2026 — Known issue updated: "Rollout of this update is temporarily paused due to installation error 0x80073712"
  • March 27, 2026 — Known issue added: "Rollout of this update is temporarily paused due to installation error 0x80073712"
View originalPermalink
How 26200.8116 went
28000.1764Pre-release

March 26, 2026—KB5079489 (OS Build 28000.1764) Preview

View originalPermalink
How 28000.1764 went
26200.8039

March 21, 2026—KB5085516 (OS Builds 26200.8039 and 26100.8039) Out-of-band

Fixed 1
  • Corrected the x64 and arm64 .msu update strings on the Catalog tab for KB5085516

From Windows 11

  • June 4, 2026 — Corrected the x64 and arm64 .msu update strings on the Catalog tab for KB5085516 (this update)
View originalPermalink
How 26200.8039 went
26200.8037

March 10, 2026—KB5079473 (OS Builds 26200.8037 and 26100.8037)

Changed 1
  • Updated workaround for signing in with a Microsoft account that might fail for Microsoft Teams Free and other apps
Fixed 1
  • Corrected the x64 and arm64 .msu update strings on the Catalog tab for KB5079473

From Windows 11

  • June 4, 2026 — Corrected the x64 and arm64 .msu update strings on the Catalog tab for KB5079473 (this update)
  • March 21, 2026 — Known issue revision: Updated workaround for "Signing in with a Microsoft account might fail for Microsoft Teams Free and other apps"
  • March 19, 2026 — Known issue added: "Signing in with a Microsoft account might fail for Microsoft Teams Free and other apps"
View originalPermalink
How 26200.8037 went
28000.1719

March 10, 2026—KB5079466 (OS Build 28000.1719)

Changed 1
  • Updated commands (MSU strings) under Catalog
Security 1
  • Secure Boot quality updates now include additional high confidence device targeting data to increase coverage of devices eligible to automatically receive new Secure Boot certificates

From Windows 11

  • May 26, 2026 — Updated commands (MSU strings) under Catalog.
  • March 11, 2026 — Update: This March 2026 security update (KB5079466) includes the following:[Secure Boot] With this update, Windows quality updates include additional high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Devices receive the new certificates only after demonstrating sufficient successful update signals, maintaining a controlled and phased rollout.
View originalPermalink
How 28000.1719 went
26200.7922Pre-release

February 24, 2026—KB5077241 (OS Builds 26200.7922 and 26100.7922) Preview

Added 3
  • Widget Settings now open as a full-page experience in the Widgets app instead of opening in a dialog
  • Get-SecureBootUEFI cmdlet now supports the -Decoded option, which displays Secure Boot keys and certificates in a readable format
  • Get-SecureBootSVN cmdlet lets you check the Secure Boot Security Version Number (SVN) of your device's UEFI firmware and bootloader, and report whether the device follows the latest Secure Boot policy

From Windows 11

  • June 4, 2026 — Corrected the x64 and arm64 .msu update strings on the Catalog tab for KB5077241 (this update)
  • April 10. 2026 — Update: This feature, originally documented in the Febrary 2026 non‑security update (KB5077241), has been removed from the documentation and is planned for a future release.[Widgets] New! Widget Settings now open as a full‑page experience in the Widgets app instead of opening in a dialog.
  • March 11, 2026 — Update: These features are included in the February 2026 non-security update (KB5077241).[Secure Boot] This update introduces two new PowerShell features to help you manage the ongoing Secure Boot key rollout. The Get-SecureBootUEFI cmdlet now supports the -Decoded option, which displays Secure Boot keys and certificates in a readable format. The Get-SecureBootSVN cmdlet lets you check the Secure Boot Security Version Number (SVN) of your device’s UEFI firmware and bootloader, and report whether the device follows the latest Secure Boot policy.
  • February 27, 2026 — Update: In the “How to get this update” section, under the Microsoft Update Catalog, the arm64 instructions are now included.
View originalPermalink
How 26200.7922 went
28000.1643Pre-release

February 24, 2026—KB5077239 (OS Build 28000.1643) Preview

Added 2
  • Add -Decoded option to Get-SecureBootUEFI cmdlet to display Secure Boot keys and certificates in readable format
  • Add Get-SecureBootSVN cmdlet to check Secure Boot Security Version Number (SVN) of device UEFI firmware and bootloader and report compliance with latest Secure Boot policy
Changed 1
  • Update MSU strings under Catalog

From Windows 11

  • May 26, 2026 — Updated commands (MSU strings) under Catalog.
  • March 11, 2026 — Update: These features are included in the February 2026 non-security update (KB5077239).[Secure Boot] This update introduces two new PowerShell features to help you manage the ongoing Secure Boot key rollout. The Get-SecureBootUEFI cmdlet now supports the -Decoded option, which displays Secure Boot keys and certificates in a readable format. The Get-SecureBootSVN cmdlet lets you check the Secure Boot Security Version Number (SVN) of your device’s UEFI firmware and bootloader, and report whether the device follows the latest Secure Boot policy
View originalPermalink
How 28000.1643 went
28000.1575

February 10, 2026—KB5077179 (OS Build 28000.1575)

  • May 26, 2026 — Updated MSU string
  • February 10, 2026 — This update does not include any changes.
View originalPermalink
How 28000.1575 went
26200.7840

February 10, 2026—KB5077181 (OS Builds 26200.7840 and 26100.7840)

Fixed 1
  • Corrected the x64 .msu update string on the Catalog tab for KB5077181

From Windows 11

  • June 4, 2026 — Corrected the x64 .msu update string on the Catalog tab for KB5077181 (this update)
  • February 24, 2026 — Update: In the “How to get this update” section, under Catalog, the second MSU file listed in Method 2: Install each MSU file individually has been updated.
View originalPermalink
How 26200.7840 went
26200.7705Pre-release

January 29, 2026—KB5074105 (OS Builds 26200.7705 and 26100.7705) Preview

Added 4
  • Windows Hello Enhanced Sign-in Security now supports peripheral fingerprint sensors for desktops and other Windows 11 PCs
  • View the Device card on the Settings home page showing key specifications and usage details for your PC
  • Turn Smart App Control on or off without any clean install requirement via Windows Security > App & Browser Control > Smart App Control settings
  • User Account Control prompt now displays when opening Storage settings to help ensure only authorized Windows users can access system files

From Windows 11

  • June 4, 2026 — Corrected the x64 .msu update string on the Catalog tab for KB5074105 (this update)
  • April 09, 2026 — Update: This feature, originally documented in the January 2026 non‑security update (KB5074105), has been removed from the documentation and is planned for a future release. [Windows Hello] New! Windows Hello Enhanced Sign-in Security (ESS) now supports peripheral fingerprint sensors. This update extends this more secure sign in option beyond devices with built in fingerprint sensors to include desktops and other Windows 11 PCs, including Copilot+ PCs. To get started, plug in a supported ESS fingerprint reader, go to Settings > Accounts > Sign in options, and follow the prompts to enroll.
  • February 24, 2026 — Update: In the “How to get this update” section, under Catalog, the second MSU file listed in Method 2: Install each MSU file individually has been updated.
  • February 19, 2026 — Update: This feature, originally documented in the January 2026 non‑security update (KB5074105), has been removed from the documentation and is planned for a future release. [Settings] New! You can view the Device card on the Settings home page. It shows key specifications and usage details for your PC. From the card, you can go directly to Settings > System > About for more detailed information about your device. This card appears when you sign in with your Microsoft account.
  • February 11. 2026 — Update: This feature, originally documented in the January 2026 non‑security update (KB5074105), has been removed from the documentation and is planned for a future release.[Smart App Control] New! You can turn Smart App Control (SAC) on or off without any clean install requirement. To make changes, go to Windows Security > App & Browser Control > Smart App Control settings. When turned on, SAC helps block untrusted or potentially harmful apps. To learn more, see App & Browser Control in the Windows Security App – Microsoft Support.
  • January 30, 2026 — Update: This feature is included in the January 2026 non-security update (KB5074105).[Settings] New! To help ensure that only authorized Windows users can access system files, Windows now displays a User Account Control (UAC) prompt when you open Storage settings (Settings > System > Storage).
View originalPermalink
How 26200.7705 went
View all

Discussion