Main Forum > General Computer Support

Windows 10 won't reboot after running Tweaking in Safe Mode

<< < (2/2)

Boggin:
I've never used this system but it looks useful as something else to try - https://win10.guru/dart-10-diagnostic-and-recovery-toolset-10/

Tony H:
Hi, Tom:

Success at last!  Windows 10 is working again!

I first tried your suggestion to run Kapersky's Rescue disk.  It didn't help.  After trying several other things I was finally resigned to restoring my Windows 10 image from 2017 and then doing an inplace upgrade to version 1807.

As I was making final preparations to do so I backed up my personal files from W10 and was considering backing up the Program files.  As I looked down the list of folders in the root directory I came across one just below Program Data labeled "RegBackup."  It had four folders, three from 2018 and one from 4/23/2019.  I opened the last one and discovered what appeared to be a Registry backup for the last time I ran Windows Repair.  It had 3 text files with one labeled log_backup.  It had Tweaking.com listed at the bottom with a reference to the first of the 2018 backups and containing the location of the .DAT file for that backup.  It also had a file labeled dos_restore.cmd.

I thought this may be what I was looking for.  I had come to the conclusion that the registry file may have become corrupted when I stopped the two repairs because of the length of time they ran.  I had created a new W10 installation disk a couple of days ago.  The one I had was from 3 years ago when I upgraded to W10.  I thought that might explain why it couldn't repair my installation which was more current.  So I rebooted to it and went to the command prompt.  I navigated to the directory where the registry updates were and into the one from 4/23/2019.  I ran the dos_restore.cmd and rebooted.  Windows 10 opened without any further problems.

I quickly ran full backups of W10 with both Acronis and Macrium.  I'm not taking any chances.  My next step will run the "in-place" upgrade to Windows 10 version 1807.

This method will probably work for others who find themselves in this situation.

One more thing . . .

I found the method I was looking for in a text message I created.  Here it is:

Boot with Windows installation DVD, 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)


I have found that this works when the bootrec commands do not.

Tony

Boggin:
That's good news and glad you were able to get back up, but I was wondering how you were able to access your files when Win 10 wouldn't boot.

Tony H:
Hi, Tom:

I was able to access my files from the command prompt using the W10 installation disk repair option.  You can go anywhere you want to and can even copy files to an external drive if you wish.  It's not as easy as being online and just clicking away.  You have to navigate through the directories using DOS commands.  With my GPT drive disconnected and only my SSD drive with W10 it was relatively easy,  At the D prompt I typed DIR and immediately saw "RegBackup" in the list.  The I did CD \RegBackup and saw the five entries containing registry backups made by Tweaking.com.  I just selected the most current one dated 4/23/2019 and opened it and ran the restore command.

If you're asking how I could see my files with W10 not booting it is becauae I'm running a triple boot system with W10, W8 and W7.  The other two OSes are on the GPT drive but boot off of the SSD drive which is formatted as MBR.  When one isn't booting I can still use the other two.  Sometimes I have to reset the BCD. 

Tony

Boggin:
Okay - Thanks.

Navigation

[0] Message Index

[*] Previous page

Go to full version