Diskpart - remove drive letter, but returns on reboot / Recovery Parti

Sorry, I am totally blind and blank on this thread. Too much for me to understand and make anything out of . And it has been so in Windows 10. I would be glad to take on any partition Recovery /Data recovery on an external / non-system drive but not on Windows 10 System disk. If a partition Structure gets corrupted on a GPT system drive, it is very difficult and almost impossible to rectify and make the system bootable again. Data recovery ? Yes, the OP can boot from a Live Linux Pendrive and try to recover. And @zbook there is always the the Live Ubuntu, which you usually recommend.

Thanks @jumanji for commenting.

Hi Pluginz,

Thanks for getting back to me and mentioning an extra drive. I am sure that there is only the c: drive that has been re-partitioned into e: as well by diskpart automatically as it booted due to chkdsk finding errors; then there is a d: drive - laptop had two drives - ; and finally the OEM recovery partition as f: which changed from hidden etc. Both diskpart and GParted along with TestDisk show these drives. But the problem is the OS is divided between c: and e: For c: there is barely anything but the bootmgr is here and for e: a long with the boot loader there is everything else.

:)

In response to Bree:

Yup, you are correct about this. It occurred to me afterwards too. I can always turn to this come the time. But I have found another possible solution that I need to look into when I can. It is this for diskpart:

detail vol

one of the entries listed is this is:

No Default Drive Letter: No

If I can say "yes" to this that should work? It starts with this possibly

attributes volume .... - but so far what I did applied to all!!!

So I will need to work on that come the time.

:)

For zbook.

I cannot get into the windows desktop, in WinRE and command prompt is all I can use.

:)

However, I have progressed a bit if you want to know? I found system32 on e: in a folder, found.000>dir0000.chk which was created by chkdsk after the power surge of just coming out of hibernation. No files within seem corrupted; well! The corruption mostly happened at the metadata level of the file system; hence .chk extension on only the folder. Then I moved all the files into a new system32 folder placed this in windows and rebooted.

Now I get a new startup-repair / automatic repair error:

'Your pc did not start correctly.'

That then gave srttrail.txt errors of:

'the os is incompatible with startup repair' then 'bad hard disc' but 'partition repair' has now gone.

I tried to use DISM, but this is stopped due to the temporary folder on x: and permissions despite changing this with - takeown .... and icalcs ... This also relates to the permissions on the sources folder, which I removed. Still no joy.

Yet this allowed me to do more of a 'reset pc'. That gets to 1% now. It involves a few errors. So I built a new .iso that still fails at 1% but with far less errors - 0x80070002 and 0x80004005. Now I am trying to open a windows troubleshooter off a usb for the first error.

Error code: 0x80070002 = The system cannot find the file specified
Error code: 0x80004005 = Unspecified error




See if these tools are useful:

On a working computer create:

a) a new bootable windows 10 iso 1909:
https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10
Create Bootable USB Flash Drive to Install Windows 10


b) bootable Ubuntu flash drive:
Create a bootable USB stick on Windows | Ubuntu tutorials
Create a bootable USB stick on Windows | Ubuntu
Linux to the rescue! How Ubuntu can help a computer in distress | PCWorld

c) Kyhi boot rescue flash drive:
Toolkit Item: Kyhi’s Rescue Disk – Win10.Guru
Toolkit Item: Kyhi’s Rescue Disk – Win10.Guru

d) Macrium rescue media:
Macrium Software | Macrium Reflect Free
Macrium Software | Macrium Reflect Free
Creating rescue media - KnowledgeBase v7 - Macrium Reflect Knowledgebase - KnowledgeBase v7 - Macrium Reflect Knowledgebase
Creating rescue media - KnowledgeBase v7 - Macrium Reflect Knowledgebase - KnowledgeBase v7 - Macrium Reflect Knowledgebase
Fixing Windows boot problems - KnowledgeBase v7 - Macrium Reflect Knowledgebase - KnowledgeBase v7 - Macrium Reflect Knowledgebase
Fixing Windows boot problems - KnowledgeBase v7 - Macrium Reflect Knowledgebase - KnowledgeBase v7 - Macrium Reflect Knowledgebase

Hi all,

Thanks for getting back to me. But to let you know from the start I had a bootable version of windows 10 off a DVD. And as I mentioned I made a new one with the iso noted above.

Also I used UBCD as the live CD, with TestDisk, GParted etc.

Please note partition structure ok, TestDisk also states this and caused the change with the drive letter.

Thanks for the error code, will look more into the other live CD's aware of them already.

Any more ideas on DISM, repair image and temporary folder on X: Other ways of getting reset pc to work?

:)


:)

For reset there are generally two options:
a) save files
b) remove files

The former is most similar to a custom install.
The later is most similar to a clean install.

Both can be done with a bootable Windows 10 iso:

Custom Install Windows 10
Clean Install Windows 10

Digging through the log the 'reset pc' errors (PBR), 0x8007002: are for csrss.exe; smss.exe and ntdll.dll for the destination drive. And 0x80004005 are for reading the version number of the required OS binary, build number and OS metadata. There is a bit more, but does this help more with 'reset pc'?

:)

Often metadata corruption requires a re-installation.

The re-partitioning has put virtually all of the files on e:. The c: drive is now so tiny; separated away. This was done to protect the files, the files in found.000>dir0000.chk created by chkdsk seem fine. At least a reset can deal with the two drives.

:)

Shell=C:\command.com/E:____KB /_=C:\_______\FDAUTO.BAT

- - - Updated - - -

command.com C:

Turn off any FDAPM settings too