• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Sysprep - Windows could not complete the installation

    Scheduled Pinned Locked Moved Solved
    Windows Problems
    5
    8
    4.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • RobTitian16R
      RobTitian16
      last edited by

      Server
      • FOG Version:
      • OS:
      Client
      • Service Version:
      • OS:
      Description

      Hi all,
      I’ve just built an image in a Hyper-V VM, set-up an unattend.xml file using the Windows System Image Manager and set the VM to sysprep. However, upon boot I now receive: “Windows could not complete the installation. To install Windows on this computer, restart the installation”. This then loops repeatedly, until I open a command prompt and start ms oobe to bypass the user account screen.
      Has anyone come across this before? I know how to fix it, but how do I prevent it in the first place? I can post my unattend.xml file if it helps.

      1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott
        last edited by

        This can happen for any number of reasons.

        In particular, if the FOG Client hasn’t been disabled, this problem may occur as the client may cause the device to reboot before sysprep has finished.

        I’ve also seen this happen because when you went to capture the image, before you created the task the system rebooted and started going into windows, was then caught and powered off, then captured.

        Drivers can cause this problem as well.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 1
        • PsycholiquidP
          Psycholiquid Testers
          last edited by

          Might help to know the OS your capturing. Windows 10 and Windows 7 act completely different in regards to unattend.xml files.

          RobTitian16R 1 Reply Last reply Reply Quote 0
          • RobTitian16R
            RobTitian16 @Psycholiquid
            last edited by

            @Psycholiquid I’m capturing a Windows 10x64 system.
            I put the system into Audit mode to build the image, copied the unattend.xml file across and then told it to perform a sysprep with the out of box experience. I also checked the ‘generalize’ box.

            I haven’t installed the FOG client on this system (it’s installed using a postdownload script on the FOG server) and I haven’t installed any drivers, either (I intend to install them using a postdownload script depending what machine it is).

            george1421G 1 Reply Last reply Reply Quote 0
            • george1421G
              george1421 Moderator @RobTitian16
              last edited by

              @RobTitian16 said in Sysprep - Windows could not complete the installation:

              I haven’t installed the FOG client on this system (it’s installed using a postdownload script on the FOG server)

              Just to reconfirm, you have not installed the FOG client on your reference image? We have seen if the fog client is enabled, it starts doing its job before OOBE is setup causing the error you posted. Its not possible to install the FOG Client using the postdownload script. The post download script runs in linux and the fog client is windows.

              I HAVE seen this error happen when a driver either isn’t installed or breaks the install and causes OOBE to reboot unexpectedly. When this happens you can press Sift (or Ctrl) F10 to get a windows command prompt and then inspect the unattend install logs. Just google the error message you have and there are exact instructions on using the F10 key to get a command prompt open and which logs to review. This is not a FOG issue but a windows OOBE issue.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

              RobTitian16R 1 Reply Last reply Reply Quote 0
              • sudburrS
                sudburr
                last edited by sudburr

                Antivirus can also do this. Have you tried letting the original VM boot?

                [ Standing in between extinction in the cold and explosive radiating growth ]

                1 Reply Last reply Reply Quote 0
                • RobTitian16R
                  RobTitian16 @george1421
                  last edited by

                  @george1421 Sorry; to clarify: the FOG client is installed from the setup.cmd script. The fog.postdownload script calls fog.postclient, which copies the setup.cmd script from the FOG server across to the Windows installation and then appends the .cmd script with the instructions to install the FOG client.
                  That step isn’t being hit yet, though.

                  I don’t think it could be drivers considering this is a Hyper-V VM… I haven’t had to install any.
                  Checking the sysprep error log in C:\Windows\System32\Sysprep\Panther, it says:
                  "[0x0f0043] SYSPRP WinMain: The sysprep dialog box returned FALSE.
                  (This repeats for 5 lines)
                  [0x0f00a4] SYSPRP WinMain: Unable to parse command-line arguments to sysprep;m GLE = 0x0

                  @sudburr I don’t have any anti-virus installed on the image.

                  RobTitian16R 1 Reply Last reply Reply Quote 0
                  • RobTitian16R
                    RobTitian16 @RobTitian16
                    last edited by

                    It appears it’s an issue with the Unattend.xml file. I’ve tried one that has worked in the past and that’s absolutely fine.

                    Thanks for the help, gents!

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    • First post
                      Last post

                    165

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project