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

    W10 22H2 "Windows could not complete the installation..." Upon Post-Upload/Post Sysprep Initial Boot

    Scheduled Pinned Locked Moved Solved
    Windows Problems
    2
    3
    714
    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.
    • J
      jrajra
      last edited by

      Hello all - old (very old) hand at FOG but getting some oddness with my latest venture.

      So, W10 goes on to VM, into audit mode, update fully, FOG service goes on, unattend.xml goes in C:\Windows\System32\Sysprep, image is drawn up successfully, then on reboot (expecting initial startup of W10) I get this:

      41fa457a-875c-4d8d-922d-b0c8a8f894e2-image.png

      However if I put NO unattend.xml in it goes to OOBE fine, which obviously I don’t want to be doing but suggests greatly some strangeness with unattend.xml

      Anyone seen this and have any ideas? Not strictly a FOG thing (most likely) but if it’s a common one and anyone knows what to do to shut it up I’d be very grateful!

      Thanks all.

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

        @jrajra said in W10 22H2 “Windows could not complete the installation...” Upon Post-Upload/Post Sysprep Initial Boot:

        VM, into audit mode, update fully, FOG service goes on, unattend.xml goes in C:\Windows\System32\Sysprep

        Just to confirm you installed the FOG server, but disabled it in the services applet according to the wiki? Then in your setupcomplete.cmd batch file you reenable the server?

        If NO, then that might be your problem. The FOG service will start doing its thing (renaming the system, connecting to AD, etc) before WinSetup/OOBE finishes, that is typically what generates that error windows reboots at an unexpected time during WinSetup.

        I’ve also see that happen if you have a bad driver install and windows reboots because it crashed.

        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!

        J 1 Reply Last reply Reply Quote 1
        • J
          jrajra @george1421
          last edited by

          @george1421 Thanks for that George, and also for all the help over the years!

          Had a tinker with unattend.xml and it’s fine now. Thinking it was the mismatch with local admin acct setup in there vs what I’d set locally initially, but all ok now.

          However have done none of the service off/restart it options post-sysprep (and was wondering even if I’d just put something in group policy later on that’d do it, as the last time I ran this having ANY setupcomplete at all broke the sysprep process) it was in fact just fine and happy. Maybe something in 22H2 Edu is just alright with it, or the stars aligned for me on that one.

          Either way all working now and thanks for diving in there. 🙂

          1 Reply Last reply Reply Quote 1
          • [[undefined-on, S Sebastian Roth, ]]
          • 1 / 1
          • First post
            Last post

          220

          Online

          12.0k

          Users

          17.3k

          Topics

          155.2k

          Posts
          Copyright © 2012-2024 FOG Project