๐ Secure Bits ๐ก
โ๐๐ฒ๐๐๐ถ๐ป๐ด ๐ช๐ถ๐ป๐ฑ๐ผ๐๐ ๐ฅ๐ฒ๐ฎ๐ฑ๐. ๐๐ผ๐ปโ๐ ๐๐๐ฟ๐ป ๐ผ๐ณ๐ณ ๐๐ผ๐๐ฟ ๐ฐ๐ผ๐บ๐ฝ๐๐๐ฒ๐ฟ.โ
Weโve all been thereโstuck for what feels like forever. ๐ช๐ต๐ฎ๐ ๐ฐ๐ฎ๐ป ๐๐ผ๐ ๐ฑ๐ผ?
โ
Wait (sometimes works, but usually max ~1 hour after updates, or ~5โ10 min without updates)
โ
Hard reset (risk of data loss, especially with things like databases)
โ
Orโฆ a smarter option: ๐ฟ๐ฒ๐บ๐ผ๐๐ฒ ๐๐ฟ๐ผ๐๐ฏ๐น๐ฒ๐๐ต๐ผ๐ผ๐๐ถ๐ป๐ด.
Recently, I had to use this in a customer environment and realizedโmany people donโt know this trick.
Even when RDP and the local GUI are unavailable, you often still have management paths open:
๐ฅ ๐ฅ๐ฃ๐: Get-Service -ComputerName โฆ, Get-Process -ComputerName โฆ
๐ฅ ๐๐จ๐ (RPC): compmgmt.msc โ connect to the stuck machine
๐ฅ ๐ช๐ถ๐ป๐ฅ๐ : Enter-PSSession, Invoke-Command
๐๐ฒ๐ฟ๐ฒโ๐ ๐บ๐ ๐ด๐ผ-๐๐ผ ๐บ๐ฒ๐๐ต๐ผ๐ฑ:
1๏ธโฃ Enter-PSSession to the machine
2๏ธโฃ Check services for anything in StopPending
3๏ธโฃ Identify the related process (often TrustedInstaller in my cases)
4๏ธโฃ Kill the process
5๏ธโฃ Watch the system recover and finish shutdown/reboot โจ
โ Yes, thereโs some risk, but in practice, this has saved me from resets without impact.
Whatโs your go-to move when you hit this situation?
