Frequently Asked Questions (FAQ)
Frequently asked questions when using EASYDEPLOY, compiled from the Docs and Troubleshooting. If you do not find your issue here, see the detailed topics in Troubleshooting.
License
Section titled “License”Why do I see “Invalid / expired / wrong USB license”?
Section titled “Why do I see “Invalid / expired / wrong USB license”?”The license (*.lic) is bound to the USB-SN and has an expiry date. Verify:
- The
*.licfile is placed correctly inEASYDEPLOY\on the correct registered USB. - The license has not expired and the service tier matches the features in use.
If the error persists, contact CoreSystem for a re-issue or re-key (when the USB is damaged/lost). Details: Troubleshooting.
Does low-quality USB affect licensing?
Section titled “Does low-quality USB affect licensing?”Possibly. The license is bound to the USB’s serial number (SN) — some low-cost USB drives lack a standard SN or share duplicate SNs across units, causing the license to be recognized incorrectly. Use branded USB drives with stable firmware (see License Tiers).
Deployment
Section titled “Deployment”No disk visible when selecting the target?
Section titled “No disk visible when selecting the target?”Typically caused by a missing storage/controller driver (e.g., Intel RST/VMD, RAID). The standard USB covers common hardware well; for specialized hardware, add the driver via BootBuilder (see BootBuilder).
Windows is not activated after installation?
Section titled “Windows is not activated after installation?”EASYDEPLOY only orchestrates the installation process and does not handle Windows activation. Activation follows the customer’s model (Retail, Volume/KMS, MAK, etc.). Clarify the activation model when preparing the configuration (see Deployment Modes).
“Offline image hash mismatch” error?
Section titled ““Offline image hash mismatch” error?”The local .esd file has been renamed, modified, or corrupted — it does not match the hash in the Catalog.
Re-use the exact file downloaded from the Catalog (see Troubleshooting).
Service Tier
Section titled “Service Tier”Is there a “standard” or “trial” license?
Section titled “Is there a “standard” or “trial” license?”No. There are two plans: Free (no license) and MSP Advanced (annual, USB-SN bound). BootBuilder accepts only a valid advanced license for whitebox builds; anything else builds in Free mode (2 profiles).
Can I capture an Autopilot hardware hash in WinPE?
Section titled “Can I capture an Autopilot hardware hash in WinPE?”Yes — Tools → Autopilot Hash. It writes an Intune-ready CSV (capture only; no cloud registration). Import it before the device reaches OOBE. See Autopilot hardware hash.
Do I need an ARM64 PC to build ARM64 media?
Section titled “Do I need an ARM64 PC to build ARM64 media?”No. BootBuilder runs on an x64 build workstation; the TARGET selector picks the ARM64 ADK, ESD and PowerShell payload. See ARM64 media.
Where is my inventory data?
Section titled “Where is my inventory data?”- Every tier:
Inventory-<key8>-<ts>.json+.csvon the OS volume (C:\) and the USB root. - MSP Advanced: the same local files; additional forwarding options are documented in the private package supplied with the license.
Local inventory is always written, including when the network is unavailable. CoreSystem does not receive your data — see Inventory Data and Telemetry Policy.
Cannot connect to WiFi in WinPE?
Section titled “Cannot connect to WiFi in WinPE?”Check the SSID/password, or the WiFi card may not be supported by WinPE — you need to integrate the driver via BootBuilder (see Troubleshooting).
Which flow should I use: Standard, Business, or Express?
Section titled “Which flow should I use: Standard, Business, or Express?”- Standard (1): Install clean Windows with no customization.
- Business (2): Install with an enterprise profile.
- Express (F3): Automated via pre-configured settings — suitable for large-scale deployment.
Details at Deployment Modes.