The issue has been fixed in build 6055, please update to the latest build.

This article applies to:

• Acronis True Image 2015

Symptoms

Keyboard or mouse is not detected in Acronis True Image 2015 bootable media on some hardware.

Cause

This is a known issue.

Solution

The issue has been fixed in build 6055, please update the product.

There are three workarounds for this issue:

1. Use WinPE based bootable media.

2. Use force_modules=usbhid kernel parameter manually:

• Boot from True Image 2015 media; when you see Acronis True Image boot menu click F11. You will see a text box with "quiet":
  
• Add to the text box: "force_modules=usbhid" after a space without quotes:
  
• Press OK.
• Choose to load Acronis True Image.

This workaround does not apply to Surface Pro2 devices where Touch Cover may fail to work.

3. Automate loading force_modules=usbhid parameter by recreating boot media the following way:

• Go to Tools -> Rescue Media Builder -> select Acronis bootable rescue media.
• On the next screen, where you choose media destination, click on Startup parameters:
  
• In the "Startup options" type in "force_modules=usbhid" (without quotes):
  
• Choose the destination and create new bootable media.

This workaround does not apply to Surface Pro2 devices where Touch Cover may fail to work.

More information

The nearest hotfix will have an updated version of media with the fix for initialization of 'usbhid' module responsible for mouse/keyboard detection. The root cause is related to resolving incorrectly dependencies during the module initialization (due to some hardware specifics), this leads to ‘usbhid’ module failing to load under some conditions. The hotfix will change the dependency-checking algorithm in the initialization scripts to address this issue.

See also Acronis True Image 2015.