You must have used a 3rd party tool to do that
diskpart
list vol
sel vol #
ATTRIBUTES VOLUME CLEAR HIDDEN
select the vol from disk 1
Type: Posts; User: Pentagon
You must have used a 3rd party tool to do that
diskpart
list vol
sel vol #
ATTRIBUTES VOLUME CLEAR HIDDEN
select the vol from disk 1
Can you post a screenshot of "Diskmanagement" again please.
1T boot didn't have a driveletter before.
diskpart
sel disk 1
ATTRIBUTES DISK
diskpart
sel vol #
We don't need that skript any more!
Rightclick on the unallocated space and create a new volume. Assign any free letter and the problem is solved!
You just killed the culprit :mad:
Be patient! Don't run that skript now! There is time!
Run this first:
diskpart
sel disk 1
sel par 3
delete partition override
sel par 2
delete partition override
exit
Just one question. Is that stuff that is running on disk 0 (C:) the problem disk that gave you the boot failure and is running now?
I don't need reagentc any more.
The answer please! A good...
OK, so you don't know how to copy a file to (C:). Doesn't matter!
Sometimes troubleshooting brings new ideas! When I look at your last Diskmanagement screenshot I have just one idea.
Use disk 0 as...
Yes, reboot and see what happens to the letter.
409362
same disk with 2 different drive letters!
And why don't you use cmd?
I changed the drive letter to k
diskpart
sel disk 1
sel par 3
det par
I use this script for years now and Microsoft doesn't use your instructions! :p
This is the original Microsoft Script to prepare the disk.
copy the file to C:\
409356
run cmd command
C:\Windows\System32>DiskPart /s C:\disk1.txt
after 5 seconds the disk is ready (C:)...
No, that's wrong
the first disk is disk 0
the first partition is always 1
According your screenshot
disk 1, partition 3 is the problematic one. Is that right?
You found
Partition 3
Type : 07
Hidden: No
if not means if you had found
Partition 3
Type : 27 for...
And why don’t you follow advices?
Diskmanagement like post #15 including the disk that has (F:) on it
cmd (admin)
reagentc /info
Did you download explorer++?
The problem is identified...
Everything is a real disaster.
- Your "Diskmanagement“ screenshot is not as it should be.
- If you know how to use Macrium the right way, s.th. like that doesn’t happen.
- The reason why you have...
The BCD_Cleanup was successful
"Diskmanagement" screenshot update was also needed!
3 long Commands to get the Recovery working
1.
bcdedit /store...
bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /set {fwbootmgr} displayorder {7fc884f2-5a91-11e6-8241-806e6f6e6963} /addlast
bcdedit /store...
You must have a 2nd EFI!
step by step and watch the system response after each input. Don't continue if s.th. was not successful
bcdedit /store...
To finalize the BCD-Clearance in addition to #20 run cmd:
bcdedit /delete {1a04f6db-5a86-11e6-a472-1866da10e8fe}
bcdedit /delete {7254a080-1510-4e85-ac0f-e7fb3d444736}
bcdedit /set {fwbootmgr}...
In order to heal the Recovery Situation on disk 0
cmd (admin)
step by step copy & paste
bcdedit /delete {daed529a-5a8e-11e6-be1d-1866da10e8bc}
bcdedit /delete...
What is your problem?
Disk 0 is not a virtual drive
You booted successfully from disk 0
run cmd
bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD /enum all...
Try these 2 command first:
cmd (admin) C:\Windows\System32>
bcdedit /store \\?\GLOBALROOT\device\harddisk0\partition1\EFI\Microsoft\Boot\BCD
reg query HKLM\SYSTEM\CurrentControlSet\Control /v...
merge Partition 1+2 to the new EFI-Partition.
Otherwise you have a useless partition Do you really want to tell me what is better?
I am waiting !!
diskpart
sel disk 0
sel par 5
det par
exit
YES, it is added!
diskpart
sel disk 0
sel par 5
det par
exit
takes only 2 minutes I am waiting for the output
YES it is as expected! A Fat 32 partition is needed as partition 1
The rest from #42 is to be done from USB
If you want we can prepare the last partition RECOVERY right now. It has to be done...
Very good, it is the preparation of the new EFI-Partition on Partition 1. Therefore a Fat32 Filesystem is needed.
Later when you boot from USB we can merge Partition 1+2 to the new EFI-Partition.
...