Main Forum > General Computer Support

Startup repair after using tweaking.com

(1/5) > >>

Snek:
So i used tweaking.com and my computer on windows 10 was mostly fine, it asked me to reboot and when i did, it went into startup repair.
Now i can't boot into windows at all...
I tried using bootrec commands, tried chkdsk(no errors there), sfc (couldn't repair), nothing seems to work.
Also went to try and go to a previous restore point and guess what, it tells me there are no restore points, i am very sure i had restore points!
Eventually i tried to refresh my PC and even then windows says there was an error. I can't even reset the PC!

So can anyone tell me what tweaking.com did to put my computer into this state?
And what can i do to avoid a full format of everything, which i don't want obviously. I should have never used this tool, it worked before but this time it fucked everything up.

Boggin:
I don't know what has caused that but was there a reason why you ran the program as you say it was running reasonably fine ?

I'm not sure how you are accessing the cmd prompt to execute a chkdsk or sfc /scannow but from the cmd prompt enter shutdown /r /o and that should boot you into the advanced boot options to select Troubleshoot and then Advanced Options.

From there select Startup Settings to select Safe Mode or Safe Mode with Networking.

If that gets you to there, you can then open Windows Repair and use Option 5 and Registry Restore.

You will need to use the dropdown to see the point and then click on it to Restore Now.

If at any time you are unable to boot into the advanced boot options, you can change the boot menu policy to legacy as a precaution so that tapping the F2, F8 and F12 keys on boot will get you to the BIOS, advanced boot options and a one off boot change respectively.

To do this, from a cmd prompt admin enter bcdedit then under Windows Boot Loader check to see what it gives for your Identifier.

It can either be {current} or {default} and when using it you must use those brackets type.

Then enter bcdedit /set {your Identifier} bootmenupolicy legacy which should return the cmd was successful.

Enter shutdown /s to shut the machine down then try tapping F8 as you switch on which should give you the old advanced boot options.

Snek:
Windows search service was always crashing and restarting and DISM couldn't run properly, that's why i ran the program. I was hoping some of the repair options would fix this. Should have just left it alone i guess.

When windows automatic startup repair fails i go into recovery menu which then allows me to access command prompt, system restore, etc.
I have tried entering safe mode though and it doesn't work, i select the safe mode, it restarts and just goes right to startup repair again. It said something about an error with ACPI.sys if that helps.

Are those advanced boot options any different from what i currently have? I will try setting it to legacy i guess.

Boggin:
No, the legacy boot option gives the recovery options but is a bit more direct.

You would select Repair your computer to get to the Startup Repair and other recovery options.

At the cmd prompt see if this cmd will do anything.

I'm not sure if this cmd will work in that cmd prompt to locate the volume but enter bcdedit |find "osdevice"

(That is a Pipe symbol before find and is the uppercase of \ )

Then enter this cmd assuming c but use the partition letter if different to c

dism /image:c:\ /cleanup-image /restorehealth

Enter exit to close the cmd window then reboot to see if Windows will start.

BTW - Do you know which build of Win 10 you are using - have you updated to the Creators Update (1703) or are you still on 1607 build.

Snek:
I did that command and it said that the scratch directory size might be insufficient to perform this operation so i went ahead and added /scratchdir:c:\scratch which is a folder i created as i saw in a google result.

It gave me Error: 14098 and said component archive is damaged (Not exactly that error message as my system is not in english)
And i was in windows creators update yes, however when i run dism it says "Image version: 10.0.15063.0" which is older right?
Also, thank you very much for your help so far.

Navigation

[0] Message Index

[#] Next page