Win 10 fails to start after repair

[klas]

Windows 10 does not start again after a standard Tweaking repair ( after inital logo is displayed screen go dark and just the small blue circle show up anytime I move the cursor.
Tried to restore to latest systempoint with my restore USB but  after few minutes  the PC gave up the attempt showing the error 0x80070003. Tried several times.
Anything I can do now? exept starting a heavy restore after backing up all my files...?

[Boggin]

Which version of Win 10 are you using and do you have a Win 10 install disk or USB that you can boot up with ?

[klas]

I have Win 10 Home (ver 10.0.17134.1)
I made a USB recovery disk and system restore point just before repair.
USB boots nicely to meny but neither system restore  or start repair is succesful.
When I select cmd line repair it tells not enough memory for this cmd.
Still I get here the cmd cursor at /system32.

[Boggin]

I'm not sure what you get with a recovery USB.

Let's try clearing the memory by shutting down and removing all power sources and hold the power button in for ~30 secs.

It may or not boot up after that but you can give it a try - I assume you don't have any external drives plugged in while you are trying to get it to boot up ?

If you have access to another machine, can you create install media after reading the instructions at https://www.microsoft.com/en-gb/software-download/windows10

This will comply with your version of 1803.

If/when you have done that, boot up with it and navigate to the Install screen and click on Repair your computer.

This will give you the same advanced boot options.

Select Command Prompt and enter these cmds -

bcdedit |find "osdevice"

For clarity that is a Pipe symbol before find and is the uppercase of \

Using that partition letter instead of the X I have exampled, enter -

sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows

(note the space before each / )

Follow that with - again using your partition letter instead of my x

chkdsk x: /f

There are also a couple of bootrec cmds you can try, but I've never known them to work.

bootrec /fixmbr

bootrec /fixboot

You could get an error with that one.

Enter exit to close the cmd window, remove the install media and restart to see what you get.

[klas]

Thanks for instructions!
Unfortunately the problem is still the same also after Scannow and Chkdsk which did not report any errors.

FYI the disk is divided in four partitions : C: Windows  - D: Windows HP recovery - E: Photoarchive   - F:  Ubunbtu 18.04
and has dual booting via Grub. Files in C,D and E: can be read from Ubuntu.

I guess a reinstall is now getting close and I should appreciate your guidance.

[Boggin]

Did you create the install media ?

If you did can you try the restore point option from the advanced boot options to see if it will complete.

If that fails then I guess you will be looking a reinstall.

However, I have recovered a machine using a Kaspersky Rescue Disk where a after a scan, I was able to boot up.

That was using v10 but they now have v18.

https://support.kaspersky.co.uk/viruses/krd18

I use ImgBurn to create the bootable disk from the saved download - https://www.majorgeeks.com/files/details/imgburn.html

On one of my Win 10 upgraded laptops after one of the major updates, I now get an error when I run the restore option from there, but can't remember the error code that I get.

Fortunately I create regular Macrium system images to fall back on and always create one before I test run any new releases Shane puts out.

EDIT - I've just run the restore point option on that laptop and I get the error 0x80070003 as well, so if you were getting it with the recovery USB then you are likely to also get it after booting up with install media, but give it a try anyway before trying a scan with Kaspersky.

[jpm]

Another thing to try. I have no done this but it come from microsoft support.

That error looks like it is do to a bad update of windows - which is what could have lead you to us to begin with.

The solution is to "Please navigate to this location. C:\windows\softwaredistribution\datastore\logs\edb.log.
Delete the 'edb' log file and reboot the computer and check the issue."

That seems a tad too simple - but stranger things happen.


https://answers.microsoft.com/en-us/windows/forum/apps_windows_10-winapps/error-0x80070003/35f04855-cb83-4a55-ba17-e19c871a1daa?auth=1