New
#11
I ran the sfc scan in offline mode as suggested above and it came back with "found corrupt files but was unable to fix some of them". I have the log, plus a photo of the short report (prtscreen wouldnt work for me at that point).
Corrupted C: drive?
-
-
-
New #13
-
New #14
Hi Spunk. I think the reason for that is because in post 6 I used MS Disk Management to show the partition layout, but in post 9 following Dalchina's suggestion I used Mini Tool - below is the rationale -
"Why? It provides a lot more info, and shows a small partition that is NOT shown by Disk Management by design.[/QUOTE]" So no I didn't change anything - its hidden normally is my conclusion. That 4th, reserved partition is only 1% used by the way.
This is the photo of the offline SFC run i performed earlier today. Not quite there yet. If required i can post the log if there is a good way to do that. Its at this point i realise the limit of my knowledge/abilities!
- - - Updated - - -
Spunk, The way the messages show up here is quite confusing, I did reply to you , but it seems that message has only know revealed itself. Sorry for the confusion.
Following the SFC run above, Ghot proposed i run Dism again against G:\System, and that has completed successfully, result below..
Ghot, is the next step to put the disk back in the original PC, or are their any further steps to take? e.g. run SFC again? and thanks for getting back.
FYI I have ordered additional back up storage, as I have run out of available disk space for the moment.Last edited by markky99; 1 Week Ago at 09:36.
-
New #15
Your labels are horrible! Not even a "Windows" label!
Your SFC-Command was wrong!
Run diskmanagement like this: diskmgmt.msc
or rightclick on <Start> and select "Diskmanagement"
A Diskmanagement screenshot showing all disks (including problematic) with visible columns (1) and (5) in the upper part like in post #6. Do exactly what I said!Last edited by Pentagon; 1 Week Ago at 11:40.
-
New #16
Well thx for joining the conversation Pentagon, but not sure what you are trying to tell me. My intention above was in response to previous guidance to perform a SFC command in off line mode. Part of that operation involves the use of Diskpart which doesn't show disk descriptors as you might normally see them. I have to run offline in this case because the problematic PC is non-bootable and therefore i have its boot disk (G:\System in this case) mounted in a second PC. From there i can run operations such as SFC and DISM to clean up the Disk. In this instance I am only interested in the partitions on the G:\System disk. It would only confuse if I were to show all the disks from the second PC which are not relevant to my problem.
-
New #17
I don't like discussions! I prefer solutions. The precondition for getting help and a solution is a good cooperation.
In the hole thread I can't find any helpful response. Just worthless stuff! And one more time and the last time:
Your SFC-Command was wrong and your DISM-Command was wrong as well.
-
New #18
Having said I wasn't going to show the disks from the supporting PC, here I show some, because i am looking at the difference between the fourth partition of the working system disk (C:\ Local Disk) aka Disk 2 at the top of the picture, and the same partition on the problematic (G:\ System Disk), Disk 4. two differences that I can see are - 1. The label, and 2. the format. The label on Disk 2 , top right, is showing (Recovery Partition) and for Disk 4 it is (Data Partition).
The format - I think this what it is, lower right is showing (NTFS) for Disk 2, and just "System Reserved" for Disk 4. My question is, if I were to load Disk 4/G:System back into the non-working PC, will it boot? I suspect not. And as a pointer it has already been pointed out that MiniTool, which this representation is using, is used because it is able to show this 4th partition, Disk Management doesn't show it.
-
-
New #19
The SFC command is run in Offline Mode and is correct it is Not Wrong, if you are in the Windows Recovery Environment. And you are not in Windows and booting to the Troubleshooting menu.
If you are IN Windows the command run from the Command Prompt Run as Admin would be SFC /scannow.
The DISM command is also correct as the Operation Completed Successfully.
Now run SFC /scannow in Windows again. If it comes up with No Integrity Violations, then it has repaired Windows.
Your pictures of Disk Management in post #6 and #9 have changed. This had nothing to do with Mintool.
Nonetheless, It is the correct Partitioning scheme now and all disks are Initialized GPT.
-
New #20
Thanks Spunk - I did run that SFC "offline", and was in Windows recovery mode deliberately. This is because I was targeting a suspect system disk taken from a non-working PC, and now connected to a different working pc. I did not want to target the current working system disk shown here as Disk2.
You suggest I run SFC again which I am happy to do - would that be back in the original PC, or once again in offline mode on my supporting PC?
Quote
Related Discussions
