Not sure what you mean by EAsus picture. I will just list them
Pic 1: The C drive is the SSD as one partition. E and F is the hard drive. 750GB split into two partitions. E with 300GB and the rest on F.
Pic 2: Disk 1 is the SSD and Disk 2 is the hard drive. On that picture where you see on Disk 2 "*.System", I changed that one to say "None" instead of "Active" by clicking on the option to make it inactive.
The other pictures are self explanatory I think.
Yes, looks like some parts of systems are spread over both SSD and HDD drives and BIOS is getting confuse which to boot from.
There's another problem, your BIOS is set to run in UEFI mode and I don't see any UEFI partitions in either disk.
Sorry for this idiotness on my behalf. I must correct an incorrect statement here. I did NOT have the hard drive inserted into the laptop while installing Windows 10 onto the SSD. That was the solution from the previous post to be able to install Windows 10 onto the SSD. I had to REMOVE the hard drive in order to be able to even begin the installation on the SSD. Sorry for the confusion.
BUT, on the hard drive there are remnants of a failed Windows 10 installation. Let me explain: When I got the SSD I cloned the hard drive OS partition to the SSD. Then when I saw that the machine booted with the SSD I put the hard drive back in and tried to factory reset the Windows. That FAILED. So I thought: "**** it, I will just use the SSD with the 'used' Windows on it." Then I bought a caddy and used the hard drive for data ever since. Until now..
P.S. The UEFI boot settings is something I read on another forum that someone suggested when I was trying to install Windows 10 with the hard drive in the computer as well as the SSD. I have changed it to "disabled".
You can "kill" those 2 first partitions from second drive since it's booting from SSD without second drive connected. They may be the ones causing problems. Can also merge them with E:.
Except for "Windows To Go", windows can't run from external drive anyway.
I would backup all the data you need from the HDD (drive 2?), delete all partitions, create a new NTFS inactive partition filling the drive then copy back your data.
This is a total mess.
I tried deleting the partitions and it 75% completed and stopped there. Then I ended the process after hours of waiting. Maybe not a good idea.
Now I have realised that there actually is some data on the disk that I would like back.
Now I have had the drive connected to the computer for more than 24 hours and in task manager the drive is constantly active. See picture:
It has been like that since yesterday.
If I use MiniTool Partition I can see the partitions and I can still browse the files. Which should be a good thing since I am after some files from there.
But when I use MiniTool Power Data Recovery I can only detect one file and that is some .ini file. Takes about a second to scan.
Quote
