"Something Happened" What Next?

Page 5 of 5 FirstFirst ... 345

  1. Posts : 7,871
    Windows 11 Pro 64 bit
    Thread Starter
       #41

    I can only quote from the other thread I referenced that repair of the boot configuration enabled Windows 10 to install ......

    For what it's worth - in case someone finds this thread: I finally managed to upgrade my box to Win10! As turned out the \Boot\BCD file on the boot manager partition of my system must have been corrupted, even though my system had always booted OK and even though issuing a "bcdedit" command on the recovery console had only shown valid entries.
    I only realized that nevertheless something must be fishy with that file, when I tried to do a "bcdedit /export <file>" and always got an error message "invalid handle". A tool to visually edit BCD files that I then tried to inspect the file always crashed when opening that file - another indication that something was wrong with that file. So I finally renamed the file and recreated a new BCD file (using "bootrec /RebuildBCD"). That file allowed to be exported and inspected.
    So, after fixing that I gave the Win10 install another try and - fair enough - it worked immediately.

    If only had the upgrade procedure emitted the faintest hint in that direction this would have spared me at least 15hrs of search and experimentation! The guy who dared to write this idiotic error message "something happened" should get fired, if not worse! A big MINUS 10 for this worst Windows update experience ever
      My Computers


  2. Posts : 7,871
    Windows 11 Pro 64 bit
    Thread Starter
       #42

    Thanks to all for your help.

    I've now solved this problem and have a fully working Windows 10 laptop! The problem was as I suspected - a corrupted EFI system partition. I've created a new thread showing the solution at https://www.tenforums.com/installatio...x80004005.html
      My Computers


  3. Posts : 16,325
    W10Prox64
       #43

    Steve C said:
    Thanks to all for your help.

    I've now solved this problem and have a fully working Windows 10 laptop! The problem was as I suspected - a corrupted EFI system partition. I've created a new thread showing the solution at https://www.tenforums.com/installatio...x80004005.html
    Excellent! Thanks for posting that for others as well!
    One question: should there be a space before "enable":
    had to run regaentc / enable to enable it
    So glad you got things sorted!
      My Computer


  4. Posts : 7,871
    Windows 11 Pro 64 bit
    Thread Starter
       #44

    Yes it's reagentc /enable
      My Computers


  5. Posts : 16,325
    W10Prox64
       #45

    Steve C said:
    Yes it's reagentc /enable
    Okay, might want to fix that in your post - right now it has a space before and after the "/".
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:38.
Find Us




Windows 10 Forums