Upgraded SSD
Dell Latitude 5480
I booted acronis usb and imaged to usb hard drive. Replaced Sandisk 128 GB with Samsung 250GB. Everything runs fine, except when I cold boot. I must choose boot partition.
I found this in Event Viewer.
Warning 5/15/2018 9:27:53 PM Kernel-PnP 442 None
Device SCSI\Disk&Ven_Samsung&Prod_SSD\4&2ccb24eb&0&000200 was not migrated due to partial or ambiguous match.
Are there a way to repair this without starting over? I thought about updating to 1803.
Hi Enchantech
I edited my profile and screenshot of Disk. This is for: PC 03 Dell Latitude 5480 Laptop. Should be more understandable now.
Thanks
Thanks for the new screenshot, your previous image now makes more sense as the Windows Boot Manager is offering you a choice between Windows 10 and either of the two Windows Recovery environments, which wouldn't normally be shown.
If you select one of those recovery environments, you can try doing a Startup Repair to correct the Boot Manager configuration, or else download / use a tool such as EasyBCD and remove the entries for the 2 recovery partitions.
Note: if selecting a recovery partition, pick the smaller one (on Volume 4) as given the 8GB size of the other partition, that is probably for restoring your computer to how it was shipped from the factory!
Edit: You should save a backup of your BCD file before doing the following. Use this line to make a backup file:
bcdedit /export "<path>\BCD_Backup"
Where <path> is the full path to a folder on an external USB drive. You may need this if you make a mistake.
The boot menu you see is controlled by the BCD file. Open a command window as administrator and enter:
bcdedit /enum all
Look at the beginning of the output at the Firmware Boot Manager section. Here is what mine looks like:
Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {5083aadb-4db6-11e8-9ac4-806e6f6e6963}
{afc68dd3-4b1c-11e8-9aa5-806e6f6e6963}
{afc68dd6-4b1c-11e8-9aa5-806e6f6e6963}
{5083aad9-4db6-11e8-9ac4-806e6f6e6963}
{eaa1a2b4-532a-11e8-9aef-806e6f6e6963}
{afc68dd8-4b1c-11e8-9aa5-806e6f6e6963}
{38bdf3ef-4c0f-11e8-9aad-806e6f6e6963}
{bootmgr}
{5083aada-4db6-11e8-9ac4-806e6f6e6963}
timeout 1
Notice there is only one {UUID} after the {bootmgr} line in the displayorder section. You should see three {UUID's} listed. You need to remove the two {UUID's} you don't want to show in the boot menu. Match the {UUID's} to Windows Boot Loader sections shown in the output. Confirm that two of them refer to Windows Boot Loaders for Recovery functions. These are the two you need to remove from the list. The third is your Windows system and you won't see the {UUID} in a Windows Boot Loader entry. That is because it is being shown with the id of {current} because you are booted into Windows.
You do not want to delete the {UUID's} for the recovery partitions. You only want to remove them from the display order. Use the following line to remove one entry at a time:
bcdedit /displayorder {UUID} /remove
You need to type the long UUID exactly as it is shown. After you remove the two unwanted entries, reenter:
bcdedit /enum all
Now you should only see one line after {bootmgr}. Reboot Windows to see if your problem is fixed. Whatever you do, do not remove the third entry that does not match a Recovery Partition. That will stop you from getting back into Windows. It can be fixed, but I won't go into it unless you make that mistake.
Hi Steve/Mustang
I tried to boot from Volume 4, see screenshot 0A. Searched for 0xc000000f and found https://www.wintips.org/fix-error-0xc0000428-0xc0000225-0xc000000f-at-w…. Tried Method 2. Run Startup Repair. Screenshots 0B, 0C. Would boot, show Dell Logo and repeat. I thought Windows was doing that, so I could maybe change boot options in BIOS? Read Method 5, Repair Boot Configuration Data. I was going to list volume and exit for a look. Read Mustang's post and tried that. SUCCESS. I copied to CMD notepad before I enter exit. Thanks Steve/Mustang, I was just wondering what to do.
Your Windows Recovery is disabled. Check this by opening a command prompt as administrator and entering:
reagent /info
You should see the Recovery status is disabled. Before you try to enable it, do some cleanup in the BCD file. Use the following lines one at a time:
bcdedit /delete {0b0e7b73-2d10-43df-9db6-03d71cea3bda}
bcdedit /delete {1349916f-ab08-4825-8a6e-a9a1d354f26f}
bcdedit /delete {d799041a-2ede-11e7-b4dc-d481d7bf4635}
bcdedit /delete {d799041f-2ede-11e7-b4dc-d481d7bf4635}
bcdedit /delete {d799041f-2ede-11e7-b4dc-d481d7bf4635}
bcdedit /delete {d7990420-2ede-11e7-b4dc-d481d7bf4635}
Now repair the Recovery Environment with the following lines:
bcdedit /set {e81ee387-caa2-11e7-8dd3-853f5db5f910} device ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{e81ee388-caa2-11e7-8dd3-853f5db5f910}
bcddeit /set {e81ee387-caa2-11e7-8dd3-853f5db5f910} osdevice ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{e81ee388-caa2-11e7-8dd3-853f5db5f910}
Now see what the BCD looks like:
bcdedit /enum all
Now check to see if Recovery is enabled:
reagent /info
If Recovery is still disabled, enter:
reagent /enable
Check the Recovery status again:
reagent /info
Recovery should show as enabled.
You should now be all set. Post the final BCD file and I'll see if it looks okay.
Hi Mustang
I turned off and started computer. All the boot loaders are not before window setup now, did not think to time boot. I think everything went OK. CMD2 notepad uploaded, before it’s renamed. Hoping this finished it.
Thanks
It looks good. Just one more step. I repeated one of the delete lines by mistake. No harm was done. Only 5 of the 6 entries were deleted. Take out one more so there is only one Resume from Hibernate entry:
bcdedit /delete {d799041d-2ede-11e7-b4dc-d481d7bf4635}
OK, only one Hibernate left. CMD3 attached.
Thanks
Looks great. You should be all set.
I think so to. Maybe the reason I could not earlier boot Window recovery or usb to repair options.
Thanks, Everyone ?