Cloudbook 11 Windows Issue

13567

Answers

  • JackE
    JackE ACE Posts: 45,176 Trailblazer
    OK, I have to step away for awhile so I'm gonna assume it's still a FAT32 file system. So go back into diskpart and re-enter the following diskpart commands---
    list vol
    sel vol1
    assign letter=e:
    list vol
    exit (if all the volumes now have a letter c: , e: & d: and everything else went OK)

    Then at the command prompt enter the following command---
    cd /d e:\EFI\Windows\Boot\ (if command doesn't work then try dropping the /d and enter cd e:\EFI\Windows\Boot\ )
    bootrec /FixBoot
    ren BCD BCD.old
    bcdboot c:\Windows /l en-us /s e: All

    Then try coldbooting again.

    Jack E/NJ

    Jack E/NJ

  • Skier76
    Skier76 Member Posts: 67

    Tinkerer

    Many thanks Jack! I'm getting stuck here: "cd /d e:\EFI\Windows\Boot\ (if command doesn't work then try dropping the /d and enter cd e:\EFI\Windows\Boot\ )"

    "The system cannot find the path specified."

    No rush on this. Appreciate the help. 
  • JackE
    JackE ACE Posts: 45,176 Trailblazer
    edited January 2018
    Check diskpart "list vol" again. For some reason the assigned letter e: is not taking. Perhaps we first need to select disk 0, so try ---

    sel disk 0
    list vol
    sel vol 1 (make sure this is the ESP FAT32 volume)
    assign letter=e:
    list vol
    exit

    Then re-enter diskpart, "sel disk 0" "list vol" to make sure the e letter stuck. Then exit and try the bootrec and bcd routine again at the command prompt.

    Jack E/NJ

    Jack E/NJ

  • Skier76
    Skier76 Member Posts: 67

    Tinkerer

    Will do Jack! I'll give it a go this evening. 
  • Skier76
    Skier76 Member Posts: 67

    Tinkerer

    Jack,
    No issues assigning "E" in diskpart! I'm still getting a system cannot find the path specified error. Sent you a screen shot. 
  • Skier76
    Skier76 Member Posts: 67

    Tinkerer

    Made a change based on a quick Google: cd /d e:\EFI\Microsoft\Boot\

    Then I got to e:\EFI\Microsoft\Boot

    /Fixboot (Operation Completed Successfully)

    I'm now hung up on ren bcd bcd.old  (The system cannot find the file specified)



  • JackE
    JackE ACE Posts: 45,176 Trailblazer
    Glenn---That's OK. Try the next command "bcdboot c:\Windows /l en-us /s e: All" to see if it takes. I think earlier this command returned an error that it can't find e:\efi\Windows\boot because BootRec /FixBoot was applied to e:\efi\Microsoft\boot. Jack E/NJ PS I got your screenshot and we might have other options if bcdboot doesn't work.
     

    Jack E/NJ

  • JackE
    JackE ACE Posts: 45,176 Trailblazer
    Glenn---Your screenshot shows that you were trying to access e:\efi\Windows\boot, not e:\efi\Microsoft\boot --- Note "Windows" and "Microsoft" subdirectories.

    Also, check diskpart again to make sure the e: letter stuck. Then exit diskpart. At the command prompt, enter "attrib -h e:\" without the quotes.  If you don't get an error message, then go back into diskpart to see if the e:\ volume is unhidden.

    Jack E/NJ

    Jack E/NJ

  • Skier76
    Skier76 Member Posts: 67

    Tinkerer

    Good eyes Frank! When I tried "Windows" it could not find the directory. When I used "Microsoft" in place of "Windows" I was able to proceed with /fixboot. 

    Are Windows and Microsoft interchangeable? 
  • JackE
    JackE ACE Posts: 45,176 Trailblazer
    They should not be interchangeable --- this caused a problem before. Please check diskpart again to make sure e: letter is still there after running bootrec /fixboot successfully. Then, before running "bcdboot c:\Windows /l en-us /s e: All" , see if you can unhide e: by running "attrib -h e:\" from the command prompt without the quotes (not diskpart prompt). Let me know if you get an attrib error. Jack E/NJ

    Jack E/NJ

  • Skier76
    Skier76 Member Posts: 67

    Tinkerer

    Thanks Frank. I ran into an issue when trying to use "Windows". I'll give it another go. If it doesn't work, I'll send along a screen shot. 
  • Skier76
    Skier76 Member Posts: 67

    Tinkerer

    E: was still there in diskpart and after running bootrec/fixboot 

    When I run attrib -h e:\ from the cmd prompt, I get "File nto found - E:\"
  • JackE
    JackE ACE Posts: 45,176 Trailblazer
    edited January 2018
    Try this at the command prompt. "attrib -h e:\EFI\Microsoft\Boot\*.efi" without the quotes. Jack E/NJ

    PS: On second thought, try "attrib -h e:\EFI\Microsoft\Boot\*.*" without the quotes.

    Jack E/NJ

  • Skier76
    Skier76 Member Posts: 67

    Tinkerer

    Thanks Frank! Gave it a go and go a file not found message. 
  • JackE
    JackE ACE Posts: 45,176 Trailblazer
    edited January 2018
    Try "attrib -h e:\*.*" without the quotes. If it still doesn't find it, then try "dir e:\ /ah" without the quotes---what do you see? Jack E/NJ

    Jack E/NJ

  • Skier76
    Skier76 Member Posts: 67

    Tinkerer

    Thank you Frank!

    On the first one, I got a "Path not found - E:\"

    On the second one, "The system cannot find the path specified" 

    This computer is not liking the E drive for some reason! 
  • JackE
    JackE ACE Posts: 45,176 Trailblazer
    OK. Run the "bcdboot c:\Windows /l en-us /s e: All" command again to see if you get the same error message --- can't find e:\efi\Windows\boot. That was because bootrec /fixboot only seemed to work with the Microsoft subdirectory, not the Windows subdirectory. Jack E/NJ

    Jack E/NJ

  • Skier76
    Skier76 Member Posts: 67

    Tinkerer

    Jack,
    When I ran the above, I got Bcdboot file creation and repair tool. message followed by a long list of potential commands. Is that what we're looking for? 

    Thanks again for all your guidance. Sorry for the delay in my last response. 
  • JackE
    JackE ACE Posts: 45,176 Trailblazer
    Well, not exactly, but at least we didn't get the same error message. Better PM me a snapshot of the command list if you can. Jack E/NJ

    Jack E/NJ

  • JackE
    JackE ACE Posts: 45,176 Trailblazer
    OK Glenn, got it. Let's first try the default  "bcdboot c:\Windows /l en-us" to see if the BIOS can handle it. Jack E/NJ 

    Jack E/NJ