Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Futures Kickoff
Get prepared for your futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to experience risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Microsoft's February cumulative update: Some Win11 users report infinite rebooting
IT Home, February 13 — Technology media BornCity published a blog yesterday (February 12) reporting that some Windows 11 24H2 and 25H2 users have experienced device boot loops after installing the February cumulative update KB5077181 from Microsoft. Some devices get stuck at the login screen and automatically restart more than 15 times.
IT Home notes: During the February Patch Tuesday (February 10), Microsoft released the cumulative update KB5077181 for Windows 11 24H2 and 25H2, which includes multiple quality improvements and security patches, as well as updates to Secure Boot certificates.
A user posted in the community describing the issue: after the update failed to install, the system attempted to roll back, showing “Undoing changes made to your computer” but then entered a dead loop.
When the user tried resetting the BIOS and clearing Secure Boot keys, the system directly reported “Secure Boot violation, invalid signature detected,” ultimately causing the keys to be lost and unrecoverable, forcing a switch to CSM (Compatibility Support Module) mode.
In addition to the boot loop, the update also caused chain system failures. Some users who managed to access the login screen received errors saying “System Event Notification Service failed to log in,” and running sfc /scannow showed corrupted system files.
Furthermore, some users reported Bluetooth functionality failure after the update, or encountered errors such as 0x800f0983, 0x800f0991, and 0x80073712 during installation, indicating missing or corrupted files.
In response to these issues, independent advisors in the Microsoft community recommend affected users uninstall the update immediately. If the device cannot boot into the desktop normally, users should try entering Safe Mode, open Command Prompt (CMD), and run the following command to force uninstall the patch:
wusa /uninstall /kb:5077181 /quiet /norestart