That thread is nuts! More than two years of complaints about the installer bricking the OS, followed by crickets from Docker and the thread being automatically closed. Yikes! How can you have a piece of software which you know might completely corrupt the user's OS just by installing, and not at least notify the users next to the Install button? "Warning: may be Docker, may be virus, use at your own risk."

Not actually bricked, I assume -- your laptop has not been "turned into a brick", just had the OS corrupted, right? You could presumably wipe and reinstall Windows to fix it.

(Not saying that doesn't suck, just arguing with the terminology.)

You’re right formatting the drive would work.

But reinstall Windows crashes, USB recovery drive only helps copy files from command line, system restore points all crash. “OS corruption” sounds like it can be repaired while keeping files, but this is worse than that.

> OS corruption” sounds like it can be repaired while keeping files

If it corrupts your OS and it corrupts your files, that sucks, but it's not bricking unless it's impossible to install a working operating system.

So as a last resort you'd have to boot a live image (windows or linux) to extract docs and configs in order to reinstall from zero ?

I fucking hate docker on linux but that issue is so much worse with a cherry of "Closed issues are locked after 30 days of inactivity". I can't tell if it was fixed or not.

Looks like breaking Windows is a feature now, going by the last comments in that issue.