←back to thread

195 points _ol1s | 3 comments | | HN request time: 0.001s | source
1. firecall ◴[] No.41084458[source]
Looks cool, but what does this do that the standard Windows Recovery Environment Partition doesnt do?

Maybe situations where the standard recovery env is borked? Was that the case in the recent CrowdStrike debacle?

replies(1): >>41084570 #
2. neRok ◴[] No.41084570[source]
> Was that the case in the recent CrowdStrike debacle?

Nah, it still worked fine on my work laptop and allowed to boot in to safe mode, which also worked (didn't crash).

replies(1): >>41084623 #
3. theGeatZhopa ◴[] No.41084623[source]
The biggest 3. problems in resolving clownstrike debacle are to know what and where to delete (if you don't know, you also can delete everything as well), bitlocker locked hard drives and having a lot of VMs running on Windows out there.

The first problem, however, is more significant, but you even won't come to solving if you've encrypted filesystem. And then you have to do it for each and every device/VM. It's just too much.

if you could boot into safe mode, then you already knew what to do and what to delete. Just imagine - bsod - you don't know why. A hint may be shown ;)