When you create/edit layers in App Layering, a packaging machine is created.  If you have caching enabled, then a boot disk is created as well as copies of the OS layer and any relevant App Layer.  When the packing machine is booted, some system data such as the pagefile is stored on that boot disk.  By default that boot disk is 10GB.  There may be scenarios where that disk becomes full.  This could be something like using a large custom page file.  This could cause windows to behave erratically because it ran out of space even though you have plenty of free space on the actual OS or App Layer disks you are working on.   You can avoid this by changing the default size of the boot disk. You should be able to confirm in Disk Management how much free space is on the 10GB Boot disk.   

Instructions

Console or ssh into the ELM command line interface.

Logon as root

If Compositing Engine is enabled, Edit /usr/local/unitools/MAService.exe.config, otherwise edit /usr/local/CAMService/CAMService.exe.config

In the <appSettings> section add:

<add key="MiniBootDiskSizeInGb" value="10"/>

          Change the 10 to the value required. For example, to make the disks 20G use value="20"

Save the file

Restart cams:

systemctl restart cams

Any package machine created using Compositing Engine (with caching enabled) should now have a larger boot disk