86
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Jun 2023
86 points (100.0% liked)
Chat
7498 readers
10 users here now
Relaxed section for discussion and debate that doesn't fit anywhere else. Whether it's advice, how your week is going, a link that's at the back of your mind, or something like that, it can likely go here.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
Happy to get any input from anyone on this so I do appreciate the offer :)
I have 2 nvme drives that are completely empty and have been formatted and drive partitions deleted several times.
Every time I install windows from a usb key, the installation goes without a hitch up until the installation restart. Then, my motherboard gives me the error: B1InitializeLibrary failed 0xc00000bb.
All the advice online that I can find involves trying to repair the installation using bootrec.exe and fixing mbr and rebuilding bcd. I get weird errors that differ every time when I do this.
The most painful part of this all is that the very first time I installed windows, it all worked perfectly. I fucked it all up when I decided to install Fedora Linux on the second drive. It messed up booting and everything since.
I can install Fedora Linux on any of these two nvme drives and boot to them perfectly without any issues which means this is not a hardware issue. Blaaaahhh. I just wanna use my new Index 😭
That is certainly strange! I can't seem to find much online about the issue, though I saw a couple of recommendations about disabling Secure Boot. I'm not sure why that would make a difference (especially given Microsoft's involvement with OEMs and Secure Boot...) and it probably wouldn't be the best thing to keep turned off permanently (or rather, as a "disclaimer": if you haven't already, do a bit of light researching on secure boot and why it exists) but it wouldn't hurt to try turning it off temporarily (if its not already off) to see if that gets past the error.
I did get a chuckle out of this bit from Microsoft's docs on the error:
Ah that's real helpful Microsoft, thank you!
Ya that was one of the things I’ve tried. I’m going to try disconnecting all my hard drives except for the one I want windows on and buy a brand new usb stick and hope for the best.