Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Boot error in Win To Go installation with system encryption #1369

Open
mkazl opened this issue Jun 25, 2024 · 0 comments
Open

Boot error in Win To Go installation with system encryption #1369

mkazl opened this issue Jun 25, 2024 · 0 comments
Labels

Comments

@mkazl
Copy link

mkazl commented Jun 25, 2024

Error when trying to boot the system partition from Windows 11.

Expected behavior

The system boots successfully.

Observed behavior

Error "BlinitializeLibrary failed 0xc00000bb"

Steps to reproduce

  1. Install latest version Windows 11 Enterprise (Windows 11 build 22631) on external Sandisk SDSSDE81-4T00-G25 (4TB) in Windows To Go mode from Rufus 4.5
  2. Install latest version VeraCrypt (1.26.7)
  3. Start System Encryption (Normal -> Encrypt the Windows system partition -> Single-boot)
  4. Start System Encryption Pretest
  5. I get a boot error when entering the correct password.

Screenshots

image

Your Environment

VeraCrypt version: 1.26.7

Operating system and version: Windows 11 build 22631

System type: 64-bit

Additional Info

  1. I received this error on 5 different computers out of 7 tested (for example, Intel i7-12700K + Asus Prime H610M-K D4 or Ryzen 7 5700G + MSI B450 Tomahawk). The boot was successful only on the laptop Xiaomi Mi Notebook Pro JYU4057CN and virtual machine VMWare Workstation 17.5.2.
  2. My other external SSD (Samsung T5 1 TB, Kingston XS2000 2 TB) with system encryption (configured in the same way as steps above describe) works correctly on all tested system configuration
  3. I tried turning secure boot on and off, but it had no effect on the error.

If you need any additional information or tests from my side, please feel free to contact me.

@mkazl mkazl added the bug label Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant