New
#31
Um. Well after I cloned it again, the audio works. I guess we will never find out the solution to the problem. Well then! Thanks for the help, I guess...
If you clone the correct way.... all is still the same. Problems that may occur:
What problems did you have after cloning the second time? Normally none if you boot from new harddisk and detach old disk.
- DISK ID (kind of serial number for disk) of new disk is different. Boot menu points to old old disk. Most clone software handles that problem. Otherwise "start repair" fixes the boot menu.
- Also due to the diskid change... drive letters in registry point to old disk. Good clone software fixes that. Otherwise force the old disk id is not available anymore. Simply detach old disk (temporary from system). Win7 can't find C,D etc on old disk... and because C is not available... it assigns C to the new win7 partition.
- Some clone software clones the diskid as well. So problems above don't occur. But two disks with same diskid... win7 is confused, this is not allowed. Win7 doesn't know what is what! But if you boot from new disk just after cloning.... win7 assigns a new diskid to old disk.
Update driver for each IN ERROR item in System devices
For the 1st time yesterday 07 dec 2019 I got a problem in cloning the system disk in Windows. The same exact problem that "osxdude" and "Thorsen" reported on 06 mar 2013 (posts #1 and #4 on page 1 above). What WORKED IMMEDIATELY AND FULLY for me was:
Google "Windows 7 no more sound after cloning disk", 1st ranked search result:
Cloned SSD Has No Sound - Crucial.com"
that provides a clear, detailed, exact, verified, AND EFFECTIVELY WORKING, step-by-step guidance.
Be sure, in "Control Panel > System devices", to COMPLETELY update the driver for EACH (audio-related OR NOT) device that has a yellow or red exclamation mark (in my case there were 2 named "High Definition Audio Controller", and 2 others not specifically related to audio; yet updating just some of them didn't suffice to recover sound).
The present 4-page thread too was ranked high (#2) whence my updating it despite its 6-year age.
Explanation
It's OK for a start to think, as an explanation for the problem, of the disk ID change. However the Windows authentication process always has been, since its debut in Windows XP IIRC, smart enough to recognize that the system is the same after the user changed the whole motherboard with all its components, the CPU and some other related items; so changing just one disk, be it the system one, should cause no problem. In addition cloning the system disk is an operation mundane enough that handling the disk ID is probably done properly in Windows and all the cloning utilities (in my cases Acronis True Image for Crucial, ATI for Western Digital, Paragon, and maybe EaseUS IIRC).
The drive letter causes obviously no problem in most cases, since the user most often reboots with the new disk in the same place where the old disk had been, hence under the same drive letter (generally C:\).
The cause of the present bug may be in one of the changes introduced by Windows Update, since that problem was apparently rarely heard of until recent years (in my case I never had before 07 dec 2019 any problem in system disk cloning operations under various Windows versions, including a few ones under Windows 7).
None of the suggestions in the 4 pages above will work IMO, the closest to the Crucial WORKING solution being at 1:58 in the video linked in post #14 of 07 mar 2013 by "Kaktussoft": "Update Driver Software" for all devices in "Sound, video and game controllers". This is indeed near, yet different, from the WORKING Crucial solution, which is doing this Update only for the "in error" devices, found NOT primarily in "Sound, video and game controllers" but in "System devices". That same video continues with other possibilities, while warning that they are probably most often NOT working (and they are more complicated). Similar comment for the next video linked, that also addresses all items in "Sound, video and game controllers" instead of only "in error" items in "System devices".
Versailles, Sun 08 Dec 2019 14:20:25 +0100, edited (turning title into link) 14:22:55
Last edited by Michel Merlin; 08 Dec 2019 at 08:22. Reason: turning title into link