Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Tony H

Pages: [1]
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  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. 


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 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.


Hi, Tom:

Thank you for your response.  Before posting I read through several posts involving W10 not booting after using the repair software.  I picked up on your suggestion to run bcdedit |find "0sdevice" to see if it still sees it and gives you a partition letter.  It showed the Windows installation on D.  I selected it and ran SFC /Scannow.  It reported no issues.  I tried to run DISM without success.  Apparently you can run it offline.  I started with this:  DISM /image:C:\ /cleanup-image /revertpendingactions found on another website.  I added "offline" to it which helped but I was not able to properly label the location of the windows file using : \ and / combinations.

I still cannot log in to Safe Mode, even trying the method you suggested by shutting down three times.  I was able to get into the recovery console but when I chose to restart and selected Safe Mode it showed the W10 logo screen momentarily and then went to a black screen, which is what it has been doing previously.

As I mentioned, I have a backup copy from December 2018 that I can restore it needed.  But in the last year I have installed software which takes a considerable amount of time to install so I'd like to regain control of the current installation if possible.

I'll keep looking for a little while and then give up and restore the backup.  If you think of anything else I can do, let me know.



I have used this product for a few years and have found it to be very useful.  However, after recently using it I can no longer boot into Windows 10.  I'm running Windows 10 on a 240GB SSD drive formatted as MBR with only the OS and program files on it.  My second drive is a 3TB WD drive partitioned as GPT.  It contains my user files and W7 and W8 OS partitions.  I used the SSD as the boot drive to control the three OSes using EasyBCD.  I primarily use W7  most of the time to avoid the nagging Windows updates in Windows 10 when I'm doing video and audio editing.  It has worked fine for the last 5 years with no trouble. 

A few days ago when I booted into Windows 10 there was no taskbar search box and it was difficult to navigate between windows.  So I booted into Safe Mode and ran Tweaking Windows Repair overnight.  The next day I discovered that it had hung at Repair #8 for 9 hours.  I stopped it, unchecked all repairs and the re-checked all except the first 8.  Repair #28 also hung for a long time and I stopped it and proceeded on with the rest.  Then I tried to run these two one at a time and they still hung.  So I closed the program and rebooted to no avail.  I cannot boot to Windows in either active or Safe Modes.  It shows the Windows logo and the rotating circle briefly and then reboots to a black window.  I have tried all of the suggested ways to resurrect it to no avail.  That includes Startup Repair, Command line bootrec repairs [fixmbr, fixboot, ScanOs, RebuildBcd], SFC Scannow, Chkdsk.  I also tried Macrium Reflect's Rescue disk boot repair.  I reset the boot menu and I can boot from Windows 7 and 8 but still cannot boot to Windows 10.  I also tried these things with the GPT disk disconnected using only the SSD disk.

Some time ago I had a similar issue on my other desktop which also runs multi-boot.  One drive would not boot.  In my searching I came across a very short sequence of cmd line commands that addressed the bootrec of the specific OS.  It worked great!  I have searched and searched for it again and have not been able to find it.

Does anybody have any ideas on how to resurrect my Windows 10 install.  If all else fails I have a backup image of it but it's over a year old and I would prefer to recover the current installation.


Pages: [1]