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

    Solved FOG 1.5.0 BitLocker Issue Capturing Win 10 Image.

    FOG Problems
    4
    6
    4670
    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.
    • N
      Nemo_f last edited by

      Hello,

      My configuration is FOG: 1.5.0, with kernel: 4.13.4, hosted on Debian 9.
      I have a Windows 10 machine I can’t capture image from as FOG detects Bitlocker enabled on the partition - No Partitions Passed (is BitlockedPartition)
      Windows 10 version is the latest one, but I believe I was able to image the same version with the previous version of FOG. Is there a way to disable that check? I have no BitLocker enabled on that installation.
      What would be the best way to install an older version of FOG if the problem can’t be resolved in this installation? I initially installed FOG using Git about a week ago.

      1 Reply Last reply Reply Quote 0
      • D
        dylan123 @george1421 last edited by

        So with the ‘manage-bde -off C:’ command, are people then turning that back on once the image is created/deployed? Or given Bitlocker isn’t on, not bothering?

        I suppose it’s made me think I should potentially look at turning bitlocker on for some staff members which will probably just be a manual process, but just wondering if I should then be turning the above command on when I do it.

        1 Reply Last reply Reply Quote 1
        • N
          Nemo_f last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • N
            Nemo_f @george1421 last edited by

            @george1421 Thank you! I have tested and can confirm that this was indeed the issue.
            “manage-bde -off C:” decrypted the drive and now I’m capturing away…

            1 Reply Last reply Reply Quote 0
            • THEMCV
              THEMCV last edited by

              @george1421 Glad to know that I helped some. 🙂

              1 Reply Last reply Reply Quote 4
              • george1421
                george1421 Moderator last edited by

                Here is a similar thread that discusses the same issue and the commands needed to disable it: https://forums.fogproject.org/post/102522

                Review the posts by @THEMCV they are enlightening. This issue does come up quite often. Most specifically this post:

                Try this, I ran into this on Surface’s.

                Open command prompt as admin.

                manage-bde -off 😄

                manage-bde -status 😄

                Fingers crossed that it will fix it. In my case, Windows was by default encrypting the free space which caused issues.

                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!

                N D 2 Replies Last reply Reply Quote 4
                • 1 / 1
                • First post
                  Last post

                181
                Online

                10.4k
                Users

                16.4k
                Topics

                150.5k
                Posts

                Copyright © 2012-2023 FOG Project