Two first-boot hazards the sealed path hits that the baked path does not,
fixed in a configMedium-only variant of the data-disk init (the shared
path is byte-identical):
- The per-VM config rides an optical drive. On the target's first boot
the data disk is still raw and unlettered, so Windows gives the CD D:
-- where the profile volume must go. The plain `if exist D:\` guard
then sees the CD and skips, stranding ProfilesDirectory on read-only
media. Now a marker (not the letter) tracks first boot, and any
occupant of D: is parked on Y: before the data disk claims it.
- Left to Shell-Setup's FolderLocations, ProfilesDirectory can be
evaluated before the disk exists (unordered within specialize) and
fall back to C:. It is now written to the registry in the same step
that just created the volume, so the volume always exists first.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0117qMyjpuXsjpVAcpJbFD8g
Git Sagar
ee002586e5