If I am understanding you correctly, you lost the Windows 10 ISO but the clone went well? Is that correct? If so, it is no big deal, you can download it again. All is not lost.
Sorry, your replies came as I composed, ships passing in the night.
I just went back to Macrium Reflect and it was still waiting for approval to proceed so I gave the go ahead. The Win10 ISO is on a CD. I just saw the new name on the unused disk (Win 10 x64 System Disk) and panicked.
Is there a verify feature for this cloning procedure? I hope it does not give the same result as the failed imaging efforts.
In typical fashion, MS chose the word 'until' 7/29/16. Does the upgrade not work tomorrow?
thanks
baumgrenze
Thanks for the reassurance. I forgot about the clocks that sometimes are part of the nag.
Macrium Reflect just informed me that the clone is done. Is there any point in verifying it, or can I count on empirical observation to tell me when I have only the cloned disk to boot from.
I think I will shut down, disconnect the original System Disk and have a look at the clone to see if it runs.
thanks for your patience
baumgrenze
I am still here, although pretty soon I'll need some sustenance to get through the evening.
I just paid dearly for not documenting which SSD was in which drive bay. I could not see the S/N without disconnecting and removing one of the two. While I was in there, I realized I really needed to vacuum the front air filters.....And so it goes.
What I did not appreciate was that when I cloned my old System Disk the clone inherited the recognizable name I'd just given it. And, of course, Windows called it C:.
I tried running CrystalDiskInfo but Windows returned the cryptic message, "The drive or network connection that the shortcut 'CrystalDiskInfo.lnk' refers to is unavailable..." I learned earlier today that it does return the S/N. It is also probably true that the new Crucial Storage Executive program displays that. I hope to find out soon.
My next task is to use the copy of the program on my USB stick to update the drive firmware. I will report back after that.
thanks
baumgrenze
No joy!
I had my digital camera at the ready, flash off, but the designer of the update routine chose a black screen with blue text so that the shutter speed is way too low to get a readable image, esp when screens are going by quickly and you are unfamiliar with the time available.
I caught this much:
"Invalid firmware directory specified with -i option" but the following path was harder to read, maybe it was "tmp/mse_firmware" and the program rebooted me back to the same firmware, but the system still works!
Perhaps I need to install the software on the drive being updated? I will go try an install on this drive next.
thanks
baumgrenze
Somehow an image got attached. I looked at manage attachments but I could not see how to delete it. Please ignore it.
Nothing is easy...
The install wizard find a previous installation on G:\
I asked it to install anyway, figuring it would use the drive it is on, but it does not work, it cannot find G:\.
The wizard forgot to ask where I wanted to install it.
Windows Explorer only shows this:
thanks
baumgrenze
OK, I assume you are booted into the cloned drive. If the Executive program was on the original drive, it should be on the cloned drive also. See if it is and try to open it and do the upgrade. If it won't open, go to control panel, uninstall a program and see if you can uninstall the executive program. Then Copy the Executive Installer to your C drive Desktop and install it again. The executive program is to update your SSD firmware. If you don't still have the Crucial Executive installer, download it again. I'll give you the link in just a minute.
Quote
