• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Are you having HotKey issues? Click here for tips and tricks.
Common problems for Battery
We would like to share some of the most frequently asked questions about: Battery Reports, Hold a charge, Test and Calibrating Battery . Check out this link: Is your notebook plugged in and not charging?
Locked

‎05-01-2018 12:59 AM

HP Recommended
Product: HP Pavilion 15-ck063tx
Operating System: Microsoft Windows 10 (64-bit)

Just bought the basic version and decided to put in my spare SanDisk x300 256gb SATA m.2 into the laptop, in addition to the existing 1TB Hitachi 5400rpm drive. a few issues

 

1. installed the m.2, it is being detected and can be accessed for storage, however when i go into the BIOS i cannot select it 

 

2. cloned my HDD into the m.2 and unplugged the HDD, no detection of the m.2 at all at boot up

 

3. noticed the HP recovery program is separated 

 

so my question is,

 

1. how can i enable the M.2 to be selected as boot drive in the laptop? or is it not available?

 

2. why can i access the m.2 from desktop but not through the bios

 

3. if i choose to do a fresh install of windows 10, how can i enable the bios to read from bootable usb?

 

Please advise,

1 ACCEPTED SOLUTION

Accepted Solutions

‎05-01-2018 04:12 AM - edited ‎05-01-2018 04:28 AM

HP Recommended

Have you created a usb recovery flash drive?

 

The M.2 SSD is not recognized by the BIOS because it has:

 a) not been made active

b) has not been assigned a drive letter.

 

 

With the HP Recovery utility, you can use the HP Recovery utility to perform a factory image recovery to the 256 GB M.2 SSD.

 

 

The HP Recovery utility is on the legacy hard disk. It will also be on the USB recovery flash drive after you create one. Use the HP Recovery media creator to do that.  Once it has been created you can disconnect the original hard disk and make the M.2 SSD your boot disk.

 

 

 

 

How to create HP recovery media.

 

 

 

How to perform an HP recovery.


I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"



View solution in original post

Was this reply helpful? Yes No
12 REPLIES 12

‎05-01-2018 04:12 AM - edited ‎05-01-2018 04:28 AM

HP Recommended

Have you created a usb recovery flash drive?

 

The M.2 SSD is not recognized by the BIOS because it has:

 a) not been made active

b) has not been assigned a drive letter.

 

 

With the HP Recovery utility, you can use the HP Recovery utility to perform a factory image recovery to the 256 GB M.2 SSD.

 

 

The HP Recovery utility is on the legacy hard disk. It will also be on the USB recovery flash drive after you create one. Use the HP Recovery media creator to do that.  Once it has been created you can disconnect the original hard disk and make the M.2 SSD your boot disk.

 

 

 

 

How to create HP recovery media.

 

 

 

How to perform an HP recovery.


I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"



Was this reply helpful? Yes No

‎05-01-2018 06:52 AM

HP Recommended

No i did not create a usb recovery flash drive for the m.2 ssd.

 

So even when under 'This PC' it could recognise the m.2 ssd it is not considered active?

 

i will try your suggestion first and update you later. thanks

Was this reply helpful? Yes No

‎05-01-2018 09:11 AM

HP Recommended

steps done

1. created USB recovery media

2. ran it once on SSD

3. detached HDD

4. let SSD ran for additional software instllation

 

then it crashed when the bottom progress bar was at 25%.

 

the detail log shows last few entries being

 

MLGM based image

GMPP_IMAGE = False

detecting WinRE offset

PIN ERROR MSH PushbackBP.cmd PIN.BP.SIZE not defined

PIN ERROR MSH PushbackBP.cmd cant find BP

 

after that it goes back to the REcovery Manager showing Restoration Incomplete and i'm stuck there

Was this reply helpful? Yes No

‎05-01-2018 09:31 AM

HP Recommended

Disconnect the legacy hard disk.

 

Connect the power adapter.

 

Change the BIOS  system date to 01/01/2014.

 

Press F10 to exit and save the change.

 

Perform the factory image recovery again.


I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"



Was this reply helpful? Yes No

‎05-01-2018 10:16 AM

HP Recommended

i have tried the steps you have given, same issue still happens as the last post of mine. here is the latest log

 

[ 3:17:17.25][CreateE.cmd] **************************************************
[ 3:17:17.25][CreateE.cmd] [C:\SYSTEM.SAV\FactoryUpdate\CreateE.cmd] has started...
[ 3:17:17.25][CreateE.cmd] --------------------------------------------------
[ 3:17:17.25][CreateE.cmd] Start CreatE.cmd at FactoryUpdate... PASS2
[ 3:17:17.26][CreateE.cmd] --------------------------------------------------
[ 3:17:17.26][CreateE.cmd] Create ["C:\system.sav\CreateE.cmd.FAILURE.flg"]...
[ 3:17:17.26][CreateE.cmd]
[ 3:17:17.26][CreateE.cmd]
[ 3:17:17.28][CreateE.cmd]
[ 3:17:17.28][CreateE.cmd] ************************************************************
[ 3:17:17.28][CreateE.cmd] ************************************************************
[ 3:17:17.31][CreateE.cmd] ************************************************************
[ 3:17:17.31][CreateE.cmd] ************************************************************
[ 3:17:17.31][CreateE.cmd]
[ 3:17:17.32][CreateE.cmd] run [DiskPart.exe /s C:\System.sav\FactoryUpdate\dummy.txt]
[ 3:17:17.40][CreateE.cmd] --------------------------------------------------
[ 3:17:17.40][CreateE.cmd] [CreateDESP.txt]
[ 3:17:17.40][CreateE.cmd] --------------------------------------------------
[ 3:17:17.40][CreateE.cmd] --------------------------------------------------
[ 3:17:17.40][CreateE.cmd]
[ 3:17:17.42][CreateE.cmd] run DiskPart.exe /s C:\System.sav\FactoryUpdate\CreateDESP.txt
[ 3:17:17.46][CreateE.cmd] ErrorLevel=[-2147024809]
[ 3:17:17.47][CreateE.cmd]
[ 3:17:17.47][CreateE.cmd] [PIN_ERROR_MSG][CreateE.cmd] DiskPart.exe /s C:\System.sav\FactoryUpdate\CreateDESP.txt or DiskPart.exe /s C:\System.sav\FactoryUpdate\CreateESP.txt
[ 3:17:17.47][CreateE.cmd] [PIN_ERROR_MSG][CreateE.cmd] Return Code = [-2147024809]
[ 3:17:17.47][CreateE.cmd] FAILED to create ESP/MSR.
[ 3:17:17.49][CreateE.cmd]
[ 3:17:17.49][CreateE.cmd] RESULT=FAILED
[ 3:17:17.49][CreateE.cmd]
[ 3:17:17.49][CreateE.cmd] --------------------------------------------------
[ 3:17:17.50][CreateE.cmd] [CreateE.cmd] has completed...
[ 3:17:17.50][CreateE.cmd] **************************************************
[ 3:17:26.42][InactiveSP.cmd] [PIN_ERROR_MSG][InactiveSP.cmd] Failed to assign drive letter to ESP.
[ 3:17:26.42][InactiveSP.cmd] --------------------------------------------------
[ 3:17:26.42][InactiveSP.cmd] [InactiveSP.cmd] has completed...
[ 3:17:26.42][InactiveSP.cmd] **************************************************
[ 3:17:35.15][PushbackBP.cmd] **************************************************
[ 3:17:35.15][PushbackBP.cmd] [C:\SYSTEM.SAV\2ndCap\PushbackBP.cmd] has started...
[ 3:17:35.15][PushbackBP.cmd] --------------------------------------------------
[ 3:17:35.17][PushbackBP.cmd]
[ 3:17:35.17][PushbackBP.cmd] Create ["C:\system.sav\PushbackBP.cmd.FAILURE.flg"]...
[ 3:17:35.17][PushbackBP.cmd]
[ 3:17:35.18][PushbackBP.cmd] Check if this is GMPP or not [MLGM].
[ 3:17:35.18][PushbackBP.cmd] * [FIND /I 'GM_SUPPORT_TYPE=GMPP' C:\system.sav\Flags\PINCTRLTwk.pf]
[ 3:17:35.20][PushbackBP.cmd]
[ 3:17:35.20][PushbackBP.cmd] FIND command returned [1]
[ 3:17:35.20][PushbackBP.cmd]
[ 3:17:35.22][PushbackBP.cmd] [MLGM]-based image.
[ 3:17:35.22][PushbackBP.cmd] GMPP_IMAGE = [FALSE]
[ 3:17:35.23][PushbackBP.cmd]
[ 3:17:35.23][PushbackBP.cmd] Detecting WinRE offset...
[ 3:17:35.23][PushbackBP.cmd]
[ 3:17:35.27][PushbackBP.cmd] [PIN_ERROR_MSG][PushbackBP.cmd] PIN.BP.SIZE not defined
[ 3:17:35.27][PushbackBP.cmd] [PIN_ERROR_MSG][PushbackBP.cmd] Can't find BP...
[ 3:17:35.28][PushbackBP.cmd] --------------------------------------------------
[ 3:17:35.28][PushbackBP.cmd] [PushbackBP.cmd] has completed...
[ 3:17:35.30][PushbackBP.cmd] **************************************************

Was this reply helpful? Yes No

‎05-01-2018 10:25 AM

HP Recommended

I suggest putting the legacy disk back in so you can still use the notebook.

 

There could be an issue with the M.2 SSD.

 

Contact the vendor and request an RMA.


I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"



Was this reply helpful? Yes No

‎05-01-2018 08:36 PM

HP Recommended

 here i somehow got it to work! here are the steps i did

 

1. reseated both legacy hdd and m.2 ssd 

2. check with crystaldiskinfo, both shows positive signs

3. unplug legacy hdd

4. reset bios date to 1/1/2014

5. ran disc dignostic tool with f2 on start up

6. boot from USB HP recovery tool

7. ran recovery media

8. restarted to allow software installation

 

this time it actually update all the way and i'm on the desktop. i suspect maybe it's the contact point on the installation failing on me.

 

running through the windows update and stress testing it later. will post a update after that.

Was this reply helpful? Yes No

‎05-02-2018 01:54 AM - edited ‎05-02-2018 02:00 AM

HP Recommended

It just needed reseating. The first log showed that it was initially having trouble with partitioning and creating the MSR slice. There was a " Failed to assign drive letter to ESP." error in the last log. There was an error each time. I think the issue was that the recovery flash drive had issues and not the hardware.

 

So essentially, what I suggested two posts back was the solution.

 

It is good to hear that the OS is up and running on the M.2 SSD. 🙂

 

Don't forget to change the BIOS system back to the current date.

 

 

 


I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"



Was this reply helpful? Yes No

‎05-02-2018 06:29 AM

HP Recommended
Noted on the BIOS date.

I see, never know which is the issue when it comes to tech haha.

Anyway now that I want to use the legacy HDD as storage, do I need to do a full wipe? Or just format the partition through Disk Management. My main concern is the HP recovery partition in the legacy HDD.
Was this reply helpful? Yes No
Warning
Be alert for scammers posting fake support phone numbers and/or email addresses on the community.
If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.
Didn't find what you were looking for? Ask the community
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.