Page 4 of 5 FirstFirst ... 2345 LastLast
  1.    22 Sep 2016 #31

    You need to list your disks to figure out which drive letter corresponds to "the drive normally known as C:." That's because drive letters don't always (or rather, seldom, if ever) match drive letter assignments in the normal boot environment. Thus, when I boot into recovery, I usually find my drive by using the Windows Management Interface Command (WMIC) utility as follows:
    1. Open a command prompt with elevated privileges
    2. Type wmic at the command line. It has its own shell just like diskpart and other complex CLI utilities
    3. type logicaldisk get name, volumename

    Now you can figure out which drive is which. Here's a (hopefully) illustrative example:
    Click image for larger version. 

Name:	wmic-example.jpg 
Views:	4 
Size:	24.2 KB 
ID:	102582

    And of course, you'll need to type "exit" to leave the wmic cli when you're done, after which you can terminate your command line session, if you choose.
    HTH,
    --Ed--
      My System SpecsSystem Spec


  2. Joined : Sep 2016
    Posts : 28
    Windows 10
       22 Sep 2016 #32

    EdTittel said: View Post
    You need to list your disks to figure out which drive letter corresponds to "the drive normally known as C:." That's because drive letters don't always (or rather, seldom, if ever) match drive letter assignments in the normal boot environment. Thus, when I boot into recovery, I usually find my drive by using the Windows Management Interface Command (WMIC) utility as follows:
    1. Open a command prompt with elevated privileges
    2. Type wmic at the command line. It has its own shell just like diskpart and other complex CLI utilities
    3. type logicaldisk get name, volumename

    Now you can figure out which drive is which. Here's a (hopefully) illustrative example:
    Click image for larger version. 

Name:	wmic-example.jpg 
Views:	4 
Size:	24.2 KB 
ID:	102582

    And of course, you'll need to type "exit" to leave the wmic cli when you're done, after which you can terminate your command line session, if you choose.
    HTH,
    --Ed--
    "'wmic' is not recognized as an internal or external command, operable program or batch file."
      My System SpecsSystem Spec

  3.    22 Sep 2016 #33

    Bizarre! I just tried it with kyhi's recovery disk and it works fine for me. OK, there's another way using diskpart. Here goes:
    1. Fire off the admin command prompt.
    2. Type diskpart
    3. Type List volume
    Here's what that looks like:
    Click image for larger version. 

Name:	diskpart-vol.jpg 
Views:	18 
Size:	29.5 KB 
ID:	102584

    This should work in any kind of command line environment (goes back to DOS days if memory serves). Sorry for your trouble!
    HTH,
    --Ed--
      My System SpecsSystem Spec


  4. Joined : Sep 2016
    Posts : 28
    Windows 10
       22 Sep 2016 #34

    EdTittel said: View Post
    Bizarre! I just tried it with kyhi's recovery disk and it works fine for me. OK, there's another way using diskpart. Here goes:
    1. Fire off the admin command prompt.
    2. Type diskpart
    3. Type List volume
    Here's what that looks like:
    Click image for larger version. 

Name:	diskpart-vol.jpg 
Views:	18 
Size:	29.5 KB 
ID:	102584

    This should work in any kind of command line environment (goes back to DOS days if memory serves). Sorry for your trouble!
    HTH,
    --Ed--
    It looks like this now: Imgur: The most awesome images on the Internet Also, by the looks of it, do you believe there's hope of getting my system back together?
      My System SpecsSystem Spec


  5. Joined : Sep 2016
    Posts : 28
    Windows 10
       22 Sep 2016 #35

    And, if it all comes down to having to re-install Windows, will Windows 10 keep my product valid? I have a genuine product (originally Windows 7, but upgraded to 10).
      My System SpecsSystem Spec

  6.    22 Sep 2016 #36

    Yes, I think you can put your system back in working order. And yes, if you activated your upgrade based on a Windows 7 license and associated it with an MS account, your activation data (and PC) is already in the database so when you perform a clean install that should activate automatically. Keep trying!
    --Ed--
      My System SpecsSystem Spec


  7. Joined : Sep 2016
    Posts : 28
    Windows 10
       22 Sep 2016 #37

    EdTittel said: View Post
    Yes, I think you can put your system back in working order. And yes, if you activated your upgrade based on a Windows 7 license and associated it with an MS account, your activation data (and PC) is already in the database so when you perform a clean install that should activate automatically. Keep trying!
    --Ed--
    I didn't really associate it with a MS account, but I have the Windows 10 product key (and Windows 7 one, on a sticker) noted down somewhere, if that helps? And thanks, I'll keep trying, is there anything else I can try to maybe troubleshoot? It seems like the BCD file is missing also now so there are even more problems in the system...
    Do you think this guide How to Fix Error Code 0xc00007b in Windows 10 - YouTube can help?
      My System SpecsSystem Spec


  8. Joined : Jun 2015
    Posts : 10,898
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       22 Sep 2016 #38

    I do not think so, because I thought we had determined that the issue is because of the graphics driver?
      My System SpecsSystem Spec


  9. Joined : Sep 2016
    Posts : 28
    Windows 10
       22 Sep 2016 #39

    axe0 said: View Post
    I do not think so, because I thought we had determined that the issue is because of the graphics driver?
    It is yeah, but the graphics driver doesn't seem to be the only corrupt thing...it maybe broke something else with it?
      My System SpecsSystem Spec


  10. Joined : Jun 2015
    Posts : 10,898
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       22 Sep 2016 #40

    Well, the BCD rebuilding is what has already been done if I'm correct.
    In this post, the ISO is from Macrium Reflect which you booted and used the 'fix Windows boot problems' option that rebuilds the BCD.
    You could try it again, this time on the Windows partition, if you want of course.
      My System SpecsSystem Spec


 
Page 4 of 5 FirstFirst ... 2345 LastLast


Similar Threads
Thread Forum
Solved "amdkmafd.sys" "0xc000007b" BSOD during install of AMD drivers
The following was displayed in 'Automatic Repair' on startup: "The operating system couldn't be loaded because a critical system driver is missing or contains errors" "amdkmafd.sys" "0xc000007b" I had installed the new windows 10 anniversary...
BSOD Crashes and Debugging
Mouse freezing/stops, and "Last USB device malfunctioned" error.
Hi This error i'm having seems very common (seen videos and such) but I can't seem to get this problem fixed. Everything was running fine, until last Sunday. Then the mouse started to have this problem - It doesn't matter what USB port it's in...
Drivers and Hardware
"your pc needs to be repaired 0x000000e" after cloning in acronis
Hi, I have recently cloned my windows 10 in the C drive to a new F drive using Acronis True Image 2016. after attempting booting to the new F drive I get this blue screen: 74176 I tried repair with a fresh copy of windows 10 on bootable...
Installation and Setup
"add new bluetooth device" vs "join personal area network"
i don't know if i am missing something or it is a bug on w10. i click "add new bluetooth device" and then i can pair a lumia, ok. i can see my phone in "join personal area network" window. if i try to pair the phone from "join personal area...
Network and Sharing
Solved "Error (0x800F081F) - DISM Unable to find source" & "sfc /scannow"
I have upgraded 5 machines and clean installed 3 machines. Experienced an issue with one machine with continuous corruption problems After the 3rd attempt I discovered that even with a Clean Install of Win 10 I get unrepairable errors - Sorry...
General Support
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 03:51.
Find Us
Twitter Facebook Google+



Windows 10 Forums