Feature update to Windows 10, version 1709 fails to install

Yep. But I'm no better nor worse off than I was. I think you would be one or the other.

We would delete your current BCD so that a new one is entirely regenerated. That should clear out the "parameter is incorrect" error. But there is that D:partition that was cloned to C:. I think BCDBoot will want to pull it into a dual boot - but it really doesn't belong in one as is. A proper dual boot is established by installing - not by cloning. We'd have to do stuff extra to the BCD afterward to make that work or push it back out.

That really shouldn't exist. It has done its work - it is on the SSD now. I think the D:partition should be wiped. Instead, put system images on there.

@ PCR

I have actually been wondering about using  bootrec  /rebuildbcd  instead but the difference between the two methods is clear as mud.  If anything it looks like bcdboot is a deployment tool and bootrec is a repair tool?

Good grief.  Here's another one

https://www.easeus.com/partition-manager-software/fix-uefi-boot-in-windows-10-8-7.html

(Google search for

    "bootrec /rebuildbcd" vs bcdboot  (in Windows 10)

)

@ PCR

I have actually been wondering about using  bootrec  /rebuildbcd  instead but the difference between the two methods is clear as mud.  If anything it looks like bcdboot is a deployment tool and bootrec is a repair tool?

Good grief.  Here's another one

https://www.easeus.com/partition-manager-software/fix-uefi-boot-in-windows-10-8-7.html

(Google search for

    "bootrec /rebuildbcd" vs bcdboot  (in Windows 10)

)

Please note that ,I am not a technician or Engineer in the line. I am a common man and I have not much knowledge to do the things .If I do ,my position will worst.

I've done both of those now. Neither killed me. Here is what I think I know...

(1) BootRec exists only at the Command Prompt of the Recovery Environment. It only affects the BCD itself, (which makes it safer, actually). To get a clean BCD - first backup, then delete/rename the current one. Renaming provides a second backup. That's what I did back then. Otherwise, it will merely search all drives & add any compatible Windows installation to the BCD - if it isn't already there. Here is what it produced for me (a year/more ago) before a reboot...

X:\windows\system32>bcdedit /enum

Windows Boot Manager

---

identifier            {bootmgr}

device                partition=F:

path                   \EFI\Microsoft\Boot\bootmgfw.efi

description        Windows Boot Manager

locale                 en-US

default               {default}

displayorder      {default}

timeout             30

Windows Boot Loader

---

identifier                {default}

device                    partition=C:

path                       \Windows\system32\winload.efi

description             Windows 10 Home

locale                      en-US

recoverysequence    {51a43695-16a7-11e7-a171-ad6acdb1a9b8}

recoveryenabled   Yes

osdevice                partition=C:

systemroot            \Windows

bootmenupolicy    Standard

It did not turn off the recovery partition. That got set up. But I wonder, where was "resumeobject"? But I never noticed a problem with Sleep/Hibernation that I can recall.

(2) BCDBoot exists in the Command Prompt of a booted Windows. It will not only do the BCD, but also all the boot files that are on the EFI (system) partition will be replaced. That includes the boot loader, itself. Well, I can't swear my UEFI files were replaced, because a DIR before/after shows them all to be identical. But they were mentioned in the verbose report (/v) I posted above (I think). In addition, it gave me a full set of MBR boot files, which soon I did delete. I suggest one check whether the HDD is GPT or MBR , & run with the appropriate option (UEFI or BIOS - not All).

Regarding the BCD - I wish I had deleted it first. I didn't, & BCDBoot left most junk intact, like a couple of entries that reference my empty v.1703 Recovery Partition, but are themselves unreferenced. (Soon, I'll just delete them.) But it did delete a Windows Setup entry. I wonder, had I used the /c option - would that have been as good as deleting the BCD?

It did seem to do work on the Windows Boot Loader entry - that may be fresh. But it removed the references in it to the v.1709 Recovery Partition. Therefore, a Shift+Reboot did not go there, but just did a reboot to Windows. I needed to run ReagentC to turn that back ON.

Here is what BCDBoot produced (after reboot)...

Windows Boot Manager

---

identifier              {bootmgr}

device                  partition=\Device\HarddiskVolume2

path                    \EFI\Microsoft\Boot\bootmgfw.efi

description          Windows Boot Manager

locale                  en-us

inherit                 {globalsettings}

default                {current}

resumeobject     {1669dd2d-15eb-11e8-b080-74e6e2074932}

displayorder       {current}

toolsdisplayorder   {memdiag}

timeout              30

Windows Boot Loader

---

identifier             {current}

device                 partition=C:

path                    \Windows\system32\winload.efi

description         Windows 10

locale                  en-us

inherit                 {bootloadersettings}

isolatedcontext   Yes

allowedinmemorysettings    0x15000075

osdevice             partition=C:

systemroot         \Windows

resumeobject    {1669dd2d-15eb-11e8-b080-74e6e2074932}

nx                      OptIn

bootmenupolicy   Standard

Here is what the Boot Loader entry looks like immediately after ReagentC is run...

Here was my run of ReagentC...

***************************************************************

***  Turn Recovery Environment back on with ReagentC   ***

***  after BCDBoot has turned it off.                                   ***

***************************************************************

C:\Windows\system32>diskpart

Microsoft DiskPart version 10.0.16299.15

Copyright (C) Microsoft Corporation.

On computer: PCRSCOMPUTER

DISKPART> list vol

Volume ###  Ltr  Label        Fs     Type        Size     Status     Info

  ----------  ---  -----------  -----  ----------  -------  ---------  --------

  Volume 0     E                       DVD-ROM         0 B  No Media

  Volume 1     C   PCR Hard     NTFS   Partition    930 GB  Healthy    Boot

  Volume 2         Recovery     NTFS   Partition    450 MB  Healthy    Hidden

  Volume 3                      FAT32  Partition    100 MB  Healthy    System

  Volume 4                      NTFS   Partition    790 MB  Healthy    Hidden

DISKPART> sel disk 0

Disk 0 is now the selected disk.

DISKPART> list part

Partition ###  Type              Size     Offset

  -------------  ----------------  -------  -------

  Partition 1    Recovery           450 MB  1024 KB

  Partition 2    System             100 MB   451 MB

  Partition 3    Reserved            16 MB   551 MB

  Partition 4    Primary            930 GB   567 MB

  Partition 5    Recovery           790 MB   930 GB

DISKPART> sel part 5

Partition 5 is now the selected partition.

DISKPART> assign letter=R

DiskPart successfully assigned the drive letter or mount point.

DISKPART> sel part 1

Partition 1 is now the selected partition.

DISKPART> assign letter=X

DiskPart successfully assigned the drive letter or mount point.

DISKPART> exit

Leaving DiskPart...

C:\Windows\system32>dir x:\ /a /s //This is the leftover v.1703 recovery partition

 Volume in drive X is Recovery                //I wanted to see again: The stupid thing is empty!

 Volume Serial Number is DECF-96B8

Directory of x:\

10/18/2017  07:24 AM    <DIR>          Recovery

10/14/2017  03:51 PM    <DIR>          System Volume Information

               0 File(s)              0 bytes

Directory of x:\Recovery

10/18/2017  07:24 AM    <DIR>          .

10/18/2017  07:24 AM    <DIR>          ..

09/04/2017  03:27 AM    <DIR>          Logs

               0 File(s)              0 bytes

Directory of x:\Recovery\Logs

09/04/2017  03:27 AM    <DIR>          .

09/04/2017  03:27 AM    <DIR>          ..

09/04/2017  07:24 AM             1,316 Reload.xml

               1 File(s)          1,316 bytes

Total Files Listed:

               1 File(s)          1,316 bytes

               7 Dir(s)     453,353,472 bytes free

C:\Windows\system32>dir R:\ /a /s //This is the v.1709 Recovery Partition

 Volume in drive R has no label.                      //It's loaded with good stuff.

 Volume Serial Number is 9AB3-01BA

Directory of R:\

10/18/2017  07:29 AM    <DIR>          Recovery

02/13/2018  10:24 PM    <DIR>          System Volume Information

               0 File(s)              0 bytes

Directory of R:\Recovery

10/24/2017  04:34 AM    <DIR>          .

10/24/2017  04:34 AM    <DIR>          ..

12/31/2017  03:16 AM    <DIR>          Logs

12/31/2017  06:09 AM    <DIR>          WindowsRE

               0 File(s)              0 bytes

Directory of R:\Recovery\Logs

12/31/2017  03:16 AM    <DIR>          .

12/31/2017  03:16 AM    <DIR>          ..

12/31/2017  06:09 AM             1,356 Reload.xml

               1 File(s)          1,356 bytes

Directory of R:\Recovery\WindowsRE

12/31/2017  06:09 AM    <DIR>          .

12/31/2017  06:09 AM    <DIR>          ..

09/29/2017  08:42 AM         3,170,304 boot.sdi

12/31/2017  06:09 AM             1,111 ReAgent.xml

10/18/2017  07:28 AM       441,328,704 Winre.wim

               3 File(s)    444,500,119 bytes

Total Files Listed:

               4 File(s)    444,501,475 bytes

              10 Dir(s)     364,892,160 bytes free

C:\Windows\system32>ReagentC /SetREImage /Path R:\Recovery\WindowsRE /Target C:\Windows

Directory set to: \?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>ReagentC /Enable

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>ReagentC /Info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:

Windows RE status:         Enabled

    Windows RE location:       \?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE

    Boot Configuration Data (BCD) identifier: f122fa9e-b3ff-11e7-9217-d7700d4f6e45

    Recovery image location:

    Recovery image index:      0

    Custom image location:

    Custom image index:        0

REAGENTC.EXE: Operation Successful.

C:\Windows\system32>diskpart

Microsoft DiskPart version 10.0.16299.15

Copyright (C) Microsoft Corporation.

On computer: PCRSCOMPUTER

DISKPART> list vol

Volume ###  Ltr  Label        Fs     Type        Size     Status     Info

  ----------  ---  -----------  -----  ----------  -------  ---------  --------

  Volume 0     E                       DVD-ROM         0 B  No Media

  Volume 1     C   PCR Hard     NTFS   Partition    930 GB  Healthy    Boot

  Volume 2     X   Recovery     NTFS   Partition    450 MB  Healthy    Hidden

  Volume 3                      FAT32  Partition    100 MB  Healthy    System

  Volume 4     R                NTFS   Partition    790 MB  Healthy    Hidden

DISKPART> sel vol 2

Volume 2 is the selected volume.

DISKPART> remove letter=x

DiskPart successfully removed the drive letter or mount point.

DISKPART> sel vol 4

Volume 4 is the selected volume.

DISKPART> remove letter=r

DiskPart successfully removed the drive letter or mount point.

DISKPART> exit

Leaving DiskPart...

Regarding the Easus article...

(1) I didn't have to turn off Secure Boot  for either BootRec or BCDBoot.

(2) /FixMBR & /Fixboot are for MBR type HDDs - but are likely harmless on GPT.

(3) /RebuildBCD will only look for additional, compatible Windows installations to add to the BCD - unless the BCD is renamed/deleted first. Then, it generates a whole new BCD. (I guess one could delete just the existing Boot Loader entry in the BCD, then it would be recreated.)...

X:\windows\system32>bootrec /?

Repairs critical disk structures. The following commands are supported:

/FixMbr -- writes the master boot record of the system partition using the master boot record compatible with Windows. This operation does not overwrite the existing partition table.

/FixBoot -- write a new boot sector onto the system partition using the boot sector compatible with Windows.

/ScanOs -- scan all disks for installations compatible with Windows and display the entries that are currently not in the boot configuration store.

/RebuildBcd -- scan all disks for installations compatible with Windows and allow the user to choose which to add to the boot configuration store.

(4) I'm not a fan of "/f ALL" in BootRec, unless maybe making a DVD. (But it didn't really hurt.)

(5) Where the Easus article says...

"diskpart will now show the full list of volumes on your PC, find UEFI volume from the list: UEFI partition will be on Volume 2."

That wouldn't always be true. Mine is Volume 3, but turns out to be Partition 2...