New
#71
Does this look o.k.? no 3, is the worry, not sure what it is -
If it is o.k., then I just need to click the 'Write' tab.
DISKPART tried to create a Partition, has not worked
-
-
New #72
Need to put the hard disk into the laptop and see if it boots up. Will report back.
-
New #73
Just now saw your post # 71. Judging by what Partition Wizard showed in your posts#26 & 27 it appears to be correct. It is the same. In any case we cannot change anything and have to take what it shows. Right or wrong, that wouldn't in any case have any relevance to the bootabality issue.
So let us see whether the drive is bootable.
-
New #74
If not, it may be possible to make it bootable. @NavyLCDR would know...
Will not boot except through recovery - every timeNavyLCDR said:
-
New #75
Hi Guys, it boots into this screen; if any options are selected
It just stays on the same screen.
-
New #76
That's a good sign, it should be repairable. I'd try @NavyLCDR's suggestion I quoted earlier...
Download the ISO for version to suit the system to be repaired (x64 probably). Prepare a USB flash drive using Diskpart....Kyhi's bootable recovery tools has multiple partition programs that will let you do that, and it also has Macrium Reflect Free which is very good at repairing Windows booting problems.
Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums
...mount the ISO and copy all files and folders from the ISO to the USB. This will now be a bootable Kyhi rescue disk. Boot from it and run the Macrium Reflect PE that you'll find on the desktop, here you will find the boot repair option.
PS: The ACTIVE diskpart command is not necessary for booting on a UEFI system like the one you're working on, it's only needed for booting a legacy BIOS system.
-
New #77
Hi Bree
I'm not sure if the Kyhi Rescue Disk will help; until I clear/get rid of the following error. The same error appears at the Command Prompt and on Boot Up (on occasions). This is the error that came up prior to nephew/Diskpart issues.
At Boot Up it produces the following error code:
0xc000017 Windows 10
at Command Prompt it states:
'no ramdisk memory' (summary of error message)
This is the fix:
Boot your computer into Windows.
Right click the Start button and select Command Prompt (Admin).
Type bcdedit /enum all and press Enter.
You'll see a list of all the memory locations that have been deemed 'bad', this list can be cleared.
Type bcdedit /deletevalue {badmemory} badmemorylist and press Enter (type this verbatim, {badmemory} is not a placeholder for anything).
It doesn't work, it throws up another error message: 'An error occurred while attempting to delete the specified data element. Element not found'.
Here's a long article on it, I need to go through it and try a few things: - Windows 10: Update error 0xc0000017 (no ramdisk memory) | Borns Tech and Windows World
-
New #78
@rebel1, when you type bcdedit /enum all what do you see in this section of the results?
Do you even have that {badmemory} section identifier? If not, that would explain why you cannot find a value in it to delete and possibly why you get an error at boot.Code:RAM Defects ----------- identifier {badmemory}
If it's missing then create it.
bcdedit /create {badmemory}
Last edited by Bree; 08 Jun 2018 at 05:28.
-
-
New #79
-
New #80
With nothing listed beneath it? If so, maybe the {badmemory} entry is corrupted somehow and that's why you cannot delete its badmemorylist item.
You could try deleting it then creating it again to clear it.
bcdedit /delete {badmemory} /f
bcdedit /create {badmemory}
Or maybe it isn't corrupt and the {badmemory} isn't your problem. I get that on a good machine if there are no items in the badmemorylist.rebel1 said:
Quote
Related Discussions
