XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Cannot Install Windows 10 in New VM

    Scheduled Pinned Locked Moved Compute
    31 Posts 6 Posters 1.4k Views 4 Watching
    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.
    • D Offline
      dinhngtu Vates 🪐 XCP-ng Team @mickwilli
      last edited by

      @mickwilli What host hardware do you have and which ISO did you use for the Windows installation? I assume you used the default Windows 10 template?

      M 1 Reply Last reply Reply Quote 0
      • M Offline
        mickwilli @dinhngtu
        last edited by

        @dinhngtu the host is a Dell Precision T3610 workstation with Intel Xeon processor and 120GB RAM. I used the default Windows 10 (64bit) template. The ISO was built with the Microsoft Windows 10 media creator about a month ago and it successfully installed a VirtualBox VM. The ISO is located on a NFS SR.

        1 Reply Last reply Reply Quote 0
        • A Offline
          acebmxer
          last edited by

          is the vm set to bios, uefi? is secure boot enabled in the vm?

          M 1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            Also what Xeon model exactly?

            M 1 Reply Last reply Reply Quote 0
            • M Offline
              mickwilli @acebmxer
              last edited by

              @acebmxer it is UEFI, and I’ve tried with and without secure boot enabled.

              1 Reply Last reply Reply Quote 0
              • M Offline
                mickwilli @olivierlambert
                last edited by

                @olivierlambert it is a “ Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz”

                1 Reply Last reply Reply Quote 0
                • D Offline
                  dinhngtu Vates 🪐 XCP-ng Team
                  last edited by

                  Could you provide a crash dump?

                  M 1 Reply Last reply Reply Quote 0
                  • M Offline
                    mickwilli @dinhngtu
                    last edited by

                    @dinhngtu given it’s trying to boot from the installer, where would it save the crash dump to?

                    D 2 Replies Last reply Reply Quote 0
                    • D Offline
                      dinhngtu Vates 🪐 XCP-ng Team @mickwilli
                      last edited by

                      @mickwilli Forget that, I just realized E5-2660 v2 is way too old for Windows 10. See the supported processors.

                      A 1 Reply Last reply Reply Quote 0
                      • A Offline
                        Andrew Top contributor @dinhngtu
                        last edited by

                        @dinhngtu Win10 on XCP 8.3 with E5-2600v2 works just fine for me...

                        D 1 Reply Last reply Reply Quote 0
                        • D Offline
                          dinhngtu Vates 🪐 XCP-ng Team @Andrew
                          last edited by dinhngtu

                          @Andrew Still, having an unsupported CPU makes it somewhat difficult to troubleshoot the issue, especially when it's a recent ISO. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED is sometimes associated with execution of unsupported instructions (though I don't know if that's the case here). For instance, there's a poke-of-death on some newer Intel CPUs related to the Architectural LBR feature (https://docs.xcp-ng.org/troubleshooting/windows-pv-tools/#windows-bug-check-0x3b-system_service_exception-on-systems-with-newer-intel-cpus).

                          1 Reply Last reply Reply Quote 0
                          • D Offline
                            dinhngtu Vates 🪐 XCP-ng Team @mickwilli
                            last edited by

                            @mickwilli Do you know how to create custom Windows PE ISOs? It might be possible to put the boot kernel in the ISO into debugging mode, then using the Connecting to guests using serial console guide to collect a crash analysis.

                            M 1 Reply Last reply Reply Quote 0
                            • M Offline
                              mickwilli @dinhngtu
                              last edited by

                              @dinhngtu sorry, I don't know how to do that offhand. If you point me in the direction of some instructions, I'm happy to give it a go.

                              D 1 Reply Last reply Reply Quote 0
                              • D Offline
                                dinhngtu Vates 🪐 XCP-ng Team @mickwilli
                                last edited by dinhngtu

                                @mickwilli You can extract the ISO, run the following command:

                                bcdedit /store <extracted ISO path>\Boot\BCD /set {default} debug on
                                bcdedit /store <extracted ISO path>\Boot\BCD /dbgsettings serial debugport:1 baudrate:115200
                                

                                Then repack the ISO.

                                You can also create a new ISO using this guide: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-create-usb-bootable-drive then run the two commands above on media\Boot\BCD before you run MakeWinPEMedia.

                                M 2 Replies Last reply Reply Quote 0
                                • M Offline
                                  mickwilli @dinhngtu
                                  last edited by

                                  @dinhngtu Thanks. I'll try and give that a go in the next few days and will report back.

                                  Note that I have Windows 10 1803 installed without any issues. Trying to update to 22H2 fails with the same blue screen error as you'd expect. Sadly, no crash dump as it seems to fail very early in the boot process.

                                  TeddyAstieT 1 Reply Last reply Reply Quote 0
                                  • TeddyAstieT Offline
                                    TeddyAstie Vates 🪐 XCP-ng Team Xen Guru @mickwilli
                                    last edited by

                                    @mickwilli said in Cannot Install Windows 10 in New VM:

                                    @dinhngtu Thanks. I'll try and give that a go in the next few days and will report back.

                                    Note that I have Windows 10 1803 installed without any issues. Trying to update to 22H2 fails with the same blue screen error as you'd expect. Sadly, no crash dump as it seems to fail very early in the boot process.

                                    Do you get any additional BSOD details in xl dmesg ?

                                    M 1 Reply Last reply Reply Quote 0
                                    • M Offline
                                      mickwilli @TeddyAstie
                                      last edited by

                                      @TeddyAstie apologies for the tardy reply.

                                      This is the tail end of note from xl dmesg:

                                      (XEN) [1029242.324130] d17v1 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80272497e14 0xffff9f8d4689e7c8 0xffff9f8d4689e000
                                      (XEN) [1029490.963515] d18v1 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80251497e14 0xffffac025109e7c8 0xffffac025109e000
                                      (XEN) [1029557.664243] d19v1 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff8073c497e14 0xfffff4895049e7c8 0xfffff4895049e000
                                      (XEN) [1029654.360658] d20v1 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80030497e14 0xffff848fdee9e7c8 0xffff848fdee9e000
                                      (XEN) [1029786.928461] d21v0 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80639697e14 0xfffff50ea42897c8 0xfffff50ea4289000
                                      (XEN) [1030181.784003] d23v0 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80749297e14 0xfffffb0fe66897c8 0xfffffb0fe6689000
                                      (XEN) [1030346.926513] d24v0 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80337c97e14 0xffff8304baa897c8 0xffff8304baa89000
                                      (XEN) [1030399.047734] d25v0 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80542c97e14 0xfffff204226897c8 0xfffff20422689000
                                      (XEN) [1529444.878620] d13v1 VIRIDIAN GUEST_CRASH: 0x7a 0x117a30 0xc00000c0 0x2c9f6be0 0x22f46000
                                      (XEN) [1529695.616425] d30v1 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80355497e14 0xffff8387fbcb37c8 0xffff8387fbcb3000
                                      (XEN) [1546475.266724] d49v0 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff80649896f0a 0xffffba8689a897c8 0xffffba8689a89000
                                      (XEN) [2060275.879001] d54v0 VIRIDIAN GUEST_CRASH: 0x7e 0xffffffffc0000094 0xfffff8027a497e14 0xfffff302fea897c8 0xfffff302fea89000
                                      

                                      The last line appears to be from my most recent test with a fresh VM (just to check those messages were related).

                                      1 Reply Last reply Reply Quote 0
                                      • M Offline
                                        mickwilli @dinhngtu
                                        last edited by

                                        @dinhngtu I've just been trying to make those edits to the bcd file, however, I'm not having any luck. Below is a section of things I have tried with no success (using the latest Windows 10 22H2):

                                        Microsoft Windows [Version 10.0.19045.6332]
                                        (c) Microsoft Corporation. All rights reserved.
                                        
                                        C:\WINDOWS\system32>bcdedit /store "C:\Windows 10 22H2\boot\BCD" /set debug on
                                        An error occurred while attempting to reference the specified entry.
                                        The system cannot find the file specified.
                                        
                                        C:\WINDOWS\system32>bcdedit /store "C:\Windows 10 22H2\boot\BCD" /debug on
                                        An error occurred while attempting to access the specified entry.
                                        The system cannot find the file specified.
                                        
                                        D 1 Reply Last reply Reply Quote 0
                                        • D Offline
                                          dinhngtu Vates 🪐 XCP-ng Team @mickwilli
                                          last edited by dinhngtu

                                          @mickwilli Does the BCD file exist at the specified path? What do you see when running bcdedit /store (BCD path) /enum all?

                                          edit: The first command has an issue, try doing this instead:

                                          bcdedit /store <extracted ISO path>\Boot\BCD /set {default} debug on
                                          

                                          Repeat for EFI\Microsoft\Boot\BCD (the dbgsettings command as well)

                                          Sent you a PM in case you're still having issues.

                                          M 2 Replies Last reply Reply Quote 0
                                          • M Offline
                                            mickwilli @dinhngtu
                                            last edited by

                                            @dinhngtu thanks for that info and for the PM.

                                            I managed to successfully update the bcd, however after rebuilding the ISO, I cannot get the VM to boot from it, I just end up in the EFI shell. I was following these instructions: https://www.wintips.org/how-to-edit-iso-file-modify-windows-iso-bootable-image/ The only deviation I had to make was to manually set the file system to UDF, since the prompt shown in the instructions did not come up.

                                            I used the WinPE ISO that you provided, which did boot, however I didn't have a lot of joy getting any much information out of it. I managed to get WinDbg to connect and show the status, however the VM ultimately just hung on the following screen:
                                            Screenshot 2025-10-12 at 1.22.46 PM.png

                                            Note that either WinDbg was either showing that the Debugee was busy/running or disconnected. It wasn't waiting for me to click go at any point.

                                            This is what was shown in the WinDbg command window:

                                            
                                            ************* Preparing the environment for Debugger Extensions Gallery repositories **************
                                               ExtensionRepository : Implicit
                                               UseExperimentalFeatureForNugetShare : true
                                               AllowNugetExeUpdate : true
                                               NonInteractiveNuget : true
                                               AllowNugetMSCredentialProviderInstall : true
                                               AllowParallelInitializationOfLocalRepositories : true
                                               EnableRedirectToChakraJsProvider : false
                                            
                                               -- Configuring repositories
                                                  ----> Repository : LocalInstalled, Enabled: true
                                                  ----> Repository : UserExtensions, Enabled: true
                                            
                                            >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
                                            
                                            ************* Waiting for Debugger Extensions Gallery to Initialize **************
                                            
                                            >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.062 seconds
                                               ----> Repository : UserExtensions, Enabled: true, Packages count: 0
                                               ----> Repository : LocalInstalled, Enabled: true, Packages count: 45
                                            
                                            Microsoft (R) Windows Debugger Version 10.0.27920.1001 AMD64
                                            Copyright (c) Microsoft Corporation. All rights reserved.
                                            
                                            Opened 192.168.205.10
                                            Waiting to reconnect...
                                            BD: Boot Debugger Initialized
                                            Connected to Windows Boot Debugger 26100 x64 target at (Sun Oct 12 12:39:23.766 2025 (UTC + 13:00)), ptr64 TRUE
                                            Kernel Debugger connection established.
                                            Symbol search path is: srv*
                                            Executable search path is: 
                                            ReadVirtual() failed in GetXStateConfiguration() first read attempt (error == 0.)
                                            Windows Boot Debugger Kernel Version 26100 UP Free x64
                                            Primary image base = 0x00000000`016d0000 Loaded module list = 0x00000000`019499e8
                                            System Uptime: not available
                                            Shutdown occurred at (Sun Oct 12 12:41:48.383 2025 (UTC + 13:00))...unloading all symbol tables.
                                            Waiting to reconnect...
                                            BD: Boot Debugger Initialized
                                            Connected to Windows Boot Debugger 19041 x64 target at (Sun Oct 12 12:41:49.330 2025 (UTC + 13:00)), ptr64 TRUE
                                            Kernel Debugger connection established.
                                            
                                            ************* Path validation summary **************
                                            Response                         Time (ms)     Location
                                            Deferred                                       srv*
                                            Symbol search path is: srv*
                                            Executable search path is: 
                                            ReadVirtual() failed in GetXStateConfiguration() first read attempt (error == 0.)
                                            Windows Boot Debugger Kernel Version 19041 UP Free x64
                                            Primary image base = 0x00000000`01300000 Loaded module list = 0x00000000`014afa98
                                            System Uptime: not available
                                            Shutdown occurred at (Sun Oct 12 12:42:15.478 2025 (UTC + 13:00))...unloading all symbol tables.
                                            Waiting to reconnect...
                                            BD: Boot Debugger Initialized
                                            Connected to Windows Boot Debugger 19041 x64 target at (Sun Oct 12 12:42:16.760 2025 (UTC + 13:00)), ptr64 TRUE
                                            Kernel Debugger connection established.
                                            
                                            ************* Path validation summary **************
                                            Response                         Time (ms)     Location
                                            Deferred                                       srv*
                                            Symbol search path is: srv*
                                            Executable search path is: 
                                            Windows Boot Debugger Kernel Version 19041 UP Free x64
                                            Primary image base = 0x00000000`01300000 Loaded module list = 0x00000000`014afa98
                                            System Uptime: not available
                                            Shutdown occurred at (Sun Oct 12 12:42:22.714 2025 (UTC + 13:00))...unloading all symbol tables.
                                            Waiting to reconnect...
                                            Connected to Windows 10 19041 x64 target at (Sun Oct 12 12:42:24.039 2025 (UTC + 13:00)), ptr64 TRUE
                                            Kernel Debugger connection established.
                                            
                                            ************* Path validation summary **************
                                            Response                         Time (ms)     Location
                                            Deferred                                       srv*
                                            Symbol search path is: srv*
                                            Executable search path is: 
                                            Windows 10 Kernel Version 19041 MP (1 procs) Free x64
                                            Edition build lab: 19041.3636.amd64fre.vb_release_svc_prod3.231019-1741
                                            Kernel base = 0xfffff803`51e00000 PsLoadedModuleList = 0xfffff803`52a2a930
                                            System Uptime: not available
                                            ... Retry sending the same data packet for 64 times.
                                            The transport connection between host kernel debugger and target Windows seems lost.
                                            please try resync with target, recycle the host debugger, or reboot the target Windows.
                                            ... Retry sending the same data packet for 128 times.
                                            ... Retry sending the same data packet for 192 times.
                                            
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post