I can confirm this exact same issue, yesterday i made an installation in my laptop, cnchi updated itself to 0.12.15 an everything went fine, but today this morning when i wanted to install in my desktop (note that i use the same installation media which i wrote with dd and worked at first in my laptop) the installer updated itself to 0.12.22 and showed this error after downloading and installing the packages, right in “configuring system” or something like that.

Temporary work around until next version of cnchi is released. I got it installed by downgrading the cnchi package to version 0.12.12. It is still in the pacman cache so you can downgrand and run cnchi again to do an install.

cd /var/cache/pacman/pkg/

pacman -U <file_name_of_the_package>

I found after trying to mount my lvm2 partition that the install deleted my lvm2 partition that was not even on the same disk that I installed to! Why would the installer do that? This is a major bug. Any idea how I can get my lvm2 partition back? I had backed up all my data to this partion before I started the Antergos install. Man, what a messed up distro this is.

@yellowsnow4free There’s something that I don’t understand, well let me try to explain myself.
I installed Windows on my mSata SSD and then tried to install Antergos, I got a error meanwhile installing grub, I posted it here: http://forum.antergos.com/topic/2926/antergos-stuck-at-installation
after this, windows boot was gone.
so, I decided to try to install Ubuntu, Ubuntu installed normally (grub on mSata) and then, when I tried to boot, nothing was booting, and I lost the windows boot, So I thought, it has to be the mSata, can’t install grub there.
I decided to retry the Antergos install and put the grub in the normal disk (not the mSata), that time, I had this problem (cant convert bool object to…) with seems to be solved.
After this, my windows boot was totally gone, I don’t know why that happened (I was installing the grub in another disk!), and I couldn’t recover the windows boot, I had to reinstall totally, not even the fixmbr or fixboot commands in the windows installation ISO worked to me.

And now, I had to install Ubuntu, and installed the grub on the normal disk (not the mSata), it works normally, I just have to switch the boot disk.
mSata disk is first, so… It boots windows normally if I don’t select from what disk boot from
If I’m going to use Ubuntu, simply change the boot priority to the normal disk, Ubuntu is installed on the mSata disk.
I only have the grub on the normal disk.

Why something like that would happen, even I’m installing the grub in the normal disk, the mSata boot of windows was gone.

Thank you for reading, sorry if there’s grammatical mistakes, my English is not that good.