this post was submitted on 24 Jun 2023
83 points (100.0% liked)
Chat
7499 readers
21 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.