Recovery Manager Fails "Restoration Incomplete"

[elv5003]

Attempting to revert to factory install on HP 15-AU062NR; I previously upgraded the wireless card from rtl8723be to rtl8821ce. 

I no longer have the old WiFi card to reinstall it; should i just remove the current one?  Is there any way to introduce the updated driver to the recovery process?

Recovery Manager shows "Restoration Incomplete" - CTOERROR.FLG shows the following (the only failed test is the Network Controller)

[ 9:19:11.27] ************************************************** 
[ 9:19:11.28]  [C:\SYSTEM.SAV\ExitProc\ErrorChk\ChkError.cmd] has started... 
[ 9:19:11.31] -------------------------------------------------- 
[ 9:19:11.31]  Check SW Error... 
[ 9:19:11.33] -------------------------------------------------- 
[ 9:19:11.35]   
[ 9:19:11.36]  Create ["C:\system.sav\ChkError.cmd.FAILURE.flg"] file... 
[ 9:19:11.36]   
[ 9:19:11.38]  Logfile [C:\system.sav\Logs\CheckLog\ChkErr_PASS2_BBVClean.log]... 
[ 9:19:11.40]   
[ 9:19:11.40]  Check 2nd parameter [BBVClean] 
[ 9:19:11.41]   
[ 9:19:11.41]  Error Checking items : [MEMDUMP,APPSLOG,REGDEV,TIMEOUT,WINSAT,FAILUREFLG] 
[ 9:19:11.43]  -------------------------------------------------- 
[ 9:19:11.45]  Checking : Memory Dump 
[ 9:19:11.45]    Could not find memory dump... 
[ 9:19:11.46]   
[ 9:19:11.46]  [DumpFile] 
[ 9:19:11.48]  Result=PASSED 
[ 9:19:11.49]  -------------------------------------------------- 
[ 9:19:11.49]  Checking : Apps' log 
[ 9:19:11.51]   
[ 9:19:14.12]  [AppsLog] 
[ 9:19:14.16]  Result=PASSED 
[ 9:19:14.22]  -------------------------------------------------- 
[ 9:19:14.27]  Checking : Yellow-Bang 
[ 9:19:14.31]   
[ 9:19:14.38]  Run [PINChkT.exe /dev /s] 
[ 9:19:16.33]   
[ 9:19:16.40]  Append [REGDEVT_PASS2_BBVClean.LOG] to [C:\system.sav\Logs\CheckLog\ChkErr_PASS2_BBVClean.log]... 
[RegistryDevicesCheck]
Result=FAILED

FAILED DEVICE #0:
Description  : Network Controller
PNPDeviceID  : PCI\VEN_10EC&DEV_C821&SUBSYS_831A103C&REV_00\00E04CFFFEC8210100
Code         : [28]

[ 9:19:16.44]   
[ 9:19:16.48]  Run [FIND.exe /I 'Result=FAILED' C:\SYSTEM.SAV\Logs\PINPROC\REGDEVT_PASS2_BBVClean.LOG] 
[ 9:19:16.55]  [PASS2_BBVClean][PIN_ERROR_MSG][ChkError.cmd] There was some FAILED device. Please check the file C:\SYSTEM.SAV\Logs\PINPROC\REGDEVT_PASS2_BBVClean.LOG. 
[ 9:19:16.58]    There was some FAILED device... 
[ 9:19:16.63]    or, there was not target file... 
[ 9:19:16.68]   
[ 9:19:16.73]  -------------------------------------------------- 
[ 9:19:16.77]  Checking : Timeout in INSTALL.log 
[ 9:19:16.80]   
[ 9:19:16.85]  Run [FIND.exe /I 'timeout with' C:\System.sav\Util\Install.log] 
[ 9:19:17.69]  Run [FIND.exe /I 'timeout wait' C:\System.sav\Util\Install.log] 
[ 9:19:17.88]   There is NO timeout in install.log file. 
[ 9:19:17.93]   
[ 9:19:17.96]  [TIMEOUT] 
[ 9:19:18.00]  Result=PASSED 
[ 9:19:18.07]  -------------------------------------------------- 
[ 9:19:18.10]  Checking : WinSAT 
[ 9:19:18.15]   
[ 9:19:18.19]  [WinSAT] 
[ 9:19:18.24]  Result=PASSED 
[ 9:19:18.29]  -------------------------------------------------- 
[ 9:19:18.33]  Checking : FAILURE.flg 
[ 9:19:18.51] ************************************************** 
[ 9:19:18.51]  [CheckFailureFlags.cmd] has started... 
[ 9:19:18.52] -------------------------------------------------- 
[ 9:19:18.52]  Check FAILURE.flg at [PASS2_BBVClean] 
[ 9:19:18.54] -------------------------------------------------- 
[ 9:19:26.51]   
[ 9:19:26.53]  No FAILURE.flg was found in C:\SwSetup folder 
[ 9:19:26.54]   
 Volume in drive C is WINDOWS
 Volume Serial Number is 704B-BC77

 Directory of c:\system.sav

06/20/2023  09:23 AM    <DIR>          2ndCap
10/16/2016  07:21 PM            10,936 5CD61976CQ8B_DPS
06/20/2023  09:06 AM    <DIR>          bbv
06/20/2023  09:19 AM                46 ChkError.cmd.FAILURE.flg
10/14/2016  12:36 PM           130,088 CNB16WW3DRT602.ini
10/17/2016  04:05 AM    <DIR>          CONFIG
10/16/2016  07:22 PM             8,117 cpqdl.ini
10/16/2016  07:22 PM             4,161 CTO.TXT
10/16/2016  07:22 PM                14 CTOHW.TXT
06/20/2023  09:12 AM    <DIR>          Exclude
06/20/2023  09:36 AM    <DIR>          ExitProc
06/20/2023  09:35 AM    <DIR>          FactoryUpdate
10/17/2016  04:06 AM    <DIR>          fbi
06/20/2023  09:19 AM    <DIR>          Flags
10/16/2016  07:20 PM             2,801 G34D-ABA-02
06/20/2023  09:25 AM             8,917 Info.bom
06/20/2023  09:19 AM    <DIR>          logs
05/10/2016  01:55 AM    <DIR>          P2PP
05/27/1997  02:42 AM                46 REBOOT.ME
10/17/2016  03:59 AM               368 REGFLUSH.LOG
06/20/2023  09:19 AM               139 Result.ini
10/17/2016  03:17 AM    <DIR>          support
10/17/2016  03:58 AM           505,904 SYSINFO.LOG
06/20/2023  09:06 AM    <DIR>          WDT
              12 File(s)        671,537 bytes
              12 Dir(s)  956,380,561,408 bytes free
[ 9:19:26.54] -------------------------------------------------- 
[ 9:19:26.56]  [CheckFailureFlags.cmd] has completed... 
[ 9:19:26.58] ************************************************** 
[ 9:19:26.61]   
[ 9:19:26.65]  [FAILURE_FLAG] 
[ 9:19:26.70]  Result=PASSED 
[ 9:19:26.76]   
[ 9:19:26.79]  -------------------------------------------------- 
[ 9:19:26.84]  Some error detected... 
[ 9:19:26.90]   
[ 9:19:26.95] -------------------------------------------------- 
[ 9:19:27.00]  [C:\SYSTEM.SAV\ExitProc\ErrorChk\ChkError.cmd] 
[ 9:19:27.04]  [PASS2_BBVClean][PIN_ERROR_MSG][ChkError.cmd] found [1] SW issue[s]... 
[ 9:19:27.08] -------------------------------------------------- 
[ 9:19:27.12]  [PASS2_BBVClean][PIN_ERROR_MSG][ChkError.cmd] Refer the following file[s] if exists to see detail. 
[ 9:19:27.17]  [PASS2_BBVClean][PIN_ERROR_MSG][ChkError.cmd] C:\CTOERROR.flg , C:\System.sav\*FAILURE.flg, or C:\system.sav\Logs\AllFailure.log 
[ 9:19:27.22]   
[ 9:19:27.26] -------------------------------------------------- 
[ 9:19:27.31]   
[ 9:19:27.36]  This is for customer image... 
[ 9:19:27.39]   
[ 9:19:27.44]  Trigger CTO panic... 
[ 9:19:27.48]   
[ 9:19:27.53]  This is Recovery image... 
[ 9:19:27.58]   
[ 9:19:27.62] -------------------------------------------------- 
[ 9:19:27.65]  [ChkError.cmd] has completed... 
[ 9:19:27.70] ************************************************** 

[ 9:21:07.99] ------------------------------------------------------------
[ 9:21:07.99] There might be unexpected reboot during [Windows setup]. 
[ 9:21:07.99] The process will cause CTO panic  
[ 9:21:07.99] because the image might not be normal now... 
[ 9:21:07.99] ------------------------------------------------------------

[Paul_Tikkanen · Accepted solution]

Hi:

Yes, it is failing because of the different Wi-Fi card.

I had the same thing happen to me on a HP 350 G1 when I replaced the Broadcom card it came with for an Intel wifi card.

There's nothing you can do other than to buy the original Realtek Wi-Fi card/part number it came with if you want to use the recovery media.

Otherwise, you can always clean install W10 by making a bootable W10 installation flash drive with the media creation tool and then install the drivers and software from your notebook's support page.

You can try removing the card altogether, but I would bet dollars to doughnuts that the recovery will fail because it is looking for a Realtek RTL8723BE to install a driver for.

[elv5003]

Unfortunately I threw the old card away recently (after it sat on my desk for a year).

I managed to install the correct driver for the card (CTOERROR.FLG file opened in notepad; I used the open command in notepad to get into file explorer; from there I was able to manually select the correct driver in device manager after attempting to install it from an SD card).  I even got networking up and running and connected to WiFi.

However, I could not for the life of me get past the "Restoration Incomplete" popup/screen.  I could not figure out how to re-trigger whatever check was causing this error - although it seemed like Windows was completely functional in the background and device manager was showing that all networking cards were properly installed.  

You can minimize the HP File Based Installer (FBI) and reveal a debug menu - I cant help but think there must be some way to dismiss/skip or otherwise get the process to accept the alternate device.

I have a recovery cd, but I am not sure if I have a Win10 USB created...

[elv5003]

Turns out I did have a Win 10 USB.  Much easier solution than fighting Recovery Manager.

Thank you, Paul!

[Paul_Tikkanen]

You're very welcome.