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

    Windows 10, PXE, black screen, and a beep

    Scheduled Pinned Locked Moved Solved
    Windows Problems
    2
    4
    2.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.
    • apathetic_adminA
      apathetic_admin
      last edited by

      We are hoping to trial Windows 10 to our users soon. We have Dell Latitude E6540s that we are pushing our Windows 10 Enterprise image to. Secure boot is disabled, and it’s set to legacy boot (as opposed to UEFI). Once FOG deploys the image, the laptop reboots. Then it network boots, loads the FOG menu, and then exits to boot to the hard drive. At this point the screen stays black, and then laptop beeps once. If I disable network boot, or I disconnect the ethernet cable, the laptop boots as expected and Windows 10 completes installation as I would expect. I tried the kernel named “Kernel - 4.4.2 TomElliott” from 2/23/16 in hopes that a newer kernel would resolve the issue but it did not. These laptops do successfully work with Windows 7, so I’m theorizing that this is an issue between the Windows 10 boot loader and the way that the FOG menu/kernel is handing off to it. I’ve seen a couple other posts here and there regarding similar issues but have found no resolution.

      Anybody have any suggestions?

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

        Change the “Host Bios Exit Type” for all of the Latitude E6540s that you have (put them in a group and use the group to change it).

        You’ll probably need to use GRUB, just a guess. Try different ones till you find one that works.

        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/

        apathetic_adminA 1 Reply Last reply Reply Quote 0
        • apathetic_adminA
          apathetic_admin @Wayne Workman
          last edited by

          @Wayne-Workman …It was really just that easy. I am so good at computers…

          Thanks

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

            @apathetic_admin Don’t beat yourself up over something you didn’t know. What’s important is you asked for help where you needed it - instead of just giving up or being too proud to ask for help.

            Part of being good in I.T. / comp-sci is knowing where to get answers.

            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 1
            • 1 / 1
            • First post
              Last post

            213

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project