mouse don't move
hello,
when I'm booting on my USB key(to make a restauration) my pointer can't move under true image (I'm using the pad of my ASUS zenbook UX305C)
how can I fix it or is there any mean to use true image anyway?
best regards and thanks for any answer
thank you Steve,
my USB rescue media was created...Today!! (this PC is new, it's for my kid, and I want to build a good rescue system for him)
So, how can I do to create the windows PE version and test it?
best regards and thanks for your welcome
You can create the Windows PE rescue media by using the same Rescue Media Builder tool that created the current USB media, but select Windows PE from the drop-down menu, then just follow the prompts for when it tells you that any components are missing. See screen shots to get started.
Note: You will need to download and install the Windows 10 ADK if you don't already have this. This is a large download but you only need to install 2 components from this, Deployment Tools and Windows Preinstalltion Environment (Windows PE). None of the other components in the ADK are required by ATIH.
Alternatively, to keep things simple, if you have a UsB mouse, just connect it. On systems where i have limited USB ports, I often use a USB 3.0 hub to help out. Additionally, using a unifying device (such as a logitech keyboard/mouse combo from a single UsB receiver, works well too). If you don't have the hardware or aren't interested in spending the money, then building WinPE is the way to go.
thanks a lot guys, I'm saved!!
have a good sunday!
I used Acronis 2016 to clone a boot drive from an SSD to an identical SSD. Acronis booted into stand alone mode and cloned the entire drive (4 partitions). When I boot the computer, it seemed to be booting from the clone but I really have no way to be sure. I guess it really doesn't matter since the drives should be identical. Does anyone know which SSD is now the boot drive?
By the way, I did this because I was burned by the Windows 10 Anniversary upgrade which gave me intermittent BSOD's. I spent hours trying to figure out what was wrong and eventually gave up and restored the boot drive from an Acronis backup made before the upgrade. Now since I am not sure I can turn off the Microsoft auto updates, I want a cloned boot drive, just in case.
Tony, welcome to these user forums.
Sorry but you are breaking one of the golden rules for cloning! You should never boot with the source and target drives both connected in your computer system. The two drives now have the same identical disk signature which will confuse Windows.
Please shutdown fully and remove one of the two drives.
Whichever drive you decide to keep in the computer should be connected where your original boot source drive was connected.
See KB document: 56634: Acronis True Image 2016: Cloning Disks for more information on the correct procedure for cloning drives.
The Windows system works fine with both drives active. The non-boot drive is assigned drive letters like J: and K: and can be used like any other disk. But I would like to know which physical disk is which.
I will have to open the box and disconnect one drive and boot. Then disconnect the other drive and do another boot. The BIOS only lists one SSD in the boot setup screen, so I can't swtich the boot drive from the BIOS.
I see nothing in KB56634 about removing the source or target drives after a clone, but I agree that it seems like a good idea.
Thanks for the the response!
This comment can be deleted
Tony, if you click to expand on the section in the KB document for either of the methods shown (Bootable media or from Windows), the final step at point 8. says:
- When the cloning completes, shut down the system and remove one of the hard drives.
or - When the cloning completes, you will be offered to press any key to shut down the computer. Shut down the system and remove one of the hard drives:
Hi Tony,
I have to agree with Steve -better to be safe than sorry. You can keep both drives installed, but you're risking the possibility of a bootloader issue and/or the system booting the wrong drive at some point (possibly when you're not expecting it, which could cause you to be updating data in 2 different drives without knowing it). You can do as you are, but it's not recommended as you may find yourself with a problem down the road as a result. Ideally, a clone is meant to be a safety net in the event the primary drive fails (or if you're migrating to a new drive). Really up to you though, but just know that none of the MVP's will recommend you leave the clone drive connected as you're doing as this has led to systems not booting (both the original and clone). It also gives malware and/or ransomeware access to both drives which could corrupt them at the same time, leaveing you with nothing to fall back on.
Yes, Windows will always assign the other drive a different letter - usually the next available one depnding on what other drives are also connected. The only way you can really telll which one you're booted into is to use diskpart and "list disk" or computer management >>> disk management ... or a third party tool that identifies the drive. If they are different models, then you should be able to tell which one you're booted in, but if they are the same type of drive, it's really the serial # that will give you a clue.
There are third party tools that show the serial numbers of the SSD's but I cannot get Windows to reveal the serials. Disk Management uses tags like Disk1 and Disk2 that probably refer to the SATA port numbers on the motherboard. I was able to boot from either SSD by unplugging its partner. I know I have two good boot drives, so I am happy. I try very hard to avoid storing anything on the boot drive but the OS and apps, so swapping in an emergency should cause no serious loss of data.