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

Windows auto install not working #663

Closed
sraedler opened this issue Dec 22, 2020 · 10 comments
Closed

Windows auto install not working #663

sraedler opened this issue Dec 22, 2020 · 10 comments

Comments

@sraedler
Copy link

The Structure

  • ventoy (folder)
    • ventoy.json
    • script (folder)
      • autounattend.xml
  • ISO (folder)
    • Windows10_20H2.iso
  • unattended_files (folder)
  • Windows10_20H2_privat.zip (containing a folder structure and files)

ventoy.json
autounattend.xml

The ventoy.json is attached as ventoy.log

I don't know why this is not working. The unattended setup is not executed.
The Windows10_20H2.iso is downloaded with the current Rufus version (German ISO file).
The autounattended.xml is also uploaded as autounattended.log. It should just skip all steps except the WIFI setup. The key is just a dummy found on the internet.

However, once I had a hint that the EULA is missing. Nevertheless, I can not fix this issue.

Could you please help me out?

@ventoy
Copy link
Owner

ventoy commented Dec 22, 2020

{
    "control": [
        { "VTOY_DEFAULT_MENU_MODE": "1" },
        { "VTOY_FILT_DOT_UNDERSCORE_FILE": "1" }
    ],
    
    "auto_install" : [
        {
            "image": "/ISO/Windows10_20H2.iso",
            "template": "/unattended/autounattend.xml" <===== Is this the correct path?
        }
    ],
    
    "injection": [
            {
            "image": "/ISO/Windows10_20H2.iso",
            "archive": "/unattended_files/Windows10_20H2_privat.zip"
        }
    ]
}

Should "/unattended/autounattend.xml" be "/ventoy/script/autounattend.xml" ?

@sraedler
Copy link
Author

sraedler commented Dec 22, 2020

Yes, sure!

I just uploaded the wrong version. The correct one here: ventoy.json

Additionally, the ventoy tool is not telling any issues.

If I start the unattended setup, the xml is not executed. The first time this occurs: "An unexpected error occurs. Please restart the setup" (roughly translated)
After restarting, the following image could be seen after the first manuelly executed step (entering the key): image

@ventoy
Copy link
Owner

ventoy commented Dec 22, 2020 via email

@ventoy
Copy link
Owner

ventoy commented Dec 22, 2020

If you don't set the autoinstall configuration, does it setup successfully?

@sraedler
Copy link
Author

sraedler commented Dec 22, 2020

Did it prompt you to select boot with or without autoinstalltion?
yes, it prompts. I select autoinstall.

If you don't set the autoinstall configuration, does it setup successfully?
Yes, I can install it if I click start without autoinstall

Maybe it is because I checked "secure boot" on the ventoy setup?

Edit: Recently, I realized that a part of the autoconfig is executed (the first steps are skipped).
Nevertheless, the autounattend.xml works if I integrate it into the iso using ntlite (it is extracted from that image).

Can you propose a xml that you used for testing? I just want to skip all steps

@DX37
Copy link

DX37 commented Dec 25, 2020

Can you propose a xml that you used for testing? I just want to skip all steps

I can give you successfully tested unattended file - skip_oobe.txt. Please rename it's extension to xml and try it.

@sraedler
Copy link
Author

sraedler commented Jan 7, 2021

@DX37 thanks for the suggestion and sorry for my late reply!

Unfortunately it does not work. The xml is executed as well as it is with my xml file. However, the file does not work with the windows version.

@steve6375
Copy link

The error message can be caused by the wrong Product Key being used in the XML file.
It can also be caused by lack of memory RAM in the system. I think Ventoy requires more RAM than a normal flat-file boot.

@ventoy
Copy link
Owner

ventoy commented Jan 14, 2021

The error message can be caused by the wrong Product Key being used in the XML file.
It can also be caused by lack of memory RAM in the system. I think Ventoy requires more RAM than a normal flat-file boot.

Not exactly.
Ventoy just requires little additional RAM when booting Windows (1~2MB).

@sraedler
Copy link
Author

I was able to make this work after hours and plenty of tests.
However, I have no idea about the problem and how I solved it.

Thanks for your help!

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

4 participants