Skip to content

[FEATURE] Merge NTLite and Winhance autounattend.xml configurations #511

@cocolight

Description

@cocolight

Please confirm these before moving forward

  • I have searched for similar feature requests and have not found a duplicate.

Feature Type

New functionality

Describe your feature request

[Feature Request] Merge NTLite and Winhance autounattend.xml configurations

Problem

When using both NTLite and Winhance, each tool generates a complete autounattend.xml. Manual merging is error-prone because:

  • NTLite configures language settings (e.g., zh-CN) that should be preserved
  • Winhance embeds PowerShell scripts in <Extensions> node that cannot be simply copy-pasted
  • Multi-architecture components (x86/arm64/amd64) are easy to miss

Desired Solution

Option A: Incremental Export

  • Export only Winhance optimization snippets (without base settings)
  • User merges into existing NTLite XML

Option B: One-Click Merge Tool

Input:  NTLite_autounattend.xml + Winhance_autounattend.xml
Output: Merged_autounattend.xml

Rules:
- Keep NTLite International-Core (language/region settings)
- Keep NTLite empty ProductKey
- Merge Winhance OOBE optimizations
- Inject Winhance <Extensions> PowerShell scripts
- Auto-handle x86/arm64/amd64 components

Use Case

After creating a slimmed image with NTLite, automatically apply Winhance optimizations during Windows setup without running Winhance manually on each machine.

Key Requirements

Keep from NTLite Add from Winhance
Language/region settings Hardware bypass checks
Empty ProductKey System optimization scripts
Base OOBE config Services/privacy/performance tweaks
FirstLogonCommands

Use case

When creating a system image with NTLite, Winhance optimization settings can be integrated simultaneously.

Software Details (Only for 'New software to be added' requests)

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions