Windows 11 Decided to Nuke it's own Registry., Back to Win 10 I Guess..

in life •  12 days ago


    image.png

    After fighting with my workstation for over a day after somehow destroying the windows 11 registry (by installing more RAM sticks, somehow) finally gave up and installed windows 10 from a boot USB I had to make. Never in all my time using M$ windblows have I ever seen a simple hardware addition cause a persistent BSOD on startup... 0x000000021c code (maybe too many zeroes) kept hitting after POST and no matter what chkdsk or startup repair or anything else attempted allowed a proper boot.

    Thankfully it looks like loss of files and projects was minimal.. Biggest pain in the ass honestly has been having none of my drives indexed for searching.. Last thing I needed was to have to rebuild my whole ass workstation and build environment.. but alas..

    Still have a few important things to find and recover.. might try and make an image of this windows installation after my build environment is rebuilt incase this shit happens again.

    reading online it seems the most cited reason for this is accidently turning off the machine during a registry update.. but no such thing occurred for me.. I was running the nightly build of windows 11 pro.. it is a legit copy.. A fucking piss off to say the least..


    VOTE @KLYE FOR WITNESS!

    Every Single Vote Helps, Thanks for the Support!

    Need to get in Contact with KLYE?
    Join the Official #KLYE Discord Server Today!


    Looking for an Affordable, Secure & Reliable Server Host for Your Witness Server or Other Web Related Projects? Check out Privex.io!
      Authors get paid when people like you upvote their post.
      If you enjoyed what you read here, create your account today and start earning FREE VOILK!