

Also consider opening up your PC and physically unplugging the Windows drive, at least until you get your Pop! install sorted.
I just want to highlight this for OP, this is great advice.
It accomplishes two things:
- It keeps the Windows drive from being accidentally changed.
- It helps the motherboard decide to boot into Linux.
And of course, if OP needs to focus on booting back into Linux, the opposite also applies - removing the POP_OS drive can help the motherboard decide to boot back to Windows.
There’s ways to use BIOS to tell the motherboard which drive to boot to, but doing that doesn’t also protect the drive from changes. So I like to remove the drive I am not changing at the moment.
Here’s some videos:
https://youtu.be/-Qkn5uZUiJg https://youtu.be/6Puffq24nl8 https://youtu.be/_IPqfCy8Uew
And tips for OP from my own experience:
- I have not seen a heat sink of top of an SSD before. There’s a good chance OPs computer doesn’t have one, and that’s fine.
- The SSD might be any length between about an inch to about four inches. There’s usually multiple spots where the clip that holds it in could be installed, but OP shouldn’t need to move the clip.
- Those plastic clips can look very different, and may or may not need to be fully removed to get the drive out. I just fiddle gently with them until I can get them out of the way, or back. I usually end up accidentally removing them, but they go back in.
In case ops needs more videos, the search terms I used were “Remove NVME SSD”.






But studies are showing it doesn’t work.
A human makes a mental model of the entire system, does some testing, and submits code that works, passes tests, and fits their unstanding of what is need.
A present day AI makes an educated guess which existing source code snippets best match the request, does some testing, and submits code that it judges is most likely to pass code review.
And yes, plenty of human coders fall into the second bracket, as well.
But AI is very good at writing code that looks right. Code review is a good and necessary tool, but the data tells us code review isn’t solving the problem of bugs introduced by AI generated code.
I don’t have an answer, but “just use code review” probably isn’t it. In my opinion, “never use AI code assist” also isn’t the answer. There’s just more to learn about it, and we should proceed with drastically more caution.