cannot create working rescue DVD
I tried to produce a working bootable rescue DVD media for my desktop with a Ryzen3 CPU with software graphics running in the CPU, Windows 10. I haven't been successful though trying the different methods. Either the screen shows vertical stripes only or nothing happens at all after trying to boot from the RW-DVD.
Is there any problem with RW-DVDs? I chose this media, because I expected to get problems, so I would not have to waste DVDs.
Is the any problem with graphics in the CPU for Acronis True Image? No graphic card?
Where should I try to troubleshoot?.
Franz, I would suggest trying the new Rescue Media feature of the MVP Assistant tool for creating your media.
The latest version of the MVP Assistant tool is at the link below.
MVP Assistant - New 2.0 with Rescue Media Builder (New Version 2.1.1)
If you run this on the desktop PC and use the driver analysis feature to ensure that you include any / all drivers needed for the software graphics.
Hi Steven, thanks for the input.
I am using True Image 2021. Since I realized that I am making backups regularly to my NAS without ANY tested and reliably working rescue media (I had just burnt the ISO-Images to DVD and believed it would work as with older versions) I chose a USB-stick as media and could create a booting stick with the MVP assistant.
I ran into two more problems
1. When choosing which backup source should be used "WIN RE" was greyed and "Windows Recovery was not found" announced. Anything I can do about this to be able to try this method also?
2. After booting from the USB-stick (WinPE based?) I could not access the network, i.e. was not able to connect to the backup files in my NAS, not even after waiting very long. Bot a single network device was shown. Also entering the IP-address \\W.X.Y.Z\Volume_1 of my NAS did not work. What can I do to make network devices visible? Does it indicate any problems with network card drivers?
1. When choosing which backup source should be used "WIN RE" was greyed and "Windows Recovery was not found" announced. Anything I can do about this to be able to try this method also?
The Win RE option requires a working, valid Windows Recovery Environment on your PC being used to create the rescue media. To check this, run the following command from an Administrator command prompt or Powershell window:
REAGENTC /INFO
PS D:\powershell> reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 4d60d2e0-12a7-11ed-ae87-dc87f5f8e45f
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.If you see any issues shown in the above output then you can try the further command:
REAGENTC /DISABLE
Then re-enable it again using /ENABLE to see if that resolves the issue.
PS D:\powershell> reagentc /?
Configures the Windows Recovery Environment (Windows RE) and system reset.
REAGENTC.EXE <command> <arguments>
The following commands can be specified:
/info - Displays Windows RE and system reset configuration
information.
/setreimage - Sets the location of the custom Windows RE image.
/enable - Enables Windows RE.
/disable - Disables Windows RE.
/boottore - Configures the system to start Windows RE next time the
system starts up.
/setbootshelllink - Adds an entry to the Reset and Restore page in the boot
menu.
For more information about these commands and their arguments, type
REAGENTC.EXE <command> /?.
Examples:
REAGENTC.EXE /setreimage /?
REAGENTC.EXE /disable /?
REAGENTC.EXE: Operation Successful.For the network access issue, getting the Win RE option working is the first step as this should bring in the needed network card drivers, after which you need to check that you are connected by using a PING command to your NAS.
PING 192.168.0.29 (using your own NAS IP address
PS D:\powershell> ping 192.168.0.29
Pinging 192.168.0.29 with 32 bytes of data:
Reply from 192.168.0.29: bytes=32 time=8ms TTL=64
Reply from 192.168.0.29: bytes=32 time=9ms TTL=64
Reply from 192.168.0.29: bytes=32 time=9ms TTL=64
Reply from 192.168.0.29: bytes=32 time=6ms TTL=64
Ping statistics for 192.168.0.29:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 9ms, Average = 8ms
PS D:\powershell>After confirming that you have network access and can ping the NAS, then you should be able to connect to the NAS, and could use a NET USE command to setup the connection and provide the user credentials.
PS D:\powershell> net use /?
The syntax of this command is:
NET USE
[devicename | *] [\\computername\sharename[\volume] [password | *]]
[/USER:[domainname\]username]
[/USER:[dotted domain name\]username]
[/USER:[username@dotted domain name]
[/SMARTCARD]
[/SAVECRED]
[/REQUIREINTEGRITY]
[/REQUIREPRIVACY]
[/WRITETHROUGH]
[/TRANSPORT:{TCP | QUIC} [/SKIPCERTCHECK]]
[/REQUESTCOMPRESSION:{YES | NO}]
[/GLOBAL]
[[/DELETE] [/GLOBAL]]]
NET USE {devicename | *} [password | *] /HOME
NET USE [/PERSISTENT:{YES | NO}]
PS D:\powershell> net use P: \\192.168.0.29\Backup /user:Acronis
Enter the password for 'Acronis' to connect to '192.168.0.29':
The command completed successfully.
PS D:\powershell> dir P:
Directory: P:\
Mode LastWriteTime Length Name
---- ------------- ------ ----
da--s- 15/07/2021 18:05 #recycle
da---- 10/08/2022 12:57 HP Omen Steve
da---- 27/05/2022 14:44 Test
da---- 14/08/2022 15:37 VMware
PS D:\powershell>