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

    Error Windows image

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    17
    2.7k
    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
      Jmercier
      last edited by

      ok thank’s , i can give you more information now @george1421 , this error was on the computer capture , i tried to deploy this image on the same who capture , but now i tried on another computer and i after downloading image , i got another error " boot device not found " and it say /dev/nvme…

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

        @jmercier What program gives you the error “boot device not found”? Is that windows or FOG with the error?

        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!

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

          @jmercier The file will end in .log probably with the names I mentioned below. The files will be text files and not xml.

          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!

          1 Reply Last reply Reply Quote 0
          • J
            Jmercier
            last edited by

            @george1421
            Here you have the folder with Sysprep file

            https://mega.nz/#F!1tEFQZ4Z!5vTLp0tNcCKQxtHoV9Nb7A

            setuperr.log is empty

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

              @jmercier Those files did not contain the answer. You must check both c:\windows\panther as well as the sysprep directory. I only know where to look because I broke windows install before.

              Also if I understand you can upload with fog and deploy to same computer as you captured from. Now you deploy to computer #2. Is that the same computer model as your captured from computer? That also means if you captured from a uefi computer, your target computer must also be uefi. If the same model or not. You can not mix uefi images and bios (legacy mode) computers.

              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!

              1 Reply Last reply Reply Quote 0
              • J
                Jmercier
                last edited by

                @george1421
                ok i will look tomorrow

                Also i can upload but not deploy on the same computer #1 and the second #2 is the same model i will tell you tommorow for c:\windows\panther

                thank you 🙂

                1 Reply Last reply Reply Quote 0
                • J
                  Jmercier
                  last edited by

                  @george1421

                  Hello , i tried one more time this morning and i checked in c:\windows\panther different files , i let you check this :

                  https://mega.nz/#F!o8cgVbyQ!XnYhjbXDbpytySAUEfxHgg

                  i hope you ill tell me good news xD i’m desperate -_-’

                  Thank you

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

                    @jmercier well looking through the log files this stands out

                    You are attempting to redeploy an OEM image which is not now allowed by the Windows EULA, but is technically possible to do. Windows OEM does not have redistributable rights.

                    2018-04-05 09:36:51, Info                         [windeploy.exe] Client OS detected: 1
                    2018-04-05 09:36:51, Info                         [windeploy.exe] OEM Licensing detected: 1
                    2018-04-05 09:36:51, Info                         [windeploy.exe] EnterpriseS or Enterprise or EnterpriseSN or EnterpriseN edition detected: 0
                    2018-04-05 09:36:51, Info                         [windeploy.exe] Client OS edition and OEM license detected and no enterprise edition detected, will not run SetupComplete.cmd
                    2018-04-05 09:36:51, Info                         [windeploy.exe] Not allowed to run the Setupcomplete.cmd, will not run SetupComplete.cmd
                    2018-04-05 09:36:51, Info                         [windeploy.exe] Windeploy: Executing move/cleanup commands
                    2018-04-05 09:36:51, Info                         [windeploy.exe] WinDeploy.exe exiting with code [0x0]
                    

                    It is having a hard time accepting setting the ui language fallback

                    2018-04-06 09:05:20, Error                        [MUIUNATTEND.EXE] Failed to set fr-FR as UILanguageFallback. error:87
                    

                    And here is the error that ends it all

                    2018-04-06 09:06:04, Info                         [oobeldr.exe] Applying data-only settings overrides using SMI...
                    2018-04-06 09:06:04, Info                  CSI    00000001@2018/4/6:07:06:04.264 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ff983694519 @0x7ff983a31f84 @0x7ff983a48a26 @0x7ff983a20751 @0x7ff983a1f50d @0x7ff610d87f08)
                    2018-04-06 09:06:04, Error                 CSI    00000001 (F) 80220005 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=5] #538# from CChildContextStore::ApplyToNamespace(namespace = @0x1d56d576c00)[gle=0x80004005]
                    2018-04-06 09:06:04, Error                        [oobeldr.exe] Failed to apply data-only settings overrides; hr = 0x80220005
                    2018-04-06 09:06:04, Info                         [oobeldr.exe] Flushing registry to disk...
                    2018-04-06 09:06:04, Info                         [oobeldr.exe] Flush took 78 ms.
                    2018-04-06 09:06:04, Error                        [oobeldr.exe] Failed to complete RunSMIPass for oobeSystem.  Error: [0x80220005]
                    2018-04-06 09:06:04, Error                        [oobeldr.exe] There was an error while processing oobeSystem. Error: [0x80220005]
                    

                    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 0
                    • J
                      Jmercier @george1421
                      last edited by Jmercier

                      @george1421 ok then i just need to deny the EULA in the file when i’m syspreping ?
                      or i need to do other things ?

                      I’m using this site for the sysprep file http://windowsafg.no-ip.org/win10x86_x64_uefi.html

                      Wayne WorkmanW 1 Reply Last reply Reply Quote 0
                      • Wayne WorkmanW
                        Wayne Workman @Jmercier
                        last edited by Wayne Workman

                        @jmercier Legally, you should not be using any tool to deploy OEM copies of Windows aside from original installation media.

                        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!
                        Daily Clean Installation Results:
                        https://fogtesting.fogproject.us/
                        FOG Reporting:
                        https://fog-external-reporting-results.fogproject.us/

                        1 Reply Last reply Reply Quote 0
                        • J
                          Jmercier
                          last edited by

                          OK thank you my prblem is solved now i will post another problem now with license key plugins x)

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

                          171

                          Online

                          12.1k

                          Users

                          17.3k

                          Topics

                          155.4k

                          Posts
                          Copyright © 2012-2024 FOG Project