Remove a Windows Partition that is not showing up in Boot Camp Assistant?

KyokoNoBasuketto wrote:

I understand the breakdown to where the space is being used.

Can you post the output of the other commands?

However, since I've never used Boot Camp before (and a quick search said to re-run the assistant to remove the partition) - I'm stumped as to it not appearing in Boot Camp Assistant as it should.

This is confusing. If you have never used Bootcamp before, how did you install Windows on this Mac? How should it appear in Bootcamp Assistant?

I'd love to know why it's not showing there but at this point I would like to know the best option to remove this partition. According to this site there should be some kind of option to uninstall Windows. I want to know why that first step is missing (hitting continue takes it straight to the photo I showed previously).

There has never been an option to uninstall Windows, but a remove option. You are most likely confused between variations in Bootcamp UI. Please see Bootcamp User Interface . If you run the BC Assistant on your specific model, there is a 'Restore' option. On older Macs, there is a Install / Remove options as detected by BC Assistant.

Has Windows been successfully installed and bootable on this Mac? Did you look at step 4 in the link I previously posted?

If the Select Tasks step appears, select “Remove Windows 7 or later version,” then click Continue.

KyokoNoBasuketto wrote:

About the disk space: Yes, that is the worst case scenario, because I really don't want to have to do a time machine backup. Just a little inconvenient.

Yes, but can save you a lot time/energy when things go kaput. 😉

About the BC UI: Should this screen still not be present? Anywhere I look in regards to using BC Assistant on Sierra still shows this option, unless I can see otherwise.

Did you see this screen during your installation sequence? The BC UI is driven by Mac Model Identifiers and can be different for different models. I have a 2012 Mac which shows this, but a 2015 Mac should show the screen in my document link.

I think I will just use Disk Utility to erase the partition, mount the EFI partition and then remove the Windows boot loader. I don't trust that BC Assistant isn't going to mess this up.

And you trust Disk Utility to do the 'right' thing? 👿.

How do you plan to take the 'erased' disk space and merge it into the OS X CoreStorage volume? You are running FileVault2 as well.

I will strongly advise against bypassing BC Assistant.

Restore option will remove the existing Windows partition and merge the freed up disk space with the OSX partition. Is the goal to remove Windows and then re-install it?

Please also see Boot Camp for Mac: Remove Windows from your Mac .

I have the exact same picture as shown in Re: Remove a Windows Partition that is not showing up in Boot Camp Assistant?

Gonna restore macOS to normal state and create new BOOTCAMP again today, wanted to install different Windows build anyway. Hoping that "Restore disk to a Single Volume" won't make any harm to existing macOS partition.

There are two different methods of counting bytes on disks, which do not agree with each other. Integral power of 10 or powers of 2. You are not losing space, but seeing the two different interpretations of such calculations.

From OS X Terminal, post the output

diskutil list

diskutil cs list

sudo gpt -vv -r show /dev/disk0

It is a very easy calculation.

In the output of you GPT command, notice the gap between GPT3 and GPT4 which is 15,625,048 512-byte sectors, which is

15,625,048 / ( 2 * 1000 * 1000 ) = 7.81 GB

15,625,048 / ( 2 * 1024 * 1024 ) = 7.45 GiB.

Your total disk space is 977,105,060 512-byte sectors which is ~ 488 GB or ~465 GiB.

If you 'Restore' your disk to a single partition, then this space will also be added back to OS X.

If you are uncomfortable, please back up OS X first, before you click on Restore.

After perusing the entire thread, I have to ask: did you rename the original MacOS boot volume/partition at any time, especially after setting up the Windows part?

I find it troubling that it shows up named " ". Is it one space? Two spaces?? Or no spaces??? In the recent past when the cats died out and CoreStorage showed up, I had issues when resizing or in general munging with partition sizes, placement and type. Whenever volume names got mixed up, mayhem started in a similar fashion to what you describe. Usually ended up having to reformat/redo the entire drive to get things right again.

I would call upon any CoreStorage guru to give this a review and suggest actions to follow. Pretty sure there's a mis-synchronization issue between the various bits and pieces that comprise the drive's data structures.

I have seen several issues with the Sierra CS management. El Capitan seems to much more stable. FV2 complicates the cleanup, unless OP disables FV2 and reverts back to the underlying JHFS+. OP also has LV and Volume name as null.

CS has no renameVolume unlike JHFS+.

This reminds me of how OS X 7 Lion used to trash a CS partition table when you inadvertently plugged a drive in. Lost more than one to that. Pity that, from what you say, Sierra might be a step back too. This reaffirms my decision to stay with ElCap and probably skip Sierra altogether.

OP, sorry for the distraction. Now back to your troubles and tribulations.

romazhuzha wrote:

Hoping that "Restore disk to a Single Volume" won't make any harm to existing macOS partition.

You should one (or two) external disk backups for safety, irrespective of this. Software can fail. Safety First.