Tweaking.com Support Forums
Main Forum => General Computer Support => Topic started by: garnita on June 12, 2019, 01:13:59 pm
-
Microsoft tech support couldn't help, and tried to do a reset with keeeping my files but that didn't work. Anything I can try to revert? I have no restore points to use or image file etc.
I am now in Lazysoft recovery suite but doubt if anything there will help.
Thanks
-
This is what another member posted who had similar problems -
Boot with Windows installation DVD/USB, select repair and open a command prompt.
Type diskpart
Type select disk 0
Type list partition
then note the partition number where you installed windows.
You may need to list volume to identify the letter of the windows installation.
Type select partition X (X is the partition number where Windows is installed)
type active
type exit
type bcdboot x:\windows (where x is the letter of your windows partition)
What are you using to post on ?
If you don't have Win 10 install media but have access to another machine, you can create install media after reading the instructions at https://www.microsoft.com/en-gb/software-download/windows10
When you boot up with it, navigate to the Install screen and click on Repair your computer which will take you to the same advanced options as pressing and holding SHIFT throughout a restart.
Click on Troubleshoot and select Command Prompt.
For interest, how did the MS tech access the advanced boot options to try the Reset ?
-
I did a boot repair and am able to access advanced boot options, but none of them worked.
I am posting with my other desktop computer, also running win10.
Already tried the repair options and the "reset and keep files options" none of which worked. It started to reset up to 30% then proceeded to undo all changes and went back to square one.
Based on this, will steps with command prompt still help?
I have this info from the boot repair: Can this help?
http://paste.ubuntu.com/p/TvcnmpMPrp/
-
Give those cmds a try.
What do you mean you did a boot repair ?
-
I have this info from the boot repair done from a usb stick with ubuntu: Can this help?
http://paste.ubuntu.com/p/TvcnmpMPrp/
-
Can you press and hold F2 as you switch on to go into the BIOS to see if you have Secure Boot and if so, disable it.
Press F10 to Save and Exit.
If that doesn't get you in normally then execute those cmds as I've described.
I'm not sure if performing a chkdsk /f from that cmd prompt would help but you would first need to enter bcdedit |find "osedvice" to give you a partition letter and then enter chkdsk x: /f where x is your partition letter.
Let me know if you get an error message when entering either of those two cmds.
For clarity that is a Pipe symbol before find and is the uppercase of \
I've already passed this onto Shane and will contact him again so that he can read the Ubunto report.
-
I just entered the cmd's and and found my OS in partition 2, letter C. Was just about to enter the boot command you gave me when I saw your new post. Should I try to check the Bios first regarding secure boot?
I am doing the chkdsk now. It has deleted a bunch of "corrupt attribute records" . It says "windows has made corrections to the file system. No further action is required". No bad sectors.
Btw, Your help and quick responses are much appreciated.
-
The chkdsk may have done it so enter exit to close the cmd window, shut down and see if it will boot, otherwise execute that first lot of cmds to make the partition active.
You could check the BIOS for secure boot.
-
Couldn't find anything regarding "secure boot" in the bios.
Tried the cmd commands and got "Failure when attempting to copy boot files"
Below is the command I executed, then got above "Failure" message
X:=\windows\sytem32>bcdboot c:\windows
-
Try these cmds -
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
If the /scanos reports no Windows installations found, try these cmds -
ren c:\bootmgr bootmgrbackup, where c: is where your Windows is installed
bootrec /RebuildBcd
bootrec /FixBoot
There are other bootrec suggestions in this article - https://neosmart.net/wiki/bootrec/#bootrec_ScanOs_doesn8217t_find_Windows
I'm going to have to shoot off shortly as it has turned 1:00am here in the UK.
-
Ok, thanks for your help, will keep trying with your advice. gnite
-
Tried everything suggested but no luck. Windows OS is listed, but when I say "yes" to add it to the boot list - it says can't be found. Crap
So Windows is not showing as a boot option at all.
-
I've never had much confidence in the Startup Repair in the advanced boot options, but give that a try.
What was the reason why you originally ran the Windows Repair program and did you use the latest version of 4.5.1 ?
-
Let's see if the machine will boot into Safe Mode.
From Win 8 onwards, booting into Safe Mode has resolved some normal boot problems.
I'd forgotten about this cmd - boot up with the Win 10 install media and navigate to the Command Prompt and enter these cmds -
bcdedit
Look for the Windows Boot Loader - it will either be {current} or {default} then enter this cmd - I'm using {default} in my example.
bcdedit /set {default} bootmenupolicy legacy
exit
then shut down.
This gives you the old F8 options.
Tap F8 as you switch on and then select Safe Mode from the advanced boot options and press enter.
See if it will then boot normally after the restart, if it does boot into Safe Mode.
To revert the boot menu policy, redo the bcdedit cmd changing legacy to standard
bcdedit /set {default} bootmenupolicy standard
I came across this Boot Repair Disk but given the author's name, it may be similar to your Ubunto one.
https://sourceforge.net/projects/boot-repair-cd/
I selected Save on the download and used ImgBurn to create a bootable disk, but you may already have your own burner tool.
https://www.majorgeeks.com/files/details/imgburn.html
-
When i enter bcdedit, it says The boot configuration data store cannot be opened. The requested system device cannot be found.
-
http://paste.ubuntu.com/p/5GRTyzMGF6/
Just ran the boot repair program as you suggested. Above is the log. Still won't recognize windows as a boot option.
As per your question, I didn't use the updated version of the windows repair program, but it seemed to work earlier so I thought it was fine. I just ran it to help speed up my computer.
-
It's possible that running an earlier version of the repair program is the reason you are unable to boot up.
This had caused problems for some previously.
The Windows Repair program isn't a tune up program.
With each version of Win 10 MS change the Permissions which is why Shane needs to update the repair program to be compatible with that while remaining compatible with previous versions.
Which version of Win 10 are you on ?
That's bad news about the bcd store.
I've only come across one Google link about the MIBRL is missing and that guy ran Startup Repair which resolved it - did you run Startup Repair as I suggested earlier ?
However, there are some interesting cmds at the bottom of this article - https://www.boyans.net/RepairWindows/RepairWindowsBCD.html
If the Startup Repair doesn't resolve, can you also scroll down to the Win 8.1/10 section in this article - https://appuals.com/bootsect-exe-use/
-
I am using Windows 10 Home version. Yes I tried the Startup Repair tool a few times with no luck. I was hoping maybe you would find something in the log file that would help.
I will try some of your other link suggestions, but it's not looking good and I'm not too sophisticated with computers unfortunately.
If only I could get "Windows" recognized as a choice in the boot menu, but it
does not show up.
-
Those last two articles look promising for rebuilding the bcd and MBR.
-
I am doing a reinstall now. Pretty much exhausted other options, and it was having issues for a while where I had to repeatedly use a boot disk to repair anyways.
Thanks though for your help and efforts to come up with a repair.
Any suggestions on which of the programs you have that can be used as good safe tools to tune up Windows in general?
There is so much crap out there, You guys at least seem honest and able to provide solutions that can be helpful if used properly that don't have malaware potential.
I will look at this as a learning process and go from there.
Thanks,
Gary
-
I was hoping those cmds in the last two articles would have negated the need to reinstall - hope you haven't lost too much stuff.
Once you are back up, get into the habit of creating regular system images onto external media and the means to recover from it - that would have negated the need for all of this.
I always create a system image before test running each new version of the repair program.
A system image is also essential to recover from when a HDD goes down and is the only true defence against Ransomware.
When my Win 10 has a problem that a sfc /scannow cannot resolve, I'll perform a repair install which doesn't affect personal stuff or installed programs.
When you have created Win 10 install media, open Windows/File Explorer - This PC - insert the install media and double click on its drive.
This will start the process when using a DVD but will open to its files when using an USB where you would then double click on setup.exe Application.
This takes 3½ - 4hrs on mine.
I don't believe in tune up programs as Windows has its tune up tools.
Win 10 runs its own maintenance program, it has its own defragger and while it has Disk Cleanup, I use the free version of CCleaner to clean out temp files etc. at the end of each session.
https://www.ccleaner.com/ccleaner?source=cpc&gclid=EAIaIQobChMI0qWmhMHo4gIVhLDtCh2AZgDnEAAYASAAEgKs1PD_BwE
In Options/Advanced uncheck the box for Only delete files in Windows Temp older than 24 hours will clean out a lot more and in the latest version, it has an Easy Clean which I find useful.
-
Great, thanks again for the tips. I will take your advice to heart and implement more precautions in future. All my files were still intact on the new install and it was our older second computer, so no real loss. Just have to reinstall some programs. I upgraded from win8, so it always had some issues anyways. Hopefully now it will run better.
Cheers,
Gary
-
A clean install can certainly resolve a lot of problems :)