Started refreshing the Windows Install article #973
Conversation
gangwerz
commented
Mar 23, 2022
gangwerz
commented
- Removed the VBox install section
- Need to add reference and link to Creating Virtual Machines in Linux article
- Back link to the Install section of this Windows article in the Creating Virtual Machines in Linux article
- Reordered a couple section for clarity
- Made the Win11 compatibility table collapsible (open by default)
- Merged the 2 install guides into 1
- There were 2 mostly full guides for the shared-drive and dedicated-drive processes. I merged these into a single section
- Added a rough draft of content from issue Expand Windows Install Article #951
|
Text above the "Selecting Pop!_OS or Windows" section is ready for review. |
There was a problem hiding this comment.
I'm a huge fan of this article consolidation. I suggested several minor consistency nitpicks, and the section covering copying Windows boot files needs another look-through for punctuation and formatting updates.
PR #1034 has some overlap with this PR, and should be taken into consideration.
Overall, great job.
| @@ -252,6 +115,14 @@ It may take several minutes or more for the process to finish -- wait until the | |||
|
|
|||
| --- | |||
|
|
|||
| ## Dual-Booting Windows with Linux | |||
|
|
|||
| Dual booting allows you to run 2 perating systems on the same computer. There are several ways to dual boot Pop!_OS and Windows. Make sure to follow the instructions for your specific situation: | |||
There was a problem hiding this comment.
We would typically write out numbers under 10: https://www.grammarly.com/blog/when-to-spell-out-numbers/
"operating" is missing an "o"
|
|
||
| If you need to install both operating systems on a single drive (for example, if your computer only supports a single SSD), it is possible to install both OS's using a custom partition scheme. Pop!_OS's full-disk encryption is not supported with this setup. | ||
|
|
||
| Start by [installing Pop!_OS](/articles/install-pop/), making sure to select `Don't Encrypt` during the installation process. | ||
|
|
||
| (System76 computers shipped with Pop!_OS give you the option of whether or not to encrypt on first boot. If you chose to encrypt at first boot, or if you reinstalled and chose to encrypt, you will need to reinstall without encrypting before proceeding. If you want to dual boot and also use full-disk encryption, you will need to [use a dedicated drive](#installing-on-a-dedicated-drive) instead.) | ||
|
|
||
| ### Shrinking Pop!_OS | ||
| #### Shrinking Pop!_OS |
There was a problem hiding this comment.
Is there a reason we bold header level four, but none of the others?
|
|
||
| Once Pop!_OS is installed (and not encrypted), boot into Recovery mode by holding down the spacebar during boot and selecting `Pop!_OS recovery` from the list of boot options. | ||
|
|
||
|  | ||
|
|
||
| Once Recovery mode has finished loading, select your language and keyboard layout, then select `Try Demo Mode` in the bottom left to exit the installer. | ||
|
|
||
| Next, open `GParted` by searching for it in the Activities menu (`SUPER`) or the Pop!_Shell launcher (`SUPER` + `/`). | ||
| Next, open `GParted` by searching for it in the Applications menu found at the top left of your primary display. |
There was a problem hiding this comment.
We've been putting menu call outs in back ticks: Applications
| Installing Windows to a **Dedicated Drive** | ||
|
|
||
| 1. Select the drive for Windows installation. | ||
| - This drive likely has 1 partition listed, or shows as "Unallocated Space" |
| Finally, the installer will ask you to select where you want to install to. In this scenario, we are installing Windows to a pre-made partition on the shared drive (if you're doing something else, see [Planning the Installation](#planning-the-installation)). | ||
| Finally, the installer will ask you to select the location where you want Windows installed. Please follow the instructions for the configuration you chose under [Dual-Booting Windows](#dual-booting-windows-with-linux) | ||
|
|
||
| Installing Windows to a **Dedicated Drive** |
There was a problem hiding this comment.
I'm wondering if this, the Shared Drive, and Windows Only sections should be headers?
| ### Using systemd-boot | ||
| #### Using the systemd-boot menu | ||
|
|
||
| Systemd-boot is the bootloader used by Pop!_OS. It can be used to select which operating system you would like to boot from. The steps below outline how to access the systemd-boot menu, and select an operating system: |
There was a problem hiding this comment.
Escape character missing in Pop!_OS
|
|
||
| If you installed Windows on a [dedicated drive](#installing-on-a-dedicated-drive), then the systemd-boot menu will not recognize the Windows drive right away. To make systemd-boot aware of the Windows installation, we will need to copy the Windows boot files from the Windows boot partition, to the Pop!\_OS boot partition. | ||
|
|
||
| 1. Boot to Pop!_OS |
There was a problem hiding this comment.
Escape character missing in Pop!_OS, also it appears periods are used inconsistently for the following list.
| - The EFI partition should be the 1st partition on the Windows drive, and will be around 100M in size | ||
| 2. Now mount the Windows EFI partition to /mnt | ||
| - sudo mount /dev/NAME where NAME is from the "name" column of the lsblk output for the EFI partition | ||
| - After mounting on a test machine, I ran ls -al /mnt/EFI and I was able to see a "Boot" and a "Microsoft" folder at this point |
There was a problem hiding this comment.
For consistency, we should not refer to ourselves in the 1st person. We use the implied "you":
I ran ls -al... vs Run ls -al
| - The EFI partition should be the 1st partition on the Windows drive, and will be around 100M in size | ||
| 2. Now mount the Windows EFI partition to /mnt | ||
| - sudo mount /dev/NAME where NAME is from the "name" column of the lsblk output for the EFI partition | ||
| - After mounting on a test machine, I ran ls -al /mnt/EFI and I was able to see a "Boot" and a "Microsoft" folder at this point |
There was a problem hiding this comment.
Since we place directories in backtics, we should probably use that same formatting when referring to folders.
|
|
||
| 1. Run the efibootmgr command in a Terminal. | ||
| - This will show you the available EFI boot entries found on your system | ||
| 2. Find the "Microsoft Boot Manager" line, we will need the 4-digit number found in the Boot000x section |
There was a problem hiding this comment.
Conventionally, any number under 10 would be spelt out "four-digit, one-time", etc.
https://www.grammarly.com/blog/when-to-spell-out-numbers/
Boot000x should probably be in backtics.
|
I'm coping some of these changes to this PR: #1034 but not closing it to keep the history for now. |
