You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft provides specific recovery images for each of their Surface devices. These images aren't packaged as ISO files but instead come as a ZIP file that contains both a boot.wim and install.swm.
Currently, when we boot into the boot.wim, it doesn’t detect the install.swm because it’s located in the wrong directory, which prevents access to the recovery option. Direct .swm support in the Ventoy menu would allow users to select the file and automatically initiate installation on the device, with the WIM file acting as an intermediary.
With OSDCloud, this process expands the image directly onto the drive, bypassing manual setup and providing a more streamlined experience. Adding native support for .swm files would be a significant improvement, as this approach has been successfully tested in WinPE with OSDCloud.
Additionally, since Microsoft sometimes includes .esd files in these packages, it may be valuable to consider adding support for .esd files as well.
Thank you for considering this feature request!
The text was updated successfully, but these errors were encountered:
Official FAQ
Ventoy Version
1.0.99
What about latest release
Yes. I have tried the latest release, but the bug still exist.
Try alternative boot mode
Yes. I have tried them, but the bug still exist.
BIOS Mode
UEFI Mode
Partition Style
MBR
Disk Capacity
64GB
Disk Manufacturer
SanDisk
Image file checksum (if applicable)
None
Image file download link (if applicable)
https://support.microsoft.com/en-us/surface-recovery-image
What happened?
Microsoft provides specific recovery images for each of their Surface devices. These images aren't packaged as ISO files but instead come as a ZIP file that contains both a boot.wim and install.swm.
Currently, when we boot into the boot.wim, it doesn’t detect the install.swm because it’s located in the wrong directory, which prevents access to the recovery option. Direct .swm support in the Ventoy menu would allow users to select the file and automatically initiate installation on the device, with the WIM file acting as an intermediary.
With OSDCloud, this process expands the image directly onto the drive, bypassing manual setup and providing a more streamlined experience. Adding native support for .swm files would be a significant improvement, as this approach has been successfully tested in WinPE with OSDCloud.
Additionally, since Microsoft sometimes includes .esd files in these packages, it may be valuable to consider adding support for .esd files as well.
Thank you for considering this feature request!
The text was updated successfully, but these errors were encountered: