- The ISO is now mounted, resolved to a volume, and dismounted through the
storage CIM provider directly instead of through the "Storage" module, which
is not present within every Windows PE boot image. The "MSFT_DiskImage" class
is projected as cmdlets using the new "Toolkit\Libraries\Storage\DiskImage.cdxml"
definition, so only the storage CIM provider itself is required
- The volume is resolved through the "MSFT_DiskImageToVolume" association rather
than through "Get-Volume", and the drive letter is normalized because the
provider exposes it as a character
- Removed the "Storage" module requirement from the requires statement
- Added the "-InstallSpiceGuestTools" parameter, which downloads and installs the
SPICE guest tools. The installer is not digitally signed and exposes no version
resource, therefore the driver signing certificates are read from the driver
catalogs contained within the installer itself, imported into the trusted
publishers store, and the expanded content is then removed. The installer is
executed using its own normal installation method, which results in a
completely silent installation with no driver prompts
- Added the new "Import-TrustedPublisherCertificate" toolkit function, which
reads the signing certificate of each signed file within one or more
directories and imports the distinct certificates into a configurable
certificate store
- The archive utility required to expand the installer ships within
"Toolkit\Tools\X64" and is located by searching the architecture specific
directories, the architecture neutral directory, and then the local download
directory. It is only downloaded when no existing copy is present, and the
downloaded package is expanded using an administrative installation so that
the product itself is never installed
- Anything downloaded at runtime is written beneath "%WinDir%\Temp\<ScriptBaseName>"
so that a read only or UNC script location is never written to
- Both the guest agent and the SPICE guest tools are gated to the full operating
system and are skipped automatically within Windows PE, so a single command
line is safe for both deployment passes
- Updated the README with the Windows PE and full operating system command lines,
the gating behavior, and the SPICE guest tools details
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
