Cloning hdd to ssd

Please run the following command to check another key in the registry.

Code: 
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching" /s > "%userprofile%\desktop\REG-exp4.txt"
 
Hi,

1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try to installing the driver for the SSD just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
 
Hi,

I first removed the Toshiba bics ssd from device manager.
Run procmon and immediately searched for new device from device manager.
After ssd is in other devices again, stopped procmon capture and saved the result as logfile1.pml
Then cleared procmon and started capture again.
Tried to search for updated drivers for ssd , after windows update screen came stopped procmon and saved the result as logfile2.pml
Compressed both files with 7z and with password in next message.
I hope this helps.
You can download it from following link.
Download logs.7z (8.03 MB) now. Fast and easy at workupload.com
 
Hi,

Please run the following command for a export of the DriverSearching key.
Code: 
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverConfiguration" /s > "%userprofile%\desktop\DriverConfiguration.txt"
 
Last edited:
Hi,

Please run the following command in a elevated command prompt.

Code: 
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching /v DriverUpdateWizardWuSearchEnabled /t REG_DWORD /d 0x1 /f

Reboot the system and try to search for drivers for the SSD. If it fails run it again with Process Monitor.
 
Hi,

Still the same, please find the logfile.7z attached, the password is same as previous one.
 

Attachments

I think I'd have done a clean install to the new drive, at least as a test the OS would work at all by now, & only proceeded trying to clone after proving it would, & deciding that sorting this out was less effort than extracting personal data from a backup / image would be...

Sometimes Nuke & Pave is the sensible option, especially if you actually have an image you can revert to if it proves either too difficult or impossible.

Just saying.
 
I agree with @Bearded Blunder that a clean install is the best option to fix this issue. After fixing the missing policy setting the problem is still there. It looks like that there is also something very wrong with some hardware profiles on this system.
 
I had installed a clean windows to the ssd , the OS sees the drive like a normal drive in that OS. So hardware is ok with a new clean windows.
I say cloning is meaningless when the OS in hdd is broken.
The OS in the hdd should be fixed to clone it.
Maybe extracting and importing some registry hardware keys from new installed windows on the ssd, would make the current OS to see the ssd drive as it should be...
 
Sometimes fixing boot driver / registry / or HAL issues is plain more work than simply re-installing missing software & extracting personal data from a backup / image.

I'm not saying you have to as long as someone is willing to help you "fix" things to "clone, I'm just suggesting you may already have spent more effort on this than "Nuke & Pave" would have been, with potentially as much effort or more still to be expended.

Given a fresh install worked previously, it's worth consideration, unless you have totally unobtanium software installed that not even the Wayback Machine will yield installers for.
 
burzek said:
Maybe extracting and importing some registry hardware keys from new installed windows on the ssd, would make the current OS to see the ssd drive as it should be...
Click to expand...
The trace of Process Monitor listed the following missing keys, you can try to add them manually to see if it will work? But no guarantee from my side... So therefore the spoiler..

Missing keys from the procmon log.
Code: 
12:58:59.8765341 PM    mmc.exe    6148    RegOpenKey    HKLM\System\CurrentControlSet\Enum\SCSI\Disk&Ven_Toshiba&Prod_Bics\4&73b0e52&0&010000\Properties\{a45c254e-df1c-4efd-8020-67d146a850e0}\0025    NAME NOT FOUND    Desired Access: Query Value
12:58:59.8769133 PM    mmc.exe    6148    RegOpenKey    HKLM\System\CurrentControlSet\Enum\SCSI\Disk&Ven_Toshiba&Prod_Bics\4&73b0e52&0&010000\Properties\{a8b865dd-2e3d-4094-ad97-e593a70c75d6}\0005    NAME NOT FOUND    Desired Access: Query Value
12:58:59.8981553 PM    mmc.exe    6148    RegOpenKey    HKLM\SYSTEM\DriverDatabase\DeviceIds\scsi\disktoshiba_____________bicsu010    NAME NOT FOUND    Desired Access: Query Value
12:58:59.8983394 PM    mmc.exe    6148    RegOpenKey    HKLM\DRIVERS\DriverDatabase\DeviceIds\scsi\disktoshiba_____________bicsu010    NAME NOT FOUND    Desired Access: Query Value
12:58:59.8984558 PM    mmc.exe    6148    RegOpenKey    HKLM\SYSTEM\DriverDatabase\DeviceIds\scsi\disktoshiba_____________bics    NAME NOT FOUND    Desired Access: Query Value
12:58:59.8986269 PM    mmc.exe    6148    RegOpenKey    HKLM\DRIVERS\DriverDatabase\DeviceIds\scsi\disktoshiba_____________bics    NAME NOT FOUND    Desired Access: Query Value
12:58:59.8987455 PM    mmc.exe    6148    RegOpenKey    HKLM\SYSTEM\DriverDatabase\DeviceIds\scsi\disktoshiba_    NAME NOT FOUND    Desired Access: Query Value
12:58:59.8988843 PM    mmc.exe    6148    RegOpenKey    HKLM\DRIVERS\DriverDatabase\DeviceIds\scsi\disktoshiba_    NAME NOT FOUND    Desired Access: Query Value
12:58:59.8989911 PM    mmc.exe    6148    RegOpenKey    HKLM\SYSTEM\DriverDatabase\DeviceIds\scsi\toshiba_____________bicsu    NAME NOT FOUND    Desired Access: Query Value
12:58:59.8991214 PM    mmc.exe    6148    RegOpenKey    HKLM\DRIVERS\DriverDatabase\DeviceIds\scsi\toshiba_____________bicsu    NAME NOT FOUND    Desired Access: Query Value
12:58:59.8992303 PM    mmc.exe    6148    RegOpenKey    HKLM\SYSTEM\DriverDatabase\DeviceIds\toshiba_____________bicsu    NAME NOT FOUND    Desired Access: Query Value
12:58:59.8993764 PM    mmc.exe    6148    RegOpenKey    HKLM\DRIVERS\DriverDatabase\DeviceIds\toshiba_____________bicsu    NAME NOT FOUND    Desired Access: Query Value
12:59:19.6739176 PM    mmc.exe    6148    RegQueryValue    HKLM\System\CurrentControlSet\Enum\SCSI\Disk&Ven_Toshiba&Prod_Bics\4&73b0e52&0&010000\FriendlyName    NAME NOT FOUND    Length: 524
12:59:21.7558753 PM    mmc.exe    6148    RegOpenKey    HKLM\System\CurrentControlSet\Hardware Profiles\0001\System\CurrentControlSet\Enum\SCSI\DISK&VEN_TOSHIBA&PROD_BICS\4&73B0E52&0&010000    NAME NOT FOUND    Desired Access: Query Value
12:59:21.7888311 PM    mmc.exe    6148    RegOpenKey    HKLM\System\CurrentControlSet\Enum\SCSI\Disk&Ven_Toshiba&Prod_Bics\4&73b0e52&0&010000\Properties\{a8b865dd-2e3d-4094-ad97-e593a70c75d6}\0002    NAME NOT FOUND    Desired Access: Query Value
12:59:21.7891021 PM    mmc.exe    6148    RegOpenKey    HKLM\System\CurrentControlSet\Enum\SCSI\Disk&Ven_Toshiba&Prod_Bics\4&73b0e52&0&010000\Properties\{a8b865dd-2e3d-4094-ad97-e593a70c75d6}\0003    NAME NOT FOUND    Desired Access: Query Value
12:59:21.7893593 PM    mmc.exe    6148    RegOpenKey    HKLM\System\CurrentControlSet\Enum\SCSI\Disk&Ven_Toshiba&Prod_Bics\4&73b0e52&0&010000\Properties\{a8b865dd-2e3d-4094-ad97-e593a70c75d6}\0005    NAME NOT FOUND    Desired Access: Query Value
12:59:36.5095985 PM    mmc.exe    6148    RegOpenKey    HKLM\System\CurrentControlSet\Hardware Profiles\0001\System\CurrentControlSet\Enum\SCSI\DISK&VEN_TOSHIBA&PROD_BICS\4&73B0E52&0&010000    NAME NOT FOUND    Desired Access: Query Value
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top