HP Envy HDD to SSD + HDD ??

[pvrbulls]

Don't know if this is the right forum for this problem, but it seemed like the best place to start.

Last week we got an HP Envy 17t-j100 for my wife that has an empty drive bay into which I installed an “old” Samsung 830 128 GB SSD. I used Samsung’s Data Migration software to copy everything from the original HDD to the SSD… except for the D:\ Recovery partition. (I didn’t copy the Recovery partition because with the 16 GB of RAM on the system, I am already using up about 50 GB with no applications installed and the Recovery partition was going to take another 20 or so GB.) After that was completed, I think( it’s all become sort of a blur at this point) that the next thing I did was to attempt to boot into BIOS where I intended to set the boot priority to the new SSD. Well….that didn’t happen. The SSD did not show up! Actually, nothing is listed except “OS boot Manager” and “Boot From EFI File”. No matter how many drives are connected, that is all that there is to choose from. I don’t know what “Boot From EFI File” does, so I haven’t changed anything. I think what happened next was that the system then booted up with both the SSD and the HDD connected. I really cannot remember for sure. In any event, I subsequently disconnected the HDD and booted the system with only the SSD installed… and it booted just fine!

I thought that my problems were over and that these HP laptops weren’t as bad as a lot of folks were saying. Then…. I reconnected the HDD. When I rebooted the system, the HDD was nowhere to be found. Accidently, while trying to compose a post here at AnandTech to ask for help, I discovered that the system has to be rebooted twice for the HDD to be recognized. Well, that solved that problem; it’s clear sailing from here…right? Not exactly! Everything seemed to be working fine while I was trying to figure out Windows 8(I hate it!) so that I could make it look and feel like Windows 7… until HP Support Assistant arrived on the scene wanting to update various drivers and other system elements. The first driver update seemed to go smoothly enough. Then it started to update the wireless network adapter…and the wireless adapter quit! I rebooted and everything was back to normal; I had internet connection… until Support Assistant came to life again and started examining the system looking to things to “fix.” The wifi adapter would go down every time that Support Assistant became active. I finally just uninstalled Support Assistant, which seemed to solve the problem. I have not lost the wifi adapter since.

After that I again thought I was home free but, while attempting to access some user setting on the Metro side, I was denied access and shown the following:

I am working from what is now my C:\ drive, the SSD, and am being denied access to files on the F:\ drive when I attempt to access a file on the C:\ drive! It seems that HP is not through with me yet!

I ran EasyBCD 2.2 Community Edition with the HDD out of the system and got the following:

Note, at the top, “EasyBCD Boot Device: C:\” and Entry #5 at the bottom.

I then ran EasyBCD with the HDD added to the system and got the following:

Now note, at the top, “EasyBCD Boot Device: D:\” and Entry #5 at the bottom.

It seems that whenever that D:\ Recovery Partition is present, the HP system recognizes it over any other boot information that might be present on another drive. What really puzzles me is why the boot information on the D:\ partition ever directs booting to the SSD at all. Right now, with the HDD installed it appears that both Windows 8 installations are being at least partially used at the same time. I am reasonably certain that I can put a blank HDD in place of the original HP loaded drive and eliminate all my problems. If I can find no better solution, that is what I intend to do. I am hoping that someone here has a more elegant solution, however, and that there is a way to work around or disable the D:\ Recovery Partition without destroying it as I want to keep the option of going back and starting over as if I had never installed the SSD.

I found this thread on the Windows Eight Forums from about 20 months ago where mikekoz had a very similar problem and just installed a new drive. Maybe someone here knows another way to "skin this cat."

Sorry for the long, long read.

 

[corkyg]

Actually this thread belongs in M&S. Have requested a move. Move done!

 

[Ketchup]

It sounds like the original drive still has the boot loader, which would explain why the computer uses it if present. You would want to tell the EFI file that the new drive has the boot loader it needs in order to be totally independent.

Personally, if you are operating the laptop with both drives in it, and you are not deleting the recovery partition from the original drive, I don't see the problem leaving it the way it is. You have established that it will boot fine when the original drive is not in place.

The app question is interesting, because it is looking for data in a user folder on the other drive, which is, of course, locked as the file it needs is in another user account. Was the app added to the original drive after you performed the clone? Does this occur with all the apps? One test would be to remove the original drive and see if you have additional app issues.

If that drive continues to be an issue, you may just want to make recovery media, then wipe the original drive and use it for storage.

 

[pvrbulls]

It sounds like the original drive still has the boot loader, which would explain why the computer uses it if present. You would want to tell the EFI file that the new drive has the boot loader it needs in order to be totally independent.

Sounds good! How does one do that? I haven't a clue!

The app question is interesting, because it is looking for data in a user folder on the other drive, which is, of course, locked as the file it needs is in another user account. Was the app added to the original drive after you performed the clone? Does this occur with all the apps?

It wasn't an app. I was trying to access Windows 8 User Settings to eliminate a lock screen, as best I can recall. That's when I got that notice that I did not have permission. I have installed no Windows 8 Apps and have used none.

If that drive continues to be an issue, you may just want to make recovery media, then wipe the original drive and use it for storage.

That will probably work, but I think it would be safer/easier to just put in a fresh drive and save the other for "just in case" since it has everything on it direct from HP....and I know it works! A new drive is only about $60 for a 1 TB....and I could easily get by with something smaller.

 

[Ketchup]

Sounds good! How does one do that? I haven't a clue!

http://san.schausberger.cc/2013/03/windows-8-move-boot-manager-and-boot-directory/
The export command looks to be of interest here. I would also recommend lookiing for more advanced options in the BIOS (both through the pre-windows-load menu and the Windows access) for further options if needed.

It wasn't an app. I was trying to access Windows 8 User Settings to eliminate a lock screen, as best I can recall. That's when I got that notice that I did not have permission. I have installed no Windows 8 Apps and have used none.

OK. I am wondering if straightening out the above will also fix this problem.

That will probably work, but I think it would be safer/easier to just put in a fresh drive and save the other for "just in case" since it has everything on it direct from HP....and I know it works! A new drive is only about $60 for a 1 TB....and I could easily get by with something smaller.

That makes sense. In that case, I even more strongly feel that the original drive should not even be in the machine. And if you take the original drive out, leaving only the SSD, do any problems remain?

 

[pvrbulls]

That makes sense. In that case, I even more strongly feel that the original drive should not even be in the machine. And if you take the original drive out, leaving only the SSD, do any problems remain?

With the original drive out, everything is normal. No problems whatsoever(so far).