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

Ok great,

I will look into Set. I can do that quite easily. Although, I came across something that said I should connect my hard disc up to another pc. It might allow for a repair, but this is to do with SATA.

Right ok,

Well with the pictures you sent, looks like there is a good reason why it would say that.

I dont see your system installed into a Primary partition or Volume. I only see your system installed into an extended logical disk space environment which cant be set as an active partition.

See what you can try to resolve this.

Pluginz,

Here is the partition information, it is not quite as you have worked out:

C: Active (and primary) partition, with the remaining minimal windows here now - barely anything.
E: (Primary) Most of the rest of windows and all the other files are here. (After the re-partitioning by diskpart).
D: Is the extended and logical partition.
F: Recovery partition.

C: has been divided into E: as has windows on it now. (This undermines SFC and DISM functionality etc).

Had a brief look into the set command and can see where you are coming from. These environmental variables can causes a lot of issues (User folder, ...). But not for this problem, or as the main cause. But this does not seem to add up with the SATA, driver problem you mentioned like HD and CD/DVD Rom causing problems.

:)

ZBook,

Because of the SMART result. I had a new look into my old hard disc that I can still use. With these newer software tools, I can see even though it is fine now. That the bad clusters have been hidden and kept seperate. So as it is now fine and passes tests, the bad clusters are actually masked. Now I am SMART testing all externals. But I did notice one thing about GSMARTControl and HD Tune are listed really high temperature that are not true like 130 C. Whilst others are also reporting this.

:)

:)

- - - Updated - - -

ZBook,

... and also the command prompt wmic diskdrive get status - is coming back as pred fail for other discs that are fine. One of the reasons for this is due to how GSMARTControl is pre-structured. So this is no necessary a good understanding of disk health.

I mention about Logical Drives in your last picture because that is exactly what it says. It doesnt mention C being on a Primary partition, or any other, only a Logical drive so if you have any upto date pictures with the Primary or Volume as active on C then i do apologise

Can you get into the registry?
Have a few searches you can try if possible

Im thinking there is some kind of secure Rom on the other drive. The kind of secure roms that came on original game CD's amd DVD's. The powerful ones that completely stop you copying a game. Reverse this problem and things could be quite difficult.

I'll have a read through your first posts again too for refreshment

Yup, I can get into regedit via command prompt. Any ideas?

Maybe try

X:\Windows

DIR /S

Should sort system files and the last that were modified

- - - Updated - - -

Sorry just X:\Windows. Sources is another option if its there too

This is for the X: virtual drive. Windows on this has mostly a number of folders; a lot of the normal ones etc. Sources is also on this.

:)

Okies well depending on what motherboard you have. See if you can delve in to X:\Sources and change the attributes and archive and index attributes. View them to start with once in X:\Sources

X:\Sources>Attrib

If you dont see an 'R' sign in the list then Read and Write options are allowed for unwanted files

- - - Updated - - -

Try

X:\Sources>Tree
Folder PATH for listing for Volume Boot
Volume Serial Number is __________ ____:____
X:.
en-US
inf
recovery
en-US



Feedback on this would be awesome. I have been round the block with all this, many times

- - - Updated - - -

At what point do the think the system changed? Do you have any recollection of the system changes by memory?

This is an old one now but I remember going to bed one night with Windows 7 and the next day waking up with Windows 10 !!!
At that point i knew there was something wrong. It wasnt Microsofts update of Windows 10 but something different, something alien.
It all looks like Windows at first. Seems real. But really its an installation of Windows inside a modified SATA bus through the Kernel32 System update.
Have a good look through your Windows Update history and see if you can find a 'System Update'.

Event history will show a CMOS Time clock crash. Windows updates will force a reboot adjusting the time with an updated Kernel32 modification and totally screw your motherboard up.

Thats my experience anyways

- - - Updated - - -

EFI vs MUI

Its logical when you think about

As for the tree command. It is just a tree diagram of directories and subdirectories alaphabetically listed. A map if you will. But what is the problem?

My system did not change. It only changes when I make it happen.

:)

Ah i am trying to resolve an old motherboard that has a pre Windows environment for internet access but the particular bios files refuse to load.

- - - Updated - - -

So have you come up with any search enquiry solutions yet?