Hello, guys! It’s the second dual boot set-up that I made but now it’s not ordinary set-up but the one with the external boot partition, made directly on this manual of dear @apparatus. I liked his idea of deniable encryption so wanted to try. And honestly, was really surprised that I could do it on the first try (but had to spend several hours to do all really carefully and finished at two in the morning 
). But there is one thing that was unexpected and unwanted - there left visible partition in Windows file explorer. If during previous set-up I installed Qubes manually on raw (unmarked) disk partition and it wasn’t displayed in Windows explorer after installation (so even in “Disk Management” section this partition looked like just raw, unmarked section of disk), now I installed it on specially created regular ntfs disk partition since according to Apparatus’ manual you should to specify in terminal disk partition where you want to install Qubes and as I know you can’t specify raw, unmarked free disk space in terminal (at least brief searching didn’t help me to find out how). I expected that now this partition would disappear from Windows file explorer since it became unrecognizable for Windows just like in previous case but now it remained in file explorer as fully filled disk partition and now it looks like not so deniable encryption as was expected. Is there a way to hide this partition without its deletion and with the possibility of its further, normal functioning with Qubes inside (in other words I really don’t want to re-install Qubes from the very beginning 'cause this method really time expendable and requires a very large concentration)? Of course it will be still visible in Disk Management as unmarked, raw space (I hope so), but it will not look so suspicious as fully filled, unoperatable disk partition in file explorer.
Ok, if there is any method how to specify unmarked, raw partition, suitable for Apparatus manual then I agree to re-install Qubes once more. Does anybody know?
There is no such thing as a ‘hidden’ partition. Even if there would be, another OS still can just overwrite the whole disk - including it’s partition table - if decided to do so.
This is one of the reasons why we can’t call ‘dual boot’ ever ‘secure’.
If you not creating any partition table, just using the whole device as it is, then it would be shown as an unused disk for windows… however, in this case windows will constantly urge you to format it 
Well… In my previous case Windows was installed on one physical disk and there was another physical disk that was used as file storage. So I (if I remember correctly. And I believe I do) compressed its space and this way left the space as unmarked space. Then I chose it in Qubes installer in manual disk partitioning mode and Qubes was successfully installed on it. So then in Windows it looks like a disk with a certain amount of disk space (smaller than the original) and the space with Qubes is not displayed at all (if to speak about file explorer). In “disk manager” it’s displayed as raw partition but it’s functioning already two years and Windows never overwrote it. Unless there was only one other scenario possible - first I created new disk partition in Windows and then, during disk partitioning in Qubes installer, I manually deleted this partition, chose this free space as Qubes installation destination and let Qubes format it itself.
yeah, it would be cool to try this
@apparatus is crazy smart. he comes up with some interesting stuff that is just so high level
You mean Apparatus’ external boot manual? And by the way, where is he? Does anybody know? I expected him to appear in this thread. Then messaged him in PM regarding this thread but he didn’t answer.
no idea where apparatus is. hope apparatus is ok
Hi, folks! A question again! @Apparatus said that the trimming ruins Deniable Encryption principle. It’s enabled in Qubes by default and should be disabled in external boot set-up. But neither in this or this articles he added in his manual, is said anything about how to disable this function. I tried to find anywhere else but there is the same picture - everybody tells how to enable it but nobody how to disable.
Apparently TRIM is not enabled by default in R4.2.4:
Love it when it turns out that nothing needs to be done and everything is done for us. 