bcdedit /set error

impelseimpelse Member Posts: 1,237 ■■■■□□□□□□
I am doing the excersie on chapter 2 on page 108

Adding a VHD to the Boot Menu

When I type:

bcdedit /set {d58405b5-182c-11df-b78e-9c87785be52d} device vhd=partition w:

I get this:

The device is not valid as specified.
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.

I also saw this link in mycrosoft:

Add a Native-Boot Virtual Hard Disk to the Boot Menu

How did you fix this problem? Because I checked everwhere and I do not have any clue.
Stop RDP Brute Force Attack with our RDP Firewall : http://www.thehost1.com
It is your personal IPS to stop the attack.

Comments

  • Hyper-MeHyper-Me Banned Posts: 2,059
    Perhaps a dumb question on my part but have you mounted the VHD using diskpart before trying this?
  • impelseimpelse Member Posts: 1,237 ■■■■□□□□□□
    I Initialized the disk using Disk Management acording to the exersice. There is not any instruction to use diskpart
    Stop RDP Brute Force Attack with our RDP Firewall : http://www.thehost1.com
    It is your personal IPS to stop the attack.

  • Hyper-MeHyper-Me Banned Posts: 2,059
    Disk Management is fine, Diskpart is just the command line way of doing it.

    Post a screenshot of your Disk Management.
  • impelseimpelse Member Posts: 1,237 ■■■■□□□□□□
    This is the picture
    Stop RDP Brute Force Attack with our RDP Firewall : http://www.thehost1.com
    It is your personal IPS to stop the attack.

  • Hyper-MeHyper-Me Banned Posts: 2,059
    It *might* be because there isnt any OS on that partition.

    Did you open the command line with "run as administrator" ?
  • Hyper-MeHyper-Me Banned Posts: 2,059
    I followed the technet article you linked to and it worked fine for me.
    C:\Windows\system32>bcdedit /copy {default} /d "vhd boot (locate)"
    The entry was successfully copied to {c70d6f64-b322-11de-ba21-8e158a7070bf}.
    C:\Windows\system32>bcdedit /set {c70d6f64-b322-11de-ba21-8e158a7070bf} device v
    hd=C:\test.vhd
    The device is not valid as specified.
    Run "bcdedit /?" for command line assistance.
    The parameter is incorrect.
    C:\Windows\system32>bcdedit /set {c70d6f64-b322-11de-ba21-8e158a7070bf} device v
    hd=[locate]\test.vhd
    The operation completed successfully.
    C:\Windows\system32>bcdedit /set {c70d6f64-b322-11de-ba21-8e158a7070bf} osdevice
     vhd=[locate]\test.vhd
    The operation completed successfully.
    C:\Windows\system32>bcdedit
    Windows Boot Manager
    --------------------
    identifier              {bootmgr}
    device                  partition=\Device\HarddiskVolume1
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {globalsettings}
    default                 {current}
    resumeobject            {c70d6f60-b322-11de-ba21-8e158a7070bf}
    displayorder            {current}
                            {c70d6f64-b322-11de-ba21-8e158a7070bf}
    toolsdisplayorder       {memdiag}
    timeout                 30
    Windows Boot Loader
    -------------------
    identifier              {current}
    device                  partition=C:
    path                    \Windows\system32\winload.exe
    description             Windows 7
    locale                  en-US
    inherit                 {bootloadersettings}
    recoverysequence        {c70d6f62-b322-11de-ba21-8e158a7070bf}
    recoveryenabled         Yes
    osdevice                partition=C:
    systemroot              \Windows
    resumeobject            {c70d6f60-b322-11de-ba21-8e158a7070bf}
    nx                      OptIn
    Windows Boot Loader
    -------------------
    identifier              {c70d6f64-b322-11de-ba21-8e158a7070bf}
    device                  vhd=[locate]\test.vhd
    path                    \Windows\system32\winload.exe
    description             vhd boot (locate)
    locale                  en-US
    inherit                 {bootloadersettings}
    recoverysequence        {c70d6f62-b322-11de-ba21-8e158a7070bf}
    recoveryenabled         Yes
    osdevice                vhd=[locate]\test.vhd
    systemroot              \Windows
    resumeobject            {c70d6f60-b322-11de-ba21-8e158a7070bf}
    nx                      OptIn
    
  • Hyper-MeHyper-Me Banned Posts: 2,059
    I looked back at your OP and your input for device as partition W: is not valid. Its looking for the actual VHD file name and location, not the letter its assigned in disk management.
  • impelseimpelse Member Posts: 1,237 ■■■■□□□□□□
    I will follow the microsoft link and not the exersice's book
    Stop RDP Brute Force Attack with our RDP Firewall : http://www.thehost1.com
    It is your personal IPS to stop the attack.

  • Hyper-MeHyper-Me Banned Posts: 2,059
    Others have said there are numerous errors in the 70-680 book.

    If you find something else that doesnt quite "jive", take a look at the following link to see the corrections.

    Amazon.com: Customer Discussions: 70-680 Errata Thread
  • impelseimpelse Member Posts: 1,237 ■■■■□□□□□□
    Hyper-Me wrote: »
    Others have said there are numerous errors in the 70-680 book.

    If you find something else that doesnt quite "jive", take a look at the following link to see the corrections.

    Amazon.com: Customer Discussions: 70-680 Errata Thread

    Thanks for the Amazon's link:

    This was the problem acording to the corrections:

    Page 108
    bcdedit /set <guid> device vhd=partition w:
    Should be
    bcdedit /set<guid> device partition=w:

    Now it is working, thanks.
    Stop RDP Brute Force Attack with our RDP Firewall : http://www.thehost1.com
    It is your personal IPS to stop the attack.

  • johnsonjamjohnsonjam Registered Users Posts: 1 ■□□□□□□□□□
    I know this post is old, I found it from google but I am getting the same issue as listed I do all the steps listed and I am getting The system cannot find the file specified. I attached a screenshot of everything. Thanks in advance for any help.

    EDIT: Is there a way to attach screenshots?
  • StephenOnTheGridStephenOnTheGrid Banned Posts: 27 ■□□□□□□□□□
    yeah that 70-680 ms press book has a lot of typo's but it isnt the first i've come across in the series of IT books with errors.

    Here are some examples of my notes:

    Using the Diskpart Utility to Create and Attach a VHD
    You can use the Diskpart command-line utility to create and attach a VHD by performing the
    following steps:
    1. On the Accessories menu, right-click Command Prompt and choose Run As
    Administrator. If necessary, click Yes to allow the program to run.
    2. Enter diskpart.
    3. Enter create vdisk file=c\win7\myothervhd.vhd maximum=20000. This creates
    a VHD file called Myothervhd Win7 with a maximum size of 20 GB in a folder called
    Win7 on the C: drive. You can also create a VHD on a second internal hard disk or on
    a USB external hard disk formatted with the NTFS filing system.
    4. Enter select vdisk file=c:\win7\myothervhd.vhd.
    5. Enter attach vdisk.
    6. Enter create partition primary.
    7. Enter assign letter=v.
    8. Enter format quick label=Windows7.
    9. Enter exit.


    Install Win7 on VHD use WAIK cmd as admin
    imageX.exe /apply i:\win7ent.wim 1 V:

    Configure boot - WinPe ISO use the X: drive that is loaded by default
    X:Windows\system32\bcdboot.exe c:\windows

    Boot settings for VHD
    Bcdedit /copy {current} /d "Win7"
    Bcdedit /set {guid} device vhd=c:\win7VHD.vhd
    Bcdedit /set {guid} osdevice vhd=C:\win7VHD.vhd
    Bcdedit /set {guid} detecthal on
    Bcdedit /v

    Example:
    Bcdedit get's you the GUID
    First
    Bcdedit /copy {current} /d "You name it here"
    Bcedit copy the GUID for Win7 or whatever it was named

    C:\Program Files\Windows AIK\Tools\x86>bcdedit /set {a872c930-5774-11e2-a2f0-000
    c290179bc} device vhd=[c:]\win7VHD.vhd

    C:\Program Files\Windows AIK\Tools\x86>bcdedit /set {a872c930-5774-11e2-a2f0-000
    c290179bc} osdevice vhd=[c:]\win7VHD.vhd

    C:\Program Files\Windows AIK\Tools\x86>bcdedit /set {a872c930-5774-11e2-a2f0-000
    c290179bc} detecthal on

    detecthal on if you plan on whoring the VHD file on other machines otherwise it isnt necessary on the same PC using vmplayer.

    Cheers
    Stephen
Sign In or Register to comment.