Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to replace the default recovery image (winre.wim) in fresh Windows install? #193

Open
spotopolis opened this issue Dec 17, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@spotopolis
Copy link

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like

When using OSDeploy built using a Win10 recovery image, at the end of the DISM image process, I then replace the default Windows recovery boot image (winre.wim) with the custom built "boot.wim" that boots OSDeploy. This way, if I ever have issues with said machine, I can just boot to OSDeploy by booting directly from the recovery partition.

Is there a way for me to accomplish the same when running OSDCloudGUI? How can I tell OSDCloud before rebooting to copy:

 From:
      USB - WinPE:\sources\boot.wim
 To:
      R:\Recovery\WindowsRE\winre.wim

The below image is how I have been doing this in my WinPE image script. Its been working great. But I have not been able to find a way to replicate this with Windows installs through OSDCloudGUI. Is there a Global Variable I can toggle, or can I just add part of the existing scripting I have to one of the scrpting folders in the X:\OSDCloud\Config\ ?

image

@OSDeploy OSDeploy self-assigned this Jan 17, 2025
@OSDeploy OSDeploy added the enhancement New feature or request label Jan 17, 2025
@OSDeploy
Copy link
Owner

I'll see if I can get this supported in OSDCloud v2, but you should be able to not have OSDCloudGUI reboot when complete, then run your script and reboot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants