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

uefi and legacy installation #6

Open
abdullah-erturk opened this issue May 16, 2024 · 1 comment
Open

uefi and legacy installation #6

abdullah-erturk opened this issue May 16, 2024 · 1 comment

Comments

@abdullah-erturk
Copy link

I edited the action.bat file for both uefi and legacy installation, there is no problem in the backup part, but after selecting the mbr or gpt of the disk in the restore part, it goes back to the mbr or gpt selection of the disk. After selecting mbr or gpt for the second time, it starts to restore the wim file, but it fails when it reaches 99% level. Can you help me edit the action.bat file to suit both uefi and legacy installation?

action bat file is attached.

Additionally, according to this edited bat file, 2 diskpart.txt files are required.

The first one is diskpart_GPT.txt
The second is diskpart_MBR.txt

The diskpart.txt file already exists in your project, you should recreate it according to the gpt and mbr disk structure.

Take these parts into consideration when doing your tests.

Since github does not allow bat files, I uploaded the action.bat file with the txt extension.

I'm looking forward to your answer.

Thank you very much in advance
action.bat.txt

@cregx
Copy link
Owner

cregx commented May 26, 2024

Hi, I couldn't find any obvious errors in your batch code. However, I have to admit that I am not an expert in batch programming. ;-)

If the error occurs during the restore process, especially in the DISM apply-image command at 99%, I would focus on that point. It might be helpful to run the CMD from the GUI and try the restore manually from there. This way, you might be able to find out more details about the problem.

A small suggestion: if the error - which I find hard to imagine at the moment - occurs due to a problem in the diskpart section, you could include an if %errorlevel% neq 0 check after its execution. In the event of an error, you could then terminate further execution with exit /b %errorlevel%.

As I said, I have no other ideas at the moment. Good luck!

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

No branches or pull requests

2 participants