Release Notes
The new version of Deployment Tool is required to deploy Kiosk Hardened Image 25.06.0
KIOSK Hardened Image 25.07.1 | |
---|---|
25 July 2025 | |
MD KIOSK version | 4.7.8.4064 Release Notes |
MD Core version | 5.15.0 Release Notes |
Windows OS version | Windows 10 IoT Enterprise LTSC (21H2, Build 19044.6093) |
BIOS version |
|
What's new | |
Application and system updates | Updated applications and system components to the latest versions (Windows 10 IoT Enterprise LTSC (21H2, Build 19044.6093), MD Kiosk 4.7.8, MD Core 5.15.0) to ensure optimal performance, security, and compatibility. Include Critical BIOS updates that address stability of 13th and 14th generation Intel processors in some models. |
New features supported for Kiosk Hardened Image Upgrade |
|
Enhanced Out-of-Box Experience (OOBE) process | Support OOBE initial configuration files Kiosk now support initial configuration files to automate the Out-of-Box Experience (OOBE) enable faster deployment at large scale. When the OOBE initial file exists, Kiosk will automatically proceed with the defined settings. It enables faster deployment at large scale |
Display key device information Key device information (including Serial Number, Kiosk Model, Image Version, Core Version, Kiosk Version, and OS Build) are displayed during the OOBE process to provide better visibility during setup. | |
Popup prompting when exiting Kiosk OOBE Kiosk Hardened Image now displays a popup message when the user exits the Out-of-Box Experience (OOBE), informing them of the consequences:
| |
Support custom script during OOBE process Supports running a custom script during the auto setup process. If a script is defined in the OOBE initialization file, the Kiosk will automatically trigger and execute the script during the deployment process. This allows additional customization and automation as part of the Out-of-Box Experience | |
Improve stability of Kiosk Hardened Image upgrade | Immediately stop the upgrade process when unable to complete the process Kiosk Hardened Image now halts the upgrade process immediately when critical conditions are detected, such as BitLocker being enabled or Core using HTTPS with a password-protected certificate. In such cases, clearer and more informative messages are displayed to assist with troubleshooting and resolution. |
Support Core configurations with excluded engines enabled Backup and upgrade now support MetaDefender Core configurations with excluded engines. Previously, such configurations could cause the upgrade to roll back. | |
Fixed Hostname backup and restore Resolved an issue where the hostname was not properly restored, which caused the Core deployment ID to change unexpectedly. | |
Known issues | |
Engine Status shows Invalid after OOBE Completion | After completing Out-of-Box Experience, the engine status may show as invalid even if all engines were downloaded and deployed successfully. This is a display issue. Reboot the system to refresh the engine status. |