Skip to main content

2018 Rescue Media fail

Thread needs solution

I recently upgraded from True Image 2011 to 2018. I can't seem to get bootable rescue media.

I've tried both easy and advanced choices for ISO, CD, and USB, but nothing works. All I get is a blank screen with a flashing cursor.

The computer boots fine from my old ATIH 2011 boot disk (CD).

I'm running Win 10  v 1709 on a Dell I-580, Intel i3 3.2GHz, 6GB RAM.

My 2009 and 2011  versions worked flawlessly.

Any ideas? I'm getting really frustrated with it.

Thanks.

0 Users found this helpful

Richard, welcome to these User Forums.

The key difference in Rescue Media between your very old 2009/2011 media and the latest 2018 media (apart from obvious OS changes) is in how the media boots.  Your old media is likely to only boot in Legacy mode whereas more recent media will boot in either Legacy or UEFI mode.

The media boot mode should match how your Windows OS boots.  See webpage: BIOS Mode - See if Windows Boot in UEFI or Legacy Mode for information on checking this.

The OS changes with the Rescue Media are a move from defaulting to Linux OS media to using Windows PE/RE - Simple media uses Windows RE versus Advanced using Windows PE but there is also an option to allow creating the older Linux media too.

Thanks for the reply, Steve.

I finally got it to boot after making a disc with the MVP tool. (BTW...this system boots in Legacy Mode)

I still don't understand why none of the boot media I made under True Image would work. I tried every option (except Linux) three times, as USB, DVD, and ISO.

I read something in one of the posts about ATIH using files from the Windows Recovery partition. Is that talking about the EOM recovery patition? I wiped this drive and did a clean install of Win 10, so there's no OEM partition.

 

Richard, you can use reagentc /info  to check the status of the Windows Recovery Environment on your computer.

OK, so I ran Reagentc /info and got the following:

C:\WINDOWS\system32>Reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: 2f740043-e751-11e7-b979-88b1e6a71408
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

Is it not making boot media because there is no recovery image location? This is still making no sense to me.

 

Richard, your RE info looks very similar to that on my computer, including the same shown for the Recovery image location: and I was able to create the Acronis 'Simple' media fine, as well as being able to create the MVP Custom ATIPE media using the WinRE media option.

The TI_Media_Builder log for the Simple media build using WinRE showed the following entries.

2018-02-11T21:27:51:431+00:00 41080 I00000000: GetDisplayInfo succeeded: DPI: 96, scaling: 100%. Monitors: Resolution: 1280x1024, work area: 1280x984, physical DPI: 76. 
2018-02-11T21:27:51:437+00:00 41080 I00000000: EnableHiDpiScaling - use system scaling.
2018-02-11T21:28:37:773+00:00 60916 I00180000: Bootable media type: WinPE-based media with Acronis software
Target media: WIM file
Image location: H:\AcronisBootablePEMedia.wim
2018-02-11T21:28:37:789+00:00 60916 I00180000: Copying source .wim file...
2018-02-11T21:28:43:047+00:00 60916 I00180000: Mounting .wim file...
2018-02-11T21:30:22:596+00:00 60916 I00180000: Updating .wim file contents...
2018-02-11T21:30:39:171+00:00 60916 I00180000: Updating registry...
2018-02-11T21:30:40:373+00:00 60916 I00180000: Updating files...
2018-02-11T21:30:40:476+00:00 60916 I00180000: Updating regional settings...
2018-02-11T21:30:40:476+00:00 60916 I00180000: Installing additional packages...
2018-02-11T21:30:40:476+00:00 60916 I00180000: Updating drivers...
2018-02-11T21:30:40:476+00:00 60916 I00180000: Saving .wim file...
2018-02-11T21:33:05:945+00:00 60916 I00180000: The operation has completed.

If you installed TI 2018 on top of TI 2011 without first uninstalling TI 2011, that may explain the problem. You should now uninstall TI 2018 and run the cleanup tool to clear out all the old files. Then reinstall TI 2018. That should help.