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

Windows 10 changed the boot order !!

Scheduled Pinned Locked Moved
Windows Problems
4
12
1.5k
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.
  • T
    Tanguy
    last edited by Mar 12, 2021, 4:57 PM

    Hello everyone !

    I searched in the forum but I don’t find a solution… Well, after the deployement, Windows 10 changed the boot order (UEFI) to put windows manager at the top.
    How can I prevent this ?

    Thanks !

    G 1 Reply Last reply Mar 13, 2021, 2:20 PM Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Mar 13, 2021, 1:43 PM

      @Tanguy FOG does not touch the UEFI boot entries at all. The change in boot order is probably happening due to the UEFI firmware applying some logic to recognize new installs or just any bootloader file it finds on an EFI boot partition.

      Check your mainboard/firmware manual to see if you can disable that “auto feature”.

      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 0
      • G
        george1421 Moderator @Tanguy
        last edited by Mar 13, 2021, 2:20 PM

        @tanguy said in Windows 10 changed the boot order !!:

        Windows 10 changed the boot order (UEFI) to put windows manager at the top.

        As they say, this is a feature not a bug. Windows 10 will change the boot order because it thinks it knows best. For bios based computer it wasn’t possible to do, but for uefi computers, during winsetup/oobe windows 10 will reset the boot order so that windows boot image will always start. You will need to reset the boot order from within windows after oobe finishes.

        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!

        T 1 Reply Last reply Mar 15, 2021, 8:11 AM Reply Quote 0
        • T
          Tanguy @george1421
          last edited by Mar 15, 2021, 8:11 AM

          @george1421 Thanks for your reply ! I work in a school with a lot of computers, and change the boot order for each is time consuming !
          If I can’t prevent this, maybe I can automate after deploying with a script ?

          F 1 Reply Last reply Mar 15, 2021, 8:23 AM Reply Quote 0
          • F
            Florent @Tanguy
            last edited by Mar 15, 2021, 8:23 AM

            @tanguy If it’s Dell manufacturer you can use CCTK config tool to modify boot order

            Florent
            Bretagne, FRANCE

            T 1 Reply Last reply Mar 15, 2021, 9:41 AM Reply Quote 0
            • T
              Tanguy @Florent
              last edited by Mar 15, 2021, 9:41 AM

              @florent Bonjour Florent ! Merci pour votre réponse. Il se trouve que nous n’avons pas que des DELL, et que le CCTK ne fonctionne pas sur tous les DELL ( nous avons aussi des Vostro). J’ai essayé un snapin powerShell mais celui-ci ne semble pas fonctionner non plus. Au vu du nombre de postes, passer sur chacun pour remettre à la main l’ordre de boot ne m’emballe pas beaucoup !
              Il y a-t-il une procédure particulière pour que mon snapin s’execute ?

              Merci d’avance !

              F 1 Reply Last reply Mar 15, 2021, 9:44 AM Reply Quote 0
              • F
                Florent @Tanguy
                last edited by Florent Mar 15, 2021, 3:45 AM Mar 15, 2021, 9:44 AM

                @tanguy Ah oui compliqué alors.
                Chez nous une solution de contournement que nous avons trouvé est de positionner le wakeonlan sur “boot on pxe” mais ça revient au meme il faut une methode pour le propager sur vos divers modèles de plusieurs marques.
                Pour les snapins il faut juste avoir un agent FOG installé sur les PC concernés, et que sur les Host dans FOG snapins soit coché

                Florent
                Bretagne, FRANCE

                T 2 Replies Last reply Mar 15, 2021, 10:26 AM Reply Quote 0
                • T
                  Tanguy @Florent
                  last edited by Mar 15, 2021, 10:26 AM

                  @florent Merci beaucoup, je vais creuser du côté du snapin. Comme je débute sur FOG, je tâtonne un peu…
                  Bonne journée

                  1 Reply Last reply Reply Quote 0
                  • T
                    Tanguy @Florent
                    last edited by Mar 19, 2021, 11:00 AM

                    @florent Bonjour,

                    J’ai enfin réussi à changer l’ordre de boot en passant par bcdedit dans le SetupComplete. Cela me semble une méthode de “bourrin” mais après quelques test, cela à l’air de fonctionner.
                    Merci encore pour votre aide et bonne journée

                    F 1 Reply Last reply Mar 19, 2021, 11:12 AM Reply Quote 0
                    • F
                      Florent @Tanguy
                      last edited by Mar 19, 2021, 11:12 AM

                      @tanguy Salut, Peux tu partager le code utilisé ?

                      Florent
                      Bretagne, FRANCE

                      T 1 Reply Last reply Mar 19, 2021, 1:23 PM Reply Quote 0
                      • T
                        Tanguy @Florent
                        last edited by Mar 19, 2021, 1:23 PM

                        @florent Bien sûr !
                        Voici le code du reseal.cmd

                        @echo off
                        set curdir=%~dp0
                        %~d0
                        cd %curdir%
                        set unattendfile=unattend.xml
                        if NOT %1!==! set unattendfile=%1
                        
                        echo sysprep with %unattendfile%
                        echo pres Ctrl+C to cancel, or any key to continue
                        pause
                        
                        :: Step #12
                        rem mkdir %windir%\Setup\Scripts
                        rem echo del /Q /F %windir%\system32\sysprep\unattend.xml > %windir%\Setup\Scripts\SetupComplete.cmd
                        rem echo del /Q /F %windir%\panther\unattend.xml >> %windir%\Setup\Scripts\SetupComplete.cmd
                        
                        :: Step #13
                        sc stop "FOGservice"
                        sc config "FOGService" start= disabled
                        
                        
                        echo on
                        copy "%unattendfile%" %windir%\system32\sysprep\unattend.xml
                        cd %windir%\system32\sysprep
                        %systemdrive%
                        
                        sysprep /generalize /oobe /quit /unattend:unattend.xml
                        

                        J’ai mis en commentaires tout le “Step #12” au cas où…

                        Et j’ai mis dans C:\Windows\Setup\Scripts le script "SetupComplete.cmd suivant :

                        powercfg -h off
                        sc config FOGService start= auto
                        sc start "FOGservice"
                        
                        
                        
                        
                        del /Q /F c:\windows\system32\sysprep\unattend.xml
                        del /Q /F c:\windows\panther\unattend.xml
                        
                        
                        bcdedit /set {fwbootmgr} displayorder {bootmgr} /addlast
                        
                        shutdown -r -t 0
                        
                        

                        Parfois le reseal.com lancé en tant qu’admin bloque, alors le lance un script powershell en tant qu’admin suivant :

                        # List of Applications to Remove
                        $AppPackages  = @()
                        $AppPackages += 'microsoft.windowscommunicationsapps'
                        $AppPackages += 'Microsoft.BingWeather'
                        $AppPackages += 'Microsoft.DesktopAppInstaller'
                        $AppPackages += 'Microsoft.Getstarted'
                        $AppPackages += 'Microsoft.Windows.Photos'
                        $AppPackages += 'Microsoft.WindowsCamera'
                        $AppPackages += 'Microsoft.WindowsFeedbackHub'
                        $AppPackages += 'Microsoft.WindowsStore'
                        $AppPackages += 'Microsoft.XboxApp'
                        $AppPackages += 'Microsoft.XboxIdentityProvider'
                        $AppPackages += 'Microsoft.ZuneMusic'
                        $AppPackages += 'Microsoft.StorePurchaseApp'
                        $AppPackages += 'Microsoft.XboxOneSmartGlass'
                        $AppPackages += 'Microsoft.GetHelp'
                        $AppPackages += 'Microsoft.Microsoft3DViewer'
                        $AppPackages += 'Microsoft.MicrosoftOfficeHub'
                        $AppPackages += 'Microsoft.LanguageExperiencePackfr-fr'
                        $AppPackages += 'Microsoft.ZuneVideo'
                        
                        foreach ($App In $AppPackages) {
                            Write-Host "Removing Package : $App"
                        	
                            $Package = Get-AppxPackage | Where-Object {$_.Name -eq $App}
                            If ($Package -ne $null) {Remove-AppxPackage -Package $Package.PackageFullName -ErrorAction SilentlyContinue}
                        
                            $Package = Get-AppxPackage -Allusers| Where-Object {$_.Name -eq $App}
                            If ($Package -ne $null) {Remove-AppxPackage -Package $Package.PackageFullName -ErrorAction SilentlyContinue}
                        	
                            $ProvisionedPackage = Get-AppxProvisionedPackage -Online | Where-Object {$_.DisplayName -eq $App}
                            If ($ProvisionedPackage -ne $null) {Remove-AppxProvisionedPackage -Online -PackageName $ProvisionedPackage.PackageName -ErrorAction SilentlyContinue}
                        
                        }
                        

                        Je n’ai pas poussé loin les tests, mais cela à l’air de fonctionner. N’hésite pas si tu as des questions !

                        1 Reply Last reply Reply Quote 0
                        • F
                          Florent
                          last edited by Mar 22, 2021, 9:09 AM

                          Merci je testerais cela un de ces jours.

                          Florent
                          Bretagne, FRANCE

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

                          229

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project