Windows 10: Set F11 recovery option in acronis true image 2017 now fails to start

Set F11 recovery option in acronis true image 2017, failed to start, can't remember the error message, something about starting from a floppy, I think. So booted from true image disk and deactvated the F11 option, now I cannot get my PC to boot....





This is the screen I get, I have booted from a Windows 10 USB pen and tried startup repair, but couldn't help.
also tried Wondershare live repair cd, but it couldn't help and one of the options chose a different HDD, with no other choices.....wish to hell I hadn't played with true image.....can some please please help me...I have a laptop if I need to download anything or make a boot disk...
thanks

:)

 

Recover Wizard Windows 7.8,8.1 and 10 Pro

Boy, you sure have been a great help and for sure you have giving me a lot of info. The problem here falls back to where we started. I should be able to create a system image through Windows but that is not happening regardless of what I try.

I guess that I will have to use another hard drive because it is not happening for me here or like you said use a third party like Acronis True Image or Norton's Ghost or if you can recommend another.

According to True Image which I have installed, I need a total of 44GB designated for the recovery image.

or can I use the Acronis partition (F11) to recover from there.

I have all the media pertaining to this computer if it ever failed like

Windows, Office, Motherboard Disk (Drivers) the rest can be downloaded as needed, the problem here is the time consumption to get back to running. As you know, this can take up to 2 hours, specifically if you do a true format of the drive.

Again Thank you.

 

Program cannot send email using smtp, gmail and port 587 and TLS

Henri,

Acronis suggested selecting TLS or SSL before providing the port number, but it didn't work for me. The only thing that worked was switching my SMTP server from gmail to comcast. When I installed True Image 2017, I didn't try the gmail server, so I'm not
sure if the problem is fixed with True Image 2017.

Gary

 

This error message looks like reference to your C: partition (or system reserved partiton, or both) is broken in the BCD registry hive. Either of these partitions have moved, now you have a dangling pointer, Windows loader is unable to find required files, and so your laptop no longer boots.

You can use Emergency Boot Kit to repair references to your partitions in the Windows Registry and, in general, fix this kind of boot problems:

Emergency Boot Kit: Fix boot problems and reassign drive letters

Start Mount and Boot Center from the main menu, make sure that partition which is supposed to be your disk C: is really labeled as disk C:, also make sure that OS is [x]-linked to loader, and finally make sure that loader is called by BIOS.

 

Thanks
just made USB boot from demo...re and finally make sure that loader is called by BIOS.is this part of the disk, or from my bios settings

Said it could not find any HDD with OS





Looked at partitions





Attachment 118956
If if I used paragon HDD manager boot disk, would that help me ?

 

Essential part is on the first screenshot:

"Failed to read from file L:\Windows\System32\config\SYSTEM: Input/output error.
Consider manual recovery from backup copy L:\Windows\System32\config\RegBack\SYSTEM"

L:\Windows\System32\config\SYSTEM is a special system file which contains Windows Registry hive HKEY_LOCAL_MACHINE\SYSTEM. This file contains a bad sector, hence it is not readable. Neither by Windows, nor by Emergency Boot Kit (Mount and Boot Center).

There is a backup copy of this file, which is automatically updated on each Windows reboot. It is stored in the file L:\Windows\System32\config\RegBack\SYSTEM. You need to:

1. Move L:\Windows\System32\config\SYSTEM -> L:\Windows\System32\config\SYSTEM_BAD
2. Move L:\Windows\System32\config\SYSTEM.LOG1 -> L:\Windows\System32\config\SYSTEM_BAD.LOG1
3. Move L:\Windows\System32\config\SYSTEM.LOG2 -> L:\Windows\System32\config\SYSTEM_BAD.LOG2
4. Copy L:\Windows\System32\config\RegBack\SYSTEM -> L:\Windows\System32\config\SYSTEM
5. Copy L:\Windows\System32\config\RegBack\SYSTEM.LOG1 -> L:\Windows\System32\config\SYSTEM.LOG1
6. Copy L:\Windows\System32\config\RegBack\SYSTEM.LOG2 -> L:\Windows\System32\config\SYSTEM.LOG2

Do not delete old SYSTEM hive because bad sector may be assigned to a new file, randomly. It's better to leave it allocated to unused file.

You can copy and move these files in EmBootKit File Manager (requires paid version) or using third party tools.
http://embootkit-v1.prime-expert.com...file_intro.pdf

It's very likely that when you restore SYSTEM hive from backup, Windows will boot normally. Otherwise, continue with EmBootKit Mount and Boot Center.

 

Do i type these symbols in ->.
Just got this from easeus HDD manager

do I use the CMD prompt in windows repair troubleshooting options ?

is there a file manager maybe Linux LIVE CD, where I could move these files around easier, or is that not possible ? Not sure why the partition is 'L'


One other question if the pc makes a backup of this registry file each restart, won't it have overwritten the good backup with a corrupt one, or doesn't it work that way ?


thanks

 

UPDATE
It Worked !!!
ran Linux Mint from a us pen, then performed all the actions you listed, now back to normal, you are my Hero....
Is there anything I need to do now ? If I don't have access to the emergency boot kit, as the demo only lasts so long....how else could I identify the issue.....or is it usually the same reg file and same procedure.....

thanks again, so so so very much

 

OK, I'm glad to see that my advice helped you.

Emergency Boot Kit demo is not time limited, so you can use it to identify similar boot problems in the future.

In general, arrival of bad blocks in your SSD is not a good thing, it may be early indicator of failing device. If this SSD is properly air-cooled and power supply is not overloaded (I've noticed you have many disks), then you probably consider its replacement.

 

Where did it say bad blocks on SSD ?
its only a few months old and not used very much, sits in a bay.....cant do much about that really...have 6 fans, so cooling should be ok....check Sandisk software and reports it's ok !!.

also, you said the registry backup files are recreated each boot, so wouldn't they et overwritten with bad files, on a failed boot...?

thanks

 

Looks a bit healthier now with EBD