Skip to main content

No Audio after Cloning HDD to SSD

Thread needs solution

I ran into serious audio problems after cloning a Windows 10 64bit (German) from a HDD to a Crucial SSD of the same size. The laptop has a Realtek audio chip installed. The cloning was performed with no errors. The system boots up normally but it says "no audio device installed". The Realtek device is normally visible in the system control. Driver is up-to-date. All services (Windows Audio with all dependend services) are running normal. The speaker symbol in the taskbar shows a red cross. The audio trouble shooting wizard can't repair or solve the issue. It displays that the audio services are not running and the volume levels are low.

The issues with non-working audio devices after cloning with Acronis are not new but I thought they are solved in the newest version. It is obviously not the case. I spent hours to walk through all the existing approaches throughout the Internet.

Here is my way to restore functionality of the sound:

1. Check if your audio driver is up-to-date, restart the computer
2. Open the CMD (Shell) with administrative privileges (as Administrator)
3. run the command: net localgroup Administrators /add networkservice
> if you run a German system replace Administratoren instead of Administrators
4. run the command: net localgroup Administrators /add localservice
> if you run a German system replace Administratoren instead of Administrators
5. type "exit" and restart the computer

I hope I can ease the rocky path of solution search for one or the other.

0 Users found this helpful

Roland, welcome to these public User Forums.

Thank you for sharing your experience and solution for this 'no audio' issue after cloning.

One question:  Did you perform the clone as per the information below?

Please see KB 56634: Acronis True Image: how to clone a disk - and review the step by step guide given there.

Note: the first section of the above KB document directs laptop users to KB 2931: How to clone a laptop hard drive - and has the following paragraph:

It is recommended to put the new drive in the laptop first, and connect the old drive via USB. Otherwise you will may not be able to boot from the new cloned drive, as Acronis True Image will apply a bootability fix to the new disk and adjust the boot settings of the target drive to boot from USB. If the new disk is inside the laptop, the boot settings will be automatically adjusted to boot from internal disk. As such, hard disk bays cannot be used for target disks. For example, if you have a target hard disk (i.e. the new disk to which you clone, and from which you intend to boot the machine) in a bay, and not physically inside the laptop, the target hard disk will be unbootable after the cloning.

Hello Steve,

thank you for the information. No, I did the clone on a seperate PC. I normally do that in this way and had no troubles in the past. I will adopt the best practice scenario given in the KB when cloning laptop drives. Thank's again for the advice.

Regards
Roland

Roland, thanks for the info!  It sounds like this was cloned "offline" with rescue media.  Probably too late now, but if you grab the offline log and system report, you can check to see if "universal restore" was automatically applied during the cloning process, or not.  This was one of the main issues people were experiencing with cloning in the past, which as "messing up" drivers.

That said, the audio issue has popped up in True Image and Snap Deploy forums a couple of times in the past - usually also as a result from Universal Restore being applied in the process.  I don't know if that is always the scenario where the problem comes out... regardless though, his is the one that has fixed the issue for me in the past

https://forum.acronis.com/forum/acronis-snap-deploy-5/realtek-driver-isssue

Any solutions to these types of issues are always welcome!

 

Hi, none of the solutions above did work for me.

What worked for me:

Go to Run, start regedit and find:

01) HKEY_LOCAL_MACHINE\SYSTEM\controlSet001\Services\HDAudBus

Modify REG_DWORD "Start" and set it to 3

Go back into computer management >>> device manager and uninstall the "high defintion audio controller"

Scan for hardware changes and it should pick up the generic driver and audio should work again.  

Worked like a charm on Windows 8.1 on a Lenovo (Medion) i7 PC.

 

Please include a piece of paper in the box of the SSD crucial drive with the written warning and solution to this stupid problem on it, it costed me the best part of a day...

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 488

Dear Duco de Klonia,
Thank you for sharing your solution.