Microsoft has done a poor job of explaining just exactly what one has to do to first create and image backup and second use the system repair disc you are asked to create to do restores. The problems are almost insurmountable. I am sure others can and do use it without a problem but what follows will show just how difficult it was for me to use.
Here are the problems:
1. I chose to use a USB stick for the backups. The backup process would not notice the stick unless it had the necessary permissions on a folder to allow it to be shared and then make a share for it.
2. Once the backup image was done I thought I had a real way to restore. Wrong! I had a situation that some people are experiencing that made my start button not work and I wanted to restore from the backup I had made. I wanted to do the restore because all of the helpful stuff about getting out of the start button problem did not work. Windows 10 System Repair DIsc was booted and then I went to the restore. It could not find the stick even though its own little operating system could. I spent several days searching on the internet to find a solution for this. The restore apparently wants only certain names and then only in the root of the usb. Unfortunately item number one above makes this impossible. Further, if you drag and drop so that everything is in the root that restore wants you have broken an unwritten rule about leaving things alone in the backup or else restore won't find the image backup. Extra files were created by the image backup that many Google hits said should not be there. Isn't this wonderful?
3. The image process creates .vhdx files for W10 not .vhd. I had purchased Acronis TI 2016 just a few days ago and when I booted their rescue disc it is not capable of using the .vhdx files. It does not even see them.
4. Creating a new userid on the image that had the start button worked and its own start button worked. This was not an option to use all the time for me. Too many things to get right in the new logon.
The solution for me was found in a Google hit that described a way to convert the .vhdx files to .vhd and then Acronis would work. The hit indicated Windows 10 Pro, which is what I have, has a feature that can be turned on called Hyper-V and is used to run virtual operating systems under W10. One could use the Hyper-V Monitor to locate, convert from .vhdx to .vhd and save them somewhere. I was able to accomplish the conversion using Hyper-V. The .vhdx files were on the stick. I put the converted ones on an attached external hd. I used Acronis Rescue Disc, located the .vhd files, chose the correct image based on size, and did the restore. It worked perfectly and my system is back like it was before the start button problem reared its ugly head. I have made a good backup with Acronis now and won't use Windows create a system image again.
Here are the problems:
1. I chose to use a USB stick for the backups. The backup process would not notice the stick unless it had the necessary permissions on a folder to allow it to be shared and then make a share for it.
2. Once the backup image was done I thought I had a real way to restore. Wrong! I had a situation that some people are experiencing that made my start button not work and I wanted to restore from the backup I had made. I wanted to do the restore because all of the helpful stuff about getting out of the start button problem did not work. Windows 10 System Repair DIsc was booted and then I went to the restore. It could not find the stick even though its own little operating system could. I spent several days searching on the internet to find a solution for this. The restore apparently wants only certain names and then only in the root of the usb. Unfortunately item number one above makes this impossible. Further, if you drag and drop so that everything is in the root that restore wants you have broken an unwritten rule about leaving things alone in the backup or else restore won't find the image backup. Extra files were created by the image backup that many Google hits said should not be there. Isn't this wonderful?
3. The image process creates .vhdx files for W10 not .vhd. I had purchased Acronis TI 2016 just a few days ago and when I booted their rescue disc it is not capable of using the .vhdx files. It does not even see them.
4. Creating a new userid on the image that had the start button worked and its own start button worked. This was not an option to use all the time for me. Too many things to get right in the new logon.
The solution for me was found in a Google hit that described a way to convert the .vhdx files to .vhd and then Acronis would work. The hit indicated Windows 10 Pro, which is what I have, has a feature that can be turned on called Hyper-V and is used to run virtual operating systems under W10. One could use the Hyper-V Monitor to locate, convert from .vhdx to .vhd and save them somewhere. I was able to accomplish the conversion using Hyper-V. The .vhdx files were on the stick. I put the converted ones on an attached external hd. I used Acronis Rescue Disc, located the .vhd files, chose the correct image based on size, and did the restore. It worked perfectly and my system is back like it was before the start button problem reared its ugly head. I have made a good backup with Acronis now and won't use Windows create a system image again.