Stuck in Automatic Repair = inadvertently changed C: drive path?

xyz · 22 Oct 2018

okay zbook

thanks a lot

will do = but has to be tomorrow = but will do these tomorrow for sure

thanks so much!

xyz · 23 Oct 2018

Attachment 209575 Attachment 209576 Attachment 209577 Attachment 209578 Attachment 209579

tried fixboot (having found out which keys worked for the symbols) = blue screen is result after restart

xyz · 23 Oct 2018

Attachment 209581 Attachment 209582 Attachment 209583 Attachment 209584 Attachment 209585

made other attempts via command

also found 2 old windows 10 flash drives (English/German) = tried to repair windows through this option (starting from Flash drive = W10 English) = unsuccessful

was unsuccessful with all the commands that Zbook gave

dalchina · 23 Oct 2018

Attachment 209594

Assuming that's what you see on trying to boot your PC after having run Fix Boot, I'd suggest booting from Kyhi's disk and actually checking what's there. I.e. can you see the files.

Now it used to be the case there was a backup copy of the registry created on each startup. Unfortunately it seems MS may have stopped that happening (3 of is have investigated that).

Turning to the SFC failure. Clearly it ran, but to have if attempt a repair you' need to use the offline version of the command.

sfc /scannow /offbootdir=Z:\ /offwindir=Z:\windows- but replace Z: with the drive letter of your Windows partition as seen from the command prompt.

How to Run SFC OFFLINE (System File Checker tool) - wintips.org - Windows Tips How-tos

Please post a picture showing the result of running Fix Boot and an updated screenshot of the partitions.

I'll leave the rest with Zbook - too much to comment on.

xyz · 23 Oct 2018

Attachment 209591 Attachment 209592

trying to resolve access denied when using fixboot I had changed in Diskpart the C: drive to V: = but when this attempt to resolve access denied fail I changed it back to C: (as seen in photo above) = but a new attempt using fixboot resulted in being told that C: could not be found (although it did find C: on the previous attempt)! so not sure what I have done there, or has happened?

xyz · 23 Oct 2018

Attachment 209599

xyz · 23 Oct 2018

Attachment 209603 Attachment 209604 Attachment 209605

dalchina · 23 Oct 2018

I think your PC is not rescuable as is.

Here is what I suggest to give you a chance to save your Windows. I believe anything else will be too complex at a distance, and probably consume a great deal of time to no good effect.

All this could have been prevented had the routine practice of disk imaging been in place.

You would need to follow the sequence exactly and without attempting anything else. I have used this in the past.

a. Create a disk image of the Windows partition, saving the image on an external drive.
Note the size of your Windows partition.
b. Clean install the same build of Windows onto your existing drive, deleting all Windows partitions as is required by this procedure. Make sure the Windows partition is a little larger than noted above.

Clean Install Windows 10 | Windows 10 Tutorials

c. Make sure your PC boots ok.
d. Restore the image of your Windows partition in place of the new Windows partition.
e. Reboot. Automatic repair will probably run and hopefully your PC will then boot.
If not, boot from the Windows install medium and run Startup Repair.

This assumes your existing Windows partition is intact and usable.

xyz · 23 Oct 2018

okay Dalchina, thanks

I am not too bothered about losing the data......with the exception of the W10 Key (an upgrade from 8.1 that was pre-installed without DVD)...it was mostly my son's games which I can download again.

Yes I made a mistake not making sure there was a backup

I have searched through some old drives and found an AOMEI W10 system Backup from 08/2017 = BUT I am not sure if it is a backup from this computer!!!??? Sorry!

Will try to follow your instructions

many thanks

zbook · 23 Oct 2018

If you have files backed up and if no other options seem workable there are some trial and error steps that can be tried to fix the underlying problem.
Report back in the thread your preference whether to clean install or troubleshoot.