Windows AppVM persistent storage

My Windows AppVMs keep resetting on reboot. I’ve set up a Windows 10 TemplateVM and have Windows AppVMs based off it. It seems that AppVMs do not have any properties of their own and upon reboot just copy the template again, deleting any files or apps installed in the AppVM. Furthermore, Windows AppVMs show 0 disk usage, only the template has any disk usage (which sort of makes sense as to why this happens).

Is there any way to make it behave like normal fedora qubes with private storage?

That is normal

clone it to create a other HVM

Creating another HVM is not the answer.

The issue is that you have installed some OS on /dev/xvda - the system
disk - in a template.
When you create qubes using that template, they will get the file system
from the template, and will have their own /dev/xvdb.
But, you have not told the system what to do with /dev/xvdb, and the
whole file system is pulled from the template. That is why any changes
you make are lost when you shutdown the qube.

Windows has Qubes Windows Tools, and an option there to move the user
profiles to /dev/xvdb.
This will make your Windows qubes behave like other template based
qubes, with each Windows qube having its own User directories.

For other OS Templates, you have to set /etc/fstab to mount /home on
/dev/xvdb, and then populate /home with /home/user, etc in the qubes.

i’m don’t know much about QWT (i hate windows)

I have QWT installed in my Windows template, I’m able to move files into it from other qubes, etc. How would I go about moving user profiles to /dev/xvdb?

I needed to customize the template to my desired settings to pass the persistence to the AppVM.

For private storage persistence in your AppVM, I think you need to initialize and format your 2GB private storage. Go to Administrative Tools > Computer Management > Disk Management. I found the files saved there are persistent.