Cloned install boot issues

One reason you might want to consider de-tweaking (moving toward defaults) is the "confused" statement (in red by me) below:

chrysalis said:

Kaktussoft said:

chrysalis said:

I am still seeing 2 issues, both I think related to the lettering and cloning.

1 - is the resource monitor under the disk tab shows weird drive lettering for running apps. posting pic on this post. it sayd D:0 instead of C:.

2 - is that apps in the windows firewall which have allow rules based on the app location are been blocked, this I think is related to #1 that the raw drive letter is incorrect even if appears as C: in explorer.

Take a look at your resource monitor screenshot! Do you see D, H, R are on disk 0!! But R is fake on disk 0??

Is windows on R?? Please disable ramdisk... at least temporary.... and test again

No thats windows getting confused.

R is a ramdisk, it is not on a physical drive. That same issue occured when I had the ramdisk before the clone.

I have turned it off to test and it had no affect on this issue.

here is my apology to gregrocker, having a 2nd think about it, even if I disagreed I should have simply tried his suggestion and said if it worked or not, so I am sorry for lack of respect given to you.

On the swap I agree, the benefit may not be significant enough to be worth bothering with especially with how much ram I got, I am now back to one swapfile. It was something I originally set when the machine had less ram and a slower boot disk.

On something like my laptop which has a slow 5400rpm drive tho I think it would be noticeable if low on ram, however on that I just upgraded the ram to stop it swapping excessively.

F5ing said:

One reason you might want to consider de-tweaking (moving toward defaults) is the "confused" statement (in red by me) below:

chrysalis said:

Kaktussoft said:

Take a look at your resource monitor screenshot! Do you see D, H, R are on disk 0!! But R is fake on disk 0??

Is windows on R?? Please disable ramdisk... at least temporary.... and test again

No thats windows getting confused.

R is a ramdisk, it is not on a physical drive. That same issue occured when I had the ramdisk before the clone.

I have turned it off to test and it had no affect on this issue.

as is for now I did disable ramdisk and non default swapfile, what I havent done is unplugged all other hdd's, however I have noticed the hdd on the jmicron controller (which incidenntly is on its own with an easy to access cable) is the drive showing first in things like hdtune and crystal diskmark info, the ssd is shown 2nd. So unplugging that would probably bump the ssd up and I will try it later today, but I dont think it would be permanent when plugging back in but I will try and see. Its all the other hdd's on the intel controller in my bottom hdd bay that are a pain to access.

Just so others know for information purposes I recently did 2 more clones.

One on my main rig from my samsung 830 ssd to new samsung 850 pro ssd, and another on my windows 10 test rig from a crappy slow 5400rpm hdd to the samsung 830 ssd.

In both cases it was flawless, none of the previous issues.

This time I used Macrium Reflect free (plan to buy it tho). I made a WinPE USB boot stick from it and did the clone using that media rather than within windows, it was far simpler than norton ghost and worked without any issues whatsoever.

In addition this time I followed the recommendation that on first boot after clone all other hdd's were unplugged to ensure no drive letter issues. In the fractal r4 design case unlike my old case thankfully this was easy to do.

Also this worked for windows 10 as well even tho I was using WinPE 3.1 not 5.0.

The only annoyance of the process was having to manually find the right usb2 drivers to copy to the boot media, as the free version doesnt automatically handle it.

for me usb2 wasnt working, my keyboard wasnt even working (usb keyboard). I only had mouse which is PS2 and internal drives, the target ssd of the clone was connected via usb to sata cable for conveniance.