Mine is going to be laid back if all goes according to plan. I’m going to do some birding with a friend tomorrow morning, then I’m headed to a used bookstore to buy a copy of “the pricess bride” that I talked myself out of the other day (I’ve never read it). Then I’m hitting the farmers market and then relaxing at home for the foreseeable future. Enjoy your weekend!

  • russjr08@outpost.zeuslink.net
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    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:

    Cause: This problem occurs because the boot firmware on the computer generates lots of memory fragmentation.

    Workaround: We recommend that you do not let boot firmware create large amounts of fragmentation. Large memory fragmentation degrades the overall startup performance and causes problems.

    Ah that’s real helpful Microsoft, thank you!

    • PerogiBoi@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      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.