![\"Windows](\"https:\/\/www.europesays.com\/ie\/wp-content\/uploads\/2026\/05\/1778922431_52_0x0.jpg\")
<\/p>\n<\/p>\n
Windows update fail.<\/p>\n
NurPhoto via Getty Images<\/p>\n
Microsoft has finally fixed the issue \u201cwhere some devices might enter BitLocker Recover<\/a>y<\/a> after updating boot files.\u201d That left frustrated PC owners hunting for recovery keys after installing the April security update. The bad news is that Microsoft warns the fix itself might now fail.<\/p>\n The Windows maker released KB5089549<\/a> on May 12, but just 72 hours later it warned of a known issue where the new \u201csecurity update fails to install with error 0x800f0922.” This is likely down to memory availability. There are workarounds \u2014 but the best advice is to restart Windows.<\/p>\n Windows update fail.<\/p>\n NurPhoto via Getty Images<\/p>\n \u201cThis issue occurs on devices that have limited free space,\u201d Microsoft says. The security update likely fails \u201cduring the restart phase at approximately 35\u201336% completion,\u201d and users may then see the message: \u201cSomething didn\u2019t go as planned. Undoing changes.\u201d The error code is 0x800f0922.<\/p>\n You can \u201callow the update to install by modifying an ESP registry setting,\u201d but you\u2019re warned that \u201cediting the registry incorrectly can cause serious system problems.\u201d That means backing up the registry first. Unless you\u2019re very confident in doing this, do not attempt this workaround.<\/p>\n The better alternative is to \u201cmitigate the issue by using Known Issue Rollback<\/a> (KIR).\u201d Your PC might actually do that for you now, undoing the update once it fails. As such, users are also told that \u201crestarting your Windows device might help the resolution apply more quickly.\u201d<\/p>\n This update is critical as June\u2019s Secure Boot deadline<\/a> approaches. Certificates first issued in 2011 will expire for the first time and must be replaced. May\u2019s update brings \u201cincreased coverage of devices eligible to automatically receive new Secure Boot certificates.\u201d<\/p>\n