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

    Windows Server 2019 VM Boot Issues After Installing KB5039217 on XCP-NG 8.2

    Scheduled Pinned Locked Moved Unsolved Compute
    6 Posts 3 Posters 2.2k 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.
    • C Offline
      carp2027
      last edited by

      Hi everyone,

      Posting for the first time and my apologies If I have posted in the wrong place or any other issues with my post.

      I wanted to share a significant issue we encountered with our Windows Server 2019 VMs running on XCP-NG 8.2 related to the installation of the KB5039217 update.

      After installing the KB5039217 update on our Windows Server 2019 VMs, we encountered a boot issue. Upon restarting the VM, it failed to boot completely. We would see the TianoCore screen, but after about 20 seconds of the OS loading, the VM would shut down without displaying any information or error messages on the screen.

      Error Messages:
      The Windows logs showed the following critical errors:

      • The driver \Driver\stcmnt failed to load for the device ROOT\STCMNT\0000.
      • DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server.

      Troubleshooting Steps Taken:
      Ran XCP-NG Tools: We ran the XCP-NG tools, but this did not resolve the issue. We took a snapshot before running this as a precaution and rolled back when it didn't help.
      Multiple Restart Attempts: We attempted multiple restarts without success.
      Windows Recovery Menu: Eventually, the Windows recovery menu appeared after several restart attempts. From there, we booted into safe mode.
      Uninstalled KB5039217: In safe mode, we uninstalled the KB5039217 update, which resolved the issue and allowed the VM to boot successfully.

      Has anyone else experienced similar issues with Windows Server 2019 VMs on XCP-NG 8.2 after installing the KB5039217 update? Any suggestions, guidance or known long-term solutions would be greatly appreciated.

      Thank you and again if this is in the wrong subsection or the wrong format - your feedback is greatly appreciated.
      regards
      carp2027

      K 1 Reply Last reply Reply Quote 0
      • K Offline
        KPS Top contributor @carp2027
        last edited by

        @carp2027
        Could be related:

        https://www.reddit.com/r/xcpng/s/5FESVUNZDw

        K 1 Reply Last reply Reply Quote 0
        • K Offline
          KPS Top contributor @KPS
          last edited by

          You could try to convert UEFI to BIOS:
          https://infra.engineer/windows/68-windows-server-convert-uefi-to-bios-without-data-loss-for-free

          Did you test windows 2022 VMs?

          C 1 Reply Last reply Reply Quote 0
          • C Offline
            carp2027 @KPS
            last edited by

            Thanks heaps, @KPS

            No this is only 2019 VMs only.

            I will try converting to BIOS boot keep you posted.

            Cheers

            K 1 Reply Last reply Reply Quote 0
            • K Offline
              KPS Top contributor @carp2027
              last edited by KPS

              @carp2027
              FYI, I did just install KB5039227 on Windows 2022 with UEFI (no secure boot), Citrix Tools 9.3.2, XCP-ng 8.2.1
              --> No Issues

              I did test with and without "Manage Citrix PV drivers via Windows Update"

              The reddit-thread is now also containing a report about Windows 10.

              4 1 Reply Last reply Reply Quote 1
              • 4 Offline
                456Q @KPS
                last edited by

                @KPS I also patched Windows 2016 und 2022 to latest version. With xen guest tools. Both worked fine as well. We dont have a 2019 machine to test with.

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