Recovery of entire disk from backup file on SSD fails. Works OK ir backup file is on USB stick. archive

Glad you got it recovered.

Is the SSD in internal drive? When you say it always worked, it that with the same drives? Did you move the backup to the USB drive to get it to work, or was that a different backup?

What is the failure? Do you have the log.

I'd use a checksum tool to compare the checksum of the backup files on the SSD and the USB to see if they match.  The power outage could have impacted the drive in a bad way if it was attached when things went south.

BrunoC wrote:

Glad you got it recovered.

Is the SSD in internal drive? When you say it always worked, it that with the same drives? Did you move the backup to the USB drive to get it to work, or was that a different backup?

What is the failure? Do you have the log.

It always worked with the same drives. Target drive SSD

Source drive (backup TIB) second SSD all drives internal.

I copied the backup TIB file that failed to a USB stick and then the recovery worked.

When the recovery failed it created a ZIP file with a bunch of logs. The ZIP file it too big to upload to this forum.

Bobbo_3C0X1 wrote:

I'd use a checksum tool to compare the checksum of the backup files on the SSD and the USB to see if they match.  The power outage could have impacted the drive in a bad way if it was attached when things went south.

I ran a checksum tool against both files. Checksums are identical.

Oops, I put this in the ATI 2020 forum and I am running ATI 2019.

I guess I can upload the ZIP file that ATI created when it failed.

I wonder if there is disk corruption on the other disk.  I do see that it's trying to do a sector-by-sector recovery:

<event id="3" level="2" module="1" code="504" time="1567637448" message="Pending operation 52 started: 'Clearing disk'." />
    <event id="4" level="2" module="1" code="504" time="1567637448" message="Pending operation 14 started: 'Recovering partition sector by sector'." />
    <event id="5" level="2" module="1" code="504" time="1567637448" message="Pending operation 14 started: 'Recovering partition sector by sector'." />
    <event id="6" level="2" module="1" code="504" time="1567637448" message="Pending operation 14 started: 'Recovering partition sector by sector'." />
    <event id="7" level="2" module="1" code="504" time="1567637557" message="Pending operation 61 started: 'Recovering MBR'." />

You might want to run chkdsk /F /R on both the source and destination disks to be on the safe side.  

Bobbo_3C0X1 wrote:

I wonder if there is disk corruption on the other disk.  I do see that it's trying to do a sector-by-sector recovery:

<event id="3" level="2" module="1" code="504" time="1567637448" message="Pending operation 52 started: 'Clearing disk'." />
    <event id="4" level="2" module="1" code="504" time="1567637448" message="Pending operation 14 started: 'Recovering partition sector by sector'." />
    <event id="5" level="2" module="1" code="504" time="1567637448" message="Pending operation 14 started: 'Recovering partition sector by sector'." />
    <event id="6" level="2" module="1" code="504" time="1567637448" message="Pending operation 14 started: 'Recovering partition sector by sector'." />
    <event id="7" level="2" module="1" code="504" time="1567637557" message="Pending operation 61 started: 'Recovering MBR'." />

You might want to run chkdsk /F /R on both the source and destination disks to be on the safe side.  

 

I ran CHKDSK on both SSDs and they are clean

Code Warrior, 

I don't have any more ideas.  The last option would be to create a new backup job (use a unique name) and back up with it instead.  Then see if the behavior is the same (sector by sector - large backup), or better (expected file size).

If it turns out better, abandon the current job and stick with the new one.

Bobbo_3C0X1 wrote:

Code Warrior, 

I don't have any more ideas.  The last option would be to create a new backup job (use a unique name) and back up with it instead.  Then see if the behavior is the same (sector by sector - large backup), or better (expected file size).

If it turns out better, abandon the current job and stick with the new one.

I tried that, same failure. I am in deep doodoo because only one backup file on the USB stick works, newer ones all fail. So I don't have a PC that is getting backup up daily.

Do you have 2019 to compare with still?  Maybe it's not your SSD, but 2020 that is the problem?  If you have 2019, and it works, I'd stick with it for now.

I can't back up one of my PC's with 2020 at all.  It backups up (not sector by sector), but at the end, it always fails (with the rescue media - I didn't bother to upgrade to 2020 on it yet because of this issue).

Bobbo_3C0X1 wrote:

Do you have 2019 to compare with still?  Maybe it's not your SSD, but 2020 that is the problem?  If you have 2019, and it works, I'd stick with it for now.

I can't back up one of my PC's with 2020 at all.  It backups up (not sector by sector), but at the end, it always fails (with the rescue media - I didn't bother to upgrade to 2020 on it yet because of this issue).

 

I am using ATI 2019 I put this in the 2020 forum by mistake. 

Is there any chance that the SSD where the backupd are stored has been accidentally included in the backup? Or that the SSD where the backup is stored is accidentally selected as the target for restoration (since the rescue media can change the drive letters compared with the ones shown by Windows)?

Pat L wrote:

Is there any chance that the SSD where the backupd are stored has been accidentally included in the backup? Or that the SSD where the backup is stored is accidentally selected as the target for restoration (since the rescue media can change the drive letters compared with the ones shown by Windows)?

 

No, I have been using ATI for many years and it has worked with no problems. I am using the same process to recover one SSD (the Windows disk) that has worked fine until the Windows Update did something to the drive. I have one backup TIB file that was created before the Windows Update and it recovers OK. But all backups since the Windows Update problem fail to recover. The recovery failure is when it is trying to recover the MBR.  

Please make sure that when you select the destination disk you select the right SSD. Maybe the Windows update and hard reboot changed something that makes Acronis display disk letters in another way and the C:\ that Acronis is showing you is in fact now the SSD where you store your backups (that may have the letter D:\ in windows). It happened to me recently with ATI 2020. Use disk size of volume names to double check.

If user error is ruled out, there has been a change in the hardware or the boot layout that throws off the recovery.

Was there any change in the way the computer boots (from MBR/Bios to GPT/UEFI) for example?

Does your BIOS indicates that the SSD is locked by any chance?

Is the EFI system partition and the boot file still on the same disk as before? A hard reboot might have forced Windows to try to repair the startup and made some changes in which disk contains the boot information.

Pat L wrote:

Please make sure that when you select the destination disk you select the right SSD. Maybe the Windows update and hard reboot changed something that makes Acronis display disk letters in another way and the C:\ that Acronis is showing you is in fact now the SSD where you store your backups (that may have the letter D:\ in windows). It happened to me recently with ATI 2020. Use disk size of volume names to double check.

If user error is ruled out, there has been a change in the hardware or the boot layout that throws off the recovery.

Was there any change in the way the computer boots (from MBR/Bios to GPT/UEFI) for example?

Does your BIOS indicates that the SSD is locked by any chance?

Is the EFI system partition and the boot file still on the same disk as before? A hard reboot might have forced Windows to try to repair the startup and made some changes in which disk contains the boot information.

 

There is no user error, I have recovered full disk images many times over the years I have been using ATI since ATI 2011.  

Disk screwed up by Windows 10 update failure. I have one ATI backup TIB file (disk image) that can be recovered. All backup TIB files created after the windows update failure fail to recover, failing during the recover MBR phase.

Here is the disk layout
*.                    128MB  128MB used
C:recovery    499MB  11MB used
*. (FAT32)      100MB  35MB used
HD_C             230GB  55GB used    

A work-a-round here could be to install Windows from scratch - just do the very basics to get the OS installed.  Then, do a partition-only recovery of the OS partition (C: drive) from one of the other backups.

Really not sure if it's an issue with the recovery, or something from the result of the bad upgrade that messed things up.  However, if it's just the bootloader that's failing, this might be a quick way to get around the boot issues and still have usable backups to recover.

One other thought - it sounds like you've recovered a lot so you probably already checked this, but to be sure...

When you are booting the rescue media, did you make sure to boot it in the correct method as the original OS was installed (UEFI or Legacy/MBR)?  Or, any chance that at one point it was legacy, you restored as UEFI/GPT and the backups you are using are now legacy still?  It may need a modification of the bios if there was such a change.  Whenever UEFI is restored, you may need to go into the bios and pick the boot priority again - making sure to select Windows Boot Manager instead of the physical disk.

If none of that is the issue, of if you try it anyway and it doesn't work, then try the Windows 10 install and just the C: drive partition recovery after that (making sure the rescue media is booted correctly for the OS recovery).

Before reinstalling Windows, we could make sure that the backup that you have is actually a good one. If we go through this and it fails, you will have to reinstall Windows.

- we will use a good backup that is on the USB drive

- disconnect any SATA disk except the system drive

- boot the computer in pre-windows environment and select add new disk in ATI. Direct this at your system drive. This will completely erase the disk and reinitialize.

- restore the backup,

- boot the computer and verify that your system is OK,

- shutdown the computer and reinstall the other SATA disk(s)

- create a new backup task, create a new backup to your favorite destination.

- you can then try a new restore to verify whether we solved the problem.

Pat L wrote:

Before reinstalling Windows, we could make sure that the backup that you have is actually a good one. If we go through this and it fails, you will have to reinstall Windows.

- we will use a good backup that is on the USB drive

- disconnect any SATA disk except the system drive

- boot the computer in pre-windows environment and select add new disk in ATI. Direct this at your system drive. This will completely erase the disk and reinitialize.

- restore the backup,

- boot the computer and verify that your system is OK,

- shutdown the computer and reinstall the other SATA disk(s)

- create a new backup task, create a new backup to your favorite destination.

- you can then try a new restore to verify whether we solved the problem.

I don't know what you mean by boot in pre-windows

I don't know what you mean by boot in pre-windows

It means to boot from the Acronis Rescue Media so that you are working outside of the Windows OS.

Pat L wrote:

Before reinstalling Windows, we could make sure that the backup that you have is actually a good one. If we go through this and it fails, you will have to reinstall Windows.

- we will use a good backup that is on the USB drive

- disconnect any SATA disk except the system drive

- boot the computer in pre-windows environment and select add new disk in ATI. Direct this at your system drive. This will completely erase the disk and reinitialize.

- restore the backup,

- boot the computer and verify that your system is OK,

- shutdown the computer and reinstall the other SATA disk(s)

- create a new backup task, create a new backup to your favorite destination.

- you can then try a new restore to verify whether we solved the problem.

That fails the same way. I guess I am toast. I am not sure that Windows 10 can be installed on this drive.

I had a look at your ZIP file I found a UEFI text file that reads as follows:

Boot variables are allowed on this system

Meaning that your system is capable of booting either UEFI or Legacy or Both

***

Could not obtain Boot Entries Enumerator, UEFI is not enabledCould not obtain Boot Order, UEFI is not enabled

This would seeming indicate that your PC bios does not have UEFI boot enabled thus no boot entries can be obtained meaning the disk will not boot or more specifically Windows Boot Manager cannot boot.

Start your PC and enter the bios, go to the Advanced settings and look for the Boot tab, Select the Boot tab and make sure that UEFI is the selected boot mode.

If your boot mode is incorrect for the backup you are recovering then this could cause a failure.  If it were me I would set the bios to boot UEFI only, Save and exit.  Then boot to the recovery media again and attempt to recover your latest backup. 

If that fails as before then I would attempt it one more time except this time I would not select the Track0 MBR for recovery.  Select all other listed partitions but NOT the MBR.

If that fails you are probably stuck with doing a clean install of Windows.  Bobbo's outline of how to do that is sound and could be followed.

Enchantech wrote:

I had a look at your ZIP file I found a UEFI text file that reads as follows:

Boot variables are allowed on this system

Meaning that your system is capable of booting either UEFI or Legacy or Both

***

Could not obtain Boot Entries Enumerator, UEFI is not enabledCould not obtain Boot Order, UEFI is not enabled

This would seeming indicate that your PC bios does not have UEFI boot enabled thus no boot entries can be obtained meaning the disk will not boot or more specifically Windows Boot Manager cannot boot.

Start your PC and enter the bios, go to the Advanced settings and look for the Boot tab, Select the Boot tab and make sure that UEFI is the selected boot mode.

If your boot mode is incorrect for the backup you are recovering then this could cause a failure.  If it were me I would set the bios to boot UEFI only, Save and exit.  Then boot to the recovery media again and attempt to recover your latest backup. 

If that fails as before then I would attempt it one more time except this time I would not select the Track0 MBR for recovery.  Select all other listed partitions but NOT the MBR.

If that fails you are probably stuck with doing a clean install of Windows.  Bobbo's outline of how to do that is sound and could be followed.

I have a Gigabyte MOBO. There is no selected boot mode. There are two settings Storage Boot Option Control = UEFI and Other PCI Devices = UEFI

When I select the device to boot from, The Windows boot is the Windows Boot Manager, no mention of UEFI but I am sure it boots up in UEFI. When I boot the ATI rescue USB, I have the choice of UEFI or not and I select UEFI. 

I tried to recover a backup and not select Track 0, but the next screen is one I have not seen before and I did not understand what It was asking me so I quit.

Code Warrior wrote:

Pat L wrote:

[...]

That fails the same way. I guess I am toast. I am not sure that Windows 10 can be installed on this drive.

What do you mean? I thought that a backup restored from the USB drive was working while the same backup restored from the SSD was not working?

Could you clarify when you say it fails?

Were you able to restore the backup completely using the backup on the USB disk?

Were you able to boot the computer on the restored disk with no other disk attached?

I copied the backup TIB file that failed to a USB stick and then the recovery worked.

When the recovery failed it created a ZIP file with a bunch of logs. The ZIP file it too big to upload to this forum.

Thu, 09/05/2019 - 06:00

I thought it restored from the USB too? 

Pat L wrote:

Code Warrior wrote:

Pat L wrote:

[...]

That fails the same way. I guess I am toast. I am not sure that Windows 10 can be installed on this drive.

What do you mean? I thought that a backup restored from the USB drive was working while the same backup restored from the SSD was not working?

Could you clarify when you say it fails?

Were you able to restore the backup completely using the backup on the USB disk?

Were you able to boot the computer on the restored disk with no other disk attached?

I did all the steps you said, the good backup on the USB recovered just like always,

I booted up windows ,created a new backup scheme and ran the backup.

Wheh I tried to recover this new backup I got the same failure during the recover MBR phase.

No error message, ATI GUI goes away back to the command prompt and the error log files are created.

The working disk image has a Windows EFI partition, the failing does not have one.

What model Gigabyte mobo do you have? 

You are saying that there are only 2 settings for boot options, are you in the Advanced settings of the bios or do you know?

Your last statement tells me that the failing restoration, not having an EFI partition, is exactly why it will not boot because the EFI partition is where the boot files for a UEFI booted machine are located.  With your boot order set as UEFI then Windows Boot Manager is not able to locate the boot files.

Along the lines of Enchantech, I am starting suspecting that there is some boot configuration or system related information on the other SSD disk. On my computer, I have seen Windows udpate put files on both my SSDs. If the updated failed, there is maybe some remnant on the wrong disk or something. For example in this case, maybe when you backup the system disk, you backup everything you need, but some of it is physically located on the SSD B where you store the backups. Then when SSD B is in the system and used for the source of the backup, and you try to restore from it, ATI get thrown off because it would have to restore something to B it draws the backup data from. Whereas when the archive file is on the USB, the problem doesn't happen, the data gets restored on A, and the linking to the information on B is restored when Windows boot again.

More sophisticated users could help you investigate your boot configuration files to see what is going on.

Personnaly, I don't know how to deal with the boot files themselves, so I would try to completely ATA secure erase both SSDs (or use the clean command of DISKPART in a Microsoft boot disk) to make sure they are blank, unpartitioned, before I restore the USB backup on SSD A alone in the system and again make sure the system boots correctly to that SSD. Only then reconnect the cleaned SSD B and try again.

Other than logical issues, it would have to be a hardware issue that would make B unviable for storing and restoring a backup file.

Bobbo_3C0X1 wrote:

One other thought - it sounds like you've recovered a lot so you probably already checked this, but to be sure...

When you are booting the rescue media, did you make sure to boot it in the correct method as the original OS was installed (UEFI or Legacy/MBR)?  Or, any chance that at one point it was legacy, you restored as UEFI/GPT and the backups you are using are now legacy still?  It may need a modification of the bios if there was such a change.  Whenever UEFI is restored, you may need to go into the bios and pick the boot priority again - making sure to select Windows Boot Manager instead of the physical disk.

If none of that is the issue, of if you try it anyway and it doesn't work, then try the Windows 10 install and just the C: drive partition recovery after that (making sure the rescue media is booted correctly for the OS recovery).

did you try this?  

Enchantech wrote:

What model Gigabyte mobo do you have? 

You are saying that there are only 2 settings for boot options, are you in the Advanced settings of the bios or do you know?

Your last statement tells me that the failing restoration, not having an EFI partition, is exactly why it will not boot because the EFI partition is where the boot files for a UEFI booted machine are located.  With your boot order set as UEFI then Windows Boot Manager is not able to locate the boot files.

The MOBO is Gigabyte B360M DS3H

The machine is very basic. Two SSDs first (256 GB NVME) is for windows 10 second (512 GB Crucial) is for backups.

The ATI backups start at 3:00 AM and  retain 6 backups.

I tried a windows install and it fails also. No error message, just a popup dialog that says Windows Failed. 

It looks like your SSD(s) is  or are locked. Is there any interface in the BIOS to ATA Secure Erase the SSDs? or to check their status?

Pat L wrote:

It looks like your SSD(s) is  or are locked. Is there any interface in the BIOS to ATA Secure Erase the SSDs? or to check their status?

I looked and did not find anything like that in the BIOS.

Seeing as the Windows installer also fails to boot...

After the install, go into the bios and verify the boot order to make sure windows boot manager is first priority, save and then reboot.

2nd, do a cold boot (press power button and hold for 20 seconds before releasing) this may help.

If not, let the boot fail 3 times and on the 4th time you should be given an option to safeboot (f8). Try that. If it boots in safe mode, it will unlock the disc and should boot normally after that.

The lock occurs in Windows. It's usually due to a hibernation file on disk from having fastboot enabled. Fastboot acts like it is shutting down, but is really just hibernating. I have seen locked disks (my own included) after recovering too. The fix is to safeboot (usually).

Code,

Are you seeing an error the the disk is locked? 

What I would recommend is the following:

1. Boot your PC using the USB disk you created.  I might be mistaken but I think this USB disk is in fact a Survival Kit drive.
2. In any case, after the TI app starts close the TI app window and you will see a Command prompt window.  Press the space bar to activate the cursor in the command prompt window.
3. The command prompt should read as follows: X:\Windows\System32> followed by a flashing cursor.
4. Type: C: then press Enter.  Your cursor should now read: C:\>
5. Type sfc /scannow then press Enter
6. A scan of Windows system files will now run.  Any corrupted files should be repaired.
7. Once that completes you should see a Verification 100% complete message.
8. If a message appears that says "Windows Resource Protection could not perform the requested operation." Then type the following at the command prompt: chkdsk /b/x  This will run NTFS filesystem check.
9. If the sfc scannow check produce now errors and fixed no files then the following commands should be run: bootrec /RebuildBcd  press Enter.  Now at the prompt type bootrec /FixMbr  press Enter.  Now at the prompt type bootrec /FixBoot  press Enter.

To exit the command prompt and end your session at the prompt type wpeutil  shutdown.  Your PC will shutdown and you can remove/disconnect your USB drive and attempt to boot your PC again.  Hopefully the steps taken above will have corrected the errors on your disk and it will boot.

If this proves unsuccessful then your last step would be to try to boot the machine into safe mode however I have little faith in that as UEFI needs to be able to find Windows to boot Safe mode and right now I do not think it can.

I will try the above steps. I have run sfc /scannow and it is clean but I will try again.

To eliminate the possibility of SSD B being the problem, I unplugged it, created a new backup scheme and did a backup to a USB stick. The recovery of this file had the same failure: Restoring the MBR

Running the SFC from a booted media rather than from a Windows command prompt will yield different results.  If your drive is simply locked then the check may run but the verification will fail.  Running the chkdsk command as outlined will perform all scans and fixes on the disk including cluster repair.  The bootrec commands can only be run from boot media and are your best bet in fixing the boot code.

Can you post a screenshot of the partitions of SSDA and SSDB?

Pat L wrote:

Can you post a screenshot of the partitions of SSDA and SSDB?

Do you want the SSDA partitions after a good recovery or after a failing recovery ? 

Enchantech wrote:

Code,

Are you seeing an error the the disk is locked? 

What I would recommend is the following:

1. Boot your PC using the USB disk you created.  I might be mistaken but I think this USB disk is in fact a Survival Kit drive.
2. In any case, after the TI app starts close the TI app window and you will see a Command prompt window.  Press the space bar to activate the cursor in the command prompt window.
3. The command prompt should read as follows: X:\Windows\System32> followed by a flashing cursor.
4. Type: C: then press Enter.  Your cursor should now read: C:\>
5. Type sfc /scannow then press Enter
6. A scan of Windows system files will now run.  Any corrupted files should be repaired.
7. Once that completes you should see a Verification 100% complete message.
8. If a message appears that says "Windows Resource Protection could not perform the requested operation." Then type the following at the command prompt: chkdsk /b/x  This will run NTFS filesystem check.
9. If the sfc scannow check produce now errors and fixed no files then the following commands should be run: bootrec /RebuildBcd  press Enter.  Now at the prompt type bootrec /FixMbr  press Enter.  Now at the prompt type bootrec /FixBoot  press Enter.

To exit the command prompt and end your session at the prompt type wpeutil  shutdown.  Your PC will shutdown and you can remove/disconnect your USB drive and attempt to boot your PC again.  Hopefully the steps taken above will have corrected the errors on your disk and it will boot.

If this proves unsuccessful then your last step would be to try to boot the machine into safe mode however I have little faith in that as UEFI needs to be able to find Windows to boot Safe mode and right now I do not think it can.

 

Step 9

bootrec /RebuildBCd Got msg Add Installation to boot list, I entered Y Got msg The System cannot find the path

bootrec /FixMbr

bootred /Fixboot Got msg Access is Denied

Pat L wrote:

Can you post a screenshot of the partitions of SSDA and SSDB?

 Not geing in the Windows environment, The only way I know how to take screen shot is with a camera

The screenshots are poor but you can see the partitions. Both good recovery and failed recovery look the same

Code,

Using a Windows 10 recovery disk follow the instructions in the LINK below:

LINK

From all indications your UEFI boot files contain errors.  The LINK provides the steps to rebuild the BCD which contain the boot entries for Windows and update the UEFI firmware.

EDIT:

I notice in your screenshots that your Windows Partition is assigned the letter D: and your Recovery partition is assigned letter C:

Please disregard the above instruction for now and let's deal with this issue first.

Code Warrior wrote:

Step 9

bootrec /RebuildBCd Got msg Add Installation to boot list, I entered Y Got msg The System cannot find the path

bootrec /FixMbr

bootred /Fixboot Got msg Access is Denied

Look at this post about the Access is Denied situation

https://www.partitionwizard.com/clone-disk/bootrec-fixboot-access-is-de…

Enchantech wrote:

Code,

Using a Windows 10 recovery disk follow the instructions in the LINK below:

LINK

From all indications your UEFI boot files contain errors.  The LINK provides the steps to rebuild the BCD which contain the boot entries for Windows and update the UEFI firmware.

 

EDIT:

I notice in your screenshots that your Windows Partition is assigned the letter D: and your Recovery partition is assigned letter C:

Please disregard the above instruction for now and let's deal with this issue first.

I went to LINK and followed the instructions. The  bootrec /fixboot got access denied.

Just for FUN I kept going with the instructions and YIPPEE the recovered SSD booted Windows.

Ran backup to get a new backup file, booted ATI did a recovery and the SSD booted up Windows again.

I am confident that I can now trust my daily backups. A 1,000 thanks for all the help I got here in this forum.

I do have one more problem. When I recovered to my NVME SSD it fails to boot giving Windows BSOD saying

Inaccessible boot device. I am in no hurry to get this fixed, I can run just fine with a regular SSD.     

Enchantech wrote:

Code,

Using a Windows 10 recovery disk follow the instructions in the LINK below:

LINK

From all indications your UEFI boot files contain errors.  The LINK provides the steps to rebuild the BCD which contain the boot entries for Windows and update the UEFI firmware.

 

EDIT:

I notice in your screenshots that your Windows Partition is assigned the letter D: and your Recovery partition is assigned letter C:

Please disregard the above instruction for now and let's deal with this issue first.

I went to LINK and followed the instructions and when entered bootrec /fixboot I got Access is Denied.
Just for FUN, I kept on going with the instructions and when done the Recovery worked !  
I booted up Windows, ran backup to get a new backup file, booted up ATI and the Recovery worked again.
I am now confident I can trust my daily backups.
I still have one problem, all the above was on a regular SSD. When I recover to an NVME SSD I get a Windows BSOD that states Inaccessible boot device. I tried cloning my SSD to the NVME SSD and got the same error when booting up Windows.
I can live with the regular SSD while I take a break from this.
A 1,000 thanks to all who helped me in this forum.

I went to LINK and followed the instructions and when entered bootrec /fixboot I got Access is Denied.
Just for FUN, I kept on going with the instructions and when done the Recovery worked !  
I booted up Windows, ran backup to get a new backup file, booted up ATI and the Recovery worked again.
I am now confident I can trust my daily backups.
I still have one problem, all the above was on a regular SSD. When I recover to an NVME SSD I get a Windows BSOD that states Inaccessible boot device. I tried cloning my SSD to the NVME SSD and got the same error when booting up Windows.
I can live with the regular SSD while I take a break from this.
A 1,000 thanks to all who helped me in this forum.

Code Warrior. Good job!

As for the next step, are you making sure to remove the source drive after the clone and then update your boot manager again? Was the clone after the fix, or before?

Keep in mind, a clone is for exact same hardware type. SATA and PCIe NVME are different. Windows 10 handles this well, but you may need to update bios settings to accommodate the hardware change. And don't boot with 2 drives installed internally that have been cloned, even if they are different connector types. This will cause trouble for sure.

Sometimes, you may need to cold boot the machine after cloning, and using the new PCIe NVMe drive, in addition to all the other steps. Sometimes, you may need to unlock the disk after letting it fail to boot 3 times and then using F8 for safeboot when given the opportunity.

And if this is not Windows 10, but instead, windows 7, you have more prep work to do too because of Win7 limitations for booting PCIe NVME drives.

Bobbo_3C0X1 wrote:

Code Warrior. Good job!

As for the next step, are you making sure to remove the source drive after the clone and then update your boot manager again? Was the clone after the fix, or before?

Keep in mind, a clone is for exact same hardware type. SATA and PCIe NVME are different. Windows 10 handles this well, but you may need to update bios settings to accommodate the hardware change. And don't boot with 2 drives installed internally that have been cloned, even if they are different connector types. This will cause trouble for sure.

Sometimes, you may need to cold boot the machine after cloning, and using the new PCIe NVMe drive, in addition to all the other steps. Sometimes, you may need to unlock the disk after letting it fail to boot 3 times and then using F8 for safeboot when given the opportunity.

And if this is not Windows 10, but instead, windows 7, you have more prep work to do too because of Win7 limitations for booting PCIe NVME drives.

 The PC is Windows 10 and normally uses a 256 GB NVME M.2 as the Windows drive.
I did all the ATI Recovery troubleshooting on a regular SSD with the NVME removed because I wanted to make sure I had a working PC. (It is my wife,s PC and I would be in big trouble if I lost her files).

The NVME makes the PC stupid fast but a working PC is better than a fast one that fails.

Roger that!  I have had 2 Gigabyte boards in a row too.  My old one was a pain in the butt and often required me to re-flash the bios (same exact version) to truly force it to pick up applied changes after switching from SSD PCIe NVME and vice-versa.  I was pulling my hair out at times with that one, but eventually figured out what worked best.  That was an older Gigabyte GA-77X-UD3H.  

After getting a little frustrated with that board (thinking that both the dual bios had failed since I couldn't boot anything on it at one time, but got around it by resetting CMOS and removing battery and power for 24-hours - shorter periods didn't help!)  I upgraded that a couple years ago to a Gigabyte GA-Z170X-Gaming 3 and initially was concerned with similar behavior, but Gigabyte started streamlining the firmware across most systems and a couple updates later, it was very stable and easy to migrate drives and has been good ever since.  

I see that your system (Gigabyte B360M DS3H) has bios F15 as the most current - are you running the latest?

F15

6.70 MB

2019/07/08

Asia China America Europe

1. Update CPU Microcode to address a potential security vulnerability in CPUs, see more: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00233.html