New
#61
My MSconfig boot tab is empty, and I can't fix it
-
-
New #62
If you don't have a lot of programs and apps to re-install, I would run with a new, clean install. Also, it doesn't matter how long you use the clean install for, if you change your mind, you can always restore the old image, until you decide you don't need the old image anymore and delete it.
The way you can tell if the computer is booting from the SSD (after the clean install) is to run:
Code:diskpart list disk select disk # <- replace # with the actual number for the SSD detail disk <- if the computer is booting from the SSD, it will say Boot Disk : Yes
-
-
New #64
-
New #65
-
-
New #67
Not if you reinstall the same edition of Windows 10 (Home or Pro, etc.) that you had activated on the computer previously. Just skip entering a product key if asked for one (I think the "link" will say "I don't have a product key"). And then pick the same edition of Windows 10 that was installed previously.
-
New #68
NavyLCDR's clean install should work as planned.
This method had worked too. If possible give it a try. If it fails then can always clean install / restore.
format M: /fs:FAT32
md \EFI\Microsoft\boot
CD/D M:\EFI\Microsoft\boot
bootrec /fixboot
bcdboot c:\windows /s M:/UEFI
reboot
It may automatically run Chkdsk.
Corrected for future viewers:
format M: /fs:FAT32
md \EFI\Microsoft\boot
CD/D M:\EFI\Microsoft\boot
bootrec /fixboot
bcdboot c:\windows /s M: /f UEFI
reboot
It may automatically run Chkdsk.Last edited by zbook; 19 Feb 2021 at 20:26.
-
-
New #69
I don't think bcdboot C:\Windows /s M:/UEFI is a valid command.
bcdboot C:\Windows /s M: /f UEFI would be valid.Code:C:\Windows\system32>bcdboot /? Bcdboot - Bcd boot file creation and repair tool. The bcdboot.exe command-line tool is used to copy critical boot files to the system partition and to create a new system BCD store. bcdboot <source> [/l <locale>] [/s <volume-letter> [/f <firmware>]] [/v] [/vbcd] [/m [{OS Loader ID}]] [/addlast] [/p] [/c] source Specifies the location of the windows system root. /l Specifies an optional locale parameter to use when initializing the BCD store. The default is US English. /s Specifies an optional volume letter parameter to designate the target system partition where boot environment files are copied. The default is the system partition identified by the firmware. /v Enables verbose mode. /vbcd Enables BCD logging. /m If an OS loader GUID is provided, this option merges the given loader object with the system template to produce a bootable entry. Otherwise, only global objects are merged. /d Specifies that the existing default windows boot entry should be preserved. /f Used with the /s command, specifies the firmware type of the target system partition. Options for <firmware> are 'UEFI', 'BIOS', or 'ALL'. /addlast Specifies that the windows boot manager firmware entry should be added last. The default behavior is to add it first. /bcdclean Clean the BCD Store. By default, simply removes any duplicate entries in the BCD. Can be followed by 'full'. In this case, each entry is scanned. If the corresponding device for that entry does not exist, the entry is deleted. /p Specifies that the windows boot manager firmware entry position should be preserved. If entry does not exist, new entry will be added in the first position. /c Specifies that any existing objects described by the template should not be migrated. Examples: bcdboot c:\windows /l en-us bcdboot c:\windows /s h: bcdboot c:\windows /s h: /f UEFI bcdboot c:\windows /m {d58d10c6-df53-11dc-878f-00064f4f4e08} bcdboot c:\windows /d /addlast bcdboot c:\windows /p
-
New #70
Quote
Related Discussions
