Citrix Applayering Packaging VM boot error 0xC000000F

Citrix Applayering Packaging VM boot error 0xC000000F

book

Article ID: CTX327971

calendar_today

Updated On:

Description

Application layer packaging VM boot fails with the boot error 0xC000000F

Untitled.png

The above given error appears on the packaging VM while you create a new application layer/edit an application layer with an OS layer version where the language packs are newly installed, but this boot failure doesn't appear while you create a packaging VM for OS layer's new version or Platform layer packaging VM

Resolution

Solution 1:
  1. Create a new connector/Edit the connector and set the “Packaging Cache Size in GB” to 0 ( Ref: https://docs.citrix.com/en-us/citrix-app-layering/4/connect.html#disable-or-re-enable-caching )
  2. Build a new app layering using the OS layer with required language pack/s

 

Solution 2 ( Recommended) :

 
OS Layer:
  1. Create a new version to the OS layer’s base( Let’s consider OS 1.1 as base)
  2. On the packaging VM, append the *.NLS files entries from “C:\windows\system32” into "C:\Program Files\Unidesk\Uniservice\bootfile.txt"
  3. Perform the Ngen update, finalize the layer(Let’s say this new layer name is OS 1.2)
  4. Create a new version of the OS layer( Let's say OS 1.3)
  5. Install required language pack/s, reboot as required
  6. Modify the required Unicode settings, reboot as required
  7. Ngen update( Ref: https://docs.citrix.com/en-us/citrix-app-layering/4/layer/update-layer.html#expedite-microsoft-ngenexe-operations-if-necessary) and finalize the OS Layer
App Layer: Create a new application layer pointing our to OS 1.3 layer

Note: While adding the entries for NLS files on "C:\Program Files\Unidesk\Uniservice\bootfile.txt", you will have to ensure the backward slashes are replaced with forward slash. For example, "C:\Windows\System32\C_870.NLS" should be mentioned as "C:/Windows/System32/C_870.NLS"

Problem Cause

While a language pack is installed over OS layer versions, there are chances that the respective NLS files aren't written to bootfile