-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Operating System and Recovery
- Re: How to solve the problem of restoring windows to the fac...

Create an account on the HP Community to personalize your profile and ask a question
04-19-2018 06:04 PM - edited 04-19-2018 06:18 PM
Hello. I have such a problem. When restoring the operating system Windows 10x64, using the recovery system HP Recovery Manager, there is a recovery error in Windows. After that, it is possible to save the error to USB storage. This was done.
How to solve the problem of restoring windows to the factory settings?
[ 5:10:44.28][ChkError.cmd] ************************************************** [ 5:10:44.28][ChkError.cmd] [C:\SYSTEM.SAV\ExitProc\ErrorChk\ChkError.cmd] has started... [ 5:10:44.30][ChkError.cmd] -------------------------------------------------- [ 5:10:44.30][ChkError.cmd] Check SW Error... [ 5:10:44.31][ChkError.cmd] -------------------------------------------------- [ 5:10:44.31][ChkError.cmd] [ 5:10:44.33][ChkError.cmd] Create ["C:\system.sav\ChkError.cmd.FAILURE.flg"] file... [ 5:10:44.34][ChkError.cmd] [ 5:10:44.35][ChkError.cmd] Logfile [C:\system.sav\Logs\CheckLog\ChkErr_PASS2_BBVClean.log]... [ 5:10:44.36][ChkError.cmd] [ 5:10:44.37][ChkError.cmd] Check 2nd parameter [BBVClean] [ 5:10:44.37][ChkError.cmd] [ 5:10:44.39][ChkError.cmd] Error Checking items : [MEMDUMP,APPSLOG,REGDEV,TIMEOUT,WINSAT,FAILUREFLG,RMFAIL] [ 5:10:44.39][ChkError.cmd] -------------------------------------------------- [ 5:10:44.40][ChkError.cmd] Checking : Memory Dump [ 5:10:44.40][ChkError.cmd] Could not find memory dump... [ 5:10:44.42][ChkError.cmd] [ 5:10:44.42][ChkError.cmd] [DumpFile] [ 5:10:44.43][ChkError.cmd] Result=PASSED [ 5:10:44.43][ChkError.cmd] -------------------------------------------------- [ 5:10:44.45][ChkError.cmd] Checking : Apps' log [ 5:10:44.45][ChkError.cmd] [ 5:10:45.94][ChkError.cmd] [AppsLog] [ 5:10:45.99][ChkError.cmd] Result=PASSED [ 5:10:46.02][ChkError.cmd] -------------------------------------------------- [ 5:10:46.06][ChkError.cmd] Checking : Yellow-Bang [ 5:10:46.09][ChkError.cmd] [ 5:10:46.13][ChkError.cmd] Run [PINChkT.exe /dev /s] [ 5:10:46.71][ChkError.cmd] [ 5:10:46.75][ChkError.cmd] Append [REGDEVT_PASS2_BBVClean.LOG] to [C:\system.sav\Logs\CheckLog\ChkErr_PASS2_BBVClean.log]... [RegistryDevicesCheck] Result=PASSED [ 5:10:46.78][ChkError.cmd] [ 5:10:46.83][ChkError.cmd] Run [FIND.exe /I 'Result=FAILED' C:\SYSTEM.SAV\Logs\PINPROC\REGDEVT_PASS2_BBVClean.LOG] [ 5:10:46.88][ChkError.cmd] No Yellow-bang device found... [ 5:10:46.91][ChkError.cmd] Result=PASSED [ 5:10:46.94][ChkError.cmd] [ 5:10:46.97][ChkError.cmd] -------------------------------------------------- [ 5:10:47.00][ChkError.cmd] Checking : Timeout in INSTALL.log [ 5:10:47.03][ChkError.cmd] [ 5:10:47.07][ChkError.cmd] Run [FIND.exe /I 'timeout with' C:\System.sav\Util\Install.log] [ 5:10:47.32][ChkError.cmd] Run [FIND.exe /I 'timeout wait' C:\System.sav\Util\Install.log] [ 5:10:47.50][ChkError.cmd] There is TIMEOUT in install.log file. [ 5:10:47.53][ChkError.cmd] [ 5:10:47.58][ChkError.cmd] [TIMEOUT] [ 5:10:47.61][ChkError.cmd] Result=FAILED [ 5:10:47.64][ChkError.cmd] -------------------------------------------------- [ 5:10:47.68][ChkError.cmd] Checking : WinSAT [ 5:10:47.71][ChkError.cmd] [ 5:10:47.74][ChkError.cmd] [WinSAT] [ 5:10:47.77][ChkError.cmd] Result=PASSED [ 5:10:47.82][ChkError.cmd] -------------------------------------------------- [ 5:10:47.85][ChkError.cmd] Checking : FAILURE.flg [ 5:10:47.96][CheckFailureFlags.cmd] ************************************************** [ 5:10:47.97][CheckFailureFlags.cmd] [CheckFailureFlags.cmd] has started... [ 5:10:47.97][CheckFailureFlags.cmd] -------------------------------------------------- [ 5:10:47.99][CheckFailureFlags.cmd] Check FAILURE.flg at [PASS2_BBVClean] [ 5:10:47.99][CheckFailureFlags.cmd] -------------------------------------------------- [ 5:10:52.93][CheckFailureFlags.cmd] [ 5:10:52.93][CheckFailureFlags.cmd] No FAILURE.flg was found in C:\SwSetup folder [ 5:10:52.94][CheckFailureFlags.cmd] Volume in drive C is WINDOWS Volume Serial Number is 0CF3-72C8 Directory of c:\system.sav 31/03/2018 11:39 <DIR> 2ndCap 20/11/2017 02:13 12,428 ABC72000P988_DPS 31/03/2018 04:35 <DIR> bbv 20/11/2017 02:12 3,318 BU11P2XABVR3M02 31/03/2018 05:10 46 ChkError.cmd.FAILURE.flg 11/11/2017 00:33 57,846 CNB17WW3K3T602.ini 20/11/2017 10:48 <DIR> Config 20/11/2017 02:15 8,621 cpqdl.ini 20/11/2017 02:15 4,530 CTO.TXT 20/11/2017 02:15 14 CTOHW.TXT 31/03/2018 11:29 <DIR> Exclude 31/03/2018 11:49 <DIR> ExitProc 31/03/2018 11:48 <DIR> FactoryUpdate 20/11/2017 10:49 <DIR> fbi 31/03/2018 05:10 <DIR> Flags 31/03/2018 11:40 9,339 Info.bom 31/03/2018 05:10 <DIR> logs 26/10/2017 08:42 <DIR> P2PP 27/05/1997 10:42 46 REBOOT.ME 20/11/2017 03:11 368 REGFLUSH.LOG 31/03/2018 05:10 139 Result.ini 20/11/2017 03:00 <DIR> support 20/11/2017 03:10 474,368 SYSINFO.LOG 20/11/2017 10:38 <DIR> WinPE_OnLine 12 File(s) 571,063 bytes 12 Dir(s) 95,979,024,384 bytes free [ 5:10:52.94][CheckFailureFlags.cmd] -------------------------------------------------- [ 5:10:52.96][CheckFailureFlags.cmd] [CheckFailureFlags.cmd] has completed... [ 5:10:52.96][CheckFailureFlags.cmd] ************************************************** [ 5:10:52.99][ChkError.cmd] [ 5:10:53.02][ChkError.cmd] [FAILURE_FLAG] [ 5:10:53.07][ChkError.cmd] Result=PASSED [ 5:10:53.11][ChkError.cmd] -------------------------------------------------- [ 5:10:53.16][ChkError.cmd] Checking : RMFAIL.flg exists or not [ 5:10:53.19][ChkError.cmd] [ 5:10:53.24][ChkError.cmd] No [C:\SYSTEM.SAV\Flags\RMFAIL.flg]. [ 5:10:53.27][ChkError.cmd] [ 5:10:53.30][ChkError.cmd] [RMFAIL] [ 5:10:53.33][ChkError.cmd] Result=PASSED [ 5:10:53.38][ChkError.cmd] [ 5:10:53.41][ChkError.cmd] -------------------------------------------------- [ 5:10:53.44][ChkError.cmd] Some error detected... [ 5:10:53.49][ChkError.cmd] [ 5:10:53.52][ChkError.cmd] -------------------------------------------------- [ 5:10:53.55][ChkError.cmd] [C:\SYSTEM.SAV\ExitProc\ErrorChk\ChkError.cmd] [ 5:10:53.58][ChkError.cmd] [PASS2_BBVClean][PIN_ERROR_MSG][ChkError.cmd] found [1] SW issue[s]... [ 5:10:53.61][ChkError.cmd] -------------------------------------------------- [ 5:10:53.66][ChkError.cmd] [PASS2_BBVClean][PIN_ERROR_MSG][ChkError.cmd] Refer the following file[s] if exists to see detail. [ 5:10:53.69][ChkError.cmd] [PASS2_BBVClean][PIN_ERROR_MSG][ChkError.cmd] C:\CTOERROR.flg , C:\System.sav\*FAILURE.flg, or C:\system.sav\Logs\AllFailure.log [ 5:10:53.72][ChkError.cmd] [ 5:10:53.77][ChkError.cmd] -------------------------------------------------- [ 5:10:53.80][ChkError.cmd] [ 5:10:53.83][ChkError.cmd] This is for customer image... [ 5:10:53.86][ChkError.cmd] [ 5:10:53.90][ChkError.cmd] Trigger CTO panic... [ 5:10:53.93][ChkError.cmd] [ 5:10:53.96][ChkError.cmd] This is Recovery image... [ 5:10:53.99][ChkError.cmd] [ 5:10:54.02][ChkError.cmd] -------------------------------------------------- [ 5:10:54.07][ChkError.cmd] [ChkError.cmd] has completed... [ 5:10:54.10][ChkError.cmd] ************************************************** [ 5:11:31.23] ------------------------------------------------------------ [ 5:11:31.23] [31/03/2018] [ 5:11:31.23] Windows has detected critical error and has triggered ErrorHandler.cmd. [ 5:11:31.23] [ 5:11:31.23] Possible cause[s]: [ 5:11:31.23] - got critical error during Specialize-Pass. [ 5:11:31.23] Check [C:\Windows\Panther\setupact.log] for this case. [ 5:11:31.23] - got critical error during Audit-Pass. [ 5:11:31.23] Check [C:\Windows\Panther\UnattendGC\setupact.log] for this case. [ 5:11:31.23] - got critical error during SysPrep. [ 5:11:31.23] Check [C:\Windows\System32\Sysprep\Panther\setupact.log] for this case. [ 5:11:31.23] [ 5:11:31.23] [ 5:11:31.24] ------------------------------------------------------------ [ 7:28:38.81] ------------------------------------------------------------ [ 7:28:38.81] [31/03/2018] [ 7:28:38.81] Windows has detected critical error and has triggered ErrorHandler.cmd. [ 7:28:38.81] [ 7:28:38.81] Possible cause[s]: [ 7:28:38.81] - got critical error during Specialize-Pass. [ 7:28:38.81] Check [C:\Windows\Panther\setupact.log] for this case. [ 7:28:38.81] - got critical error during Audit-Pass. [ 7:28:38.81] Check [C:\Windows\Panther\UnattendGC\setupact.log] for this case. [ 7:28:38.81] - got critical error during SysPrep. [ 7:28:38.81] Check [C:\Windows\System32\Sysprep\Panther\setupact.log] for this case. [ 7:28:38.81] [ 7:28:38.82] [ 7:28:38.82] ------------------------------------------------------------ [ 7:31:17.13] ------------------------------------------------------------ [ 7:31:17.13] [31/03/2018] [ 7:31:17.13] Windows has detected critical error and has triggered ErrorHandler.cmd. [ 7:31:17.13] [ 7:31:17.14] Possible cause[s]: [ 7:31:17.14] - got critical error during Specialize-Pass. [ 7:31:17.14] Check [C:\Windows\Panther\setupact.log] for this case. [ 7:31:17.14] - got critical error during Audit-Pass. [ 7:31:17.14] Check [C:\Windows\Panther\UnattendGC\setupact.log] for this case. [ 7:31:17.14] - got critical error during SysPrep. [ 7:31:17.14] Check [C:\Windows\System32\Sysprep\Panther\setupact.log] for this case. [ 7:31:17.14] [ 7:31:17.14] [ 7:31:17.15] ------------------------------------------------------------ [ 7:35:04.03] ------------------------------------------------------------ [ 7:35:04.03] [31/03/2018] [ 7:35:04.03] Windows has detected critical error and has triggered ErrorHandler.cmd. [ 7:35:04.03] [ 7:35:04.04] Possible cause[s]: [ 7:35:04.04] - got critical error during Specialize-Pass. [ 7:35:04.04] Check [C:\Windows\Panther\setupact.log] for this case. [ 7:35:04.04] - got critical error during Audit-Pass. [ 7:35:04.04] Check [C:\Windows\Panther\UnattendGC\setupact.log] for this case. [ 7:35:04.04] - got critical error during SysPrep. [ 7:35:04.04] Check [C:\Windows\System32\Sysprep\Panther\setupact.log] for this case. [ 7:35:04.04] [ 7:35:04.04] [ 7:35:04.04] ------------------------------------------------------------ [ 7:48:43.58] ------------------------------------------------------------ [ 7:48:43.58] [31/03/2018] [ 7:48:43.58] Windows has detected critical error and has triggered ErrorHandler.cmd. [ 7:48:43.58] [ 7:48:43.58] Possible cause[s]: [ 7:48:43.58] - got critical error during Specialize-Pass. [ 7:48:43.58] Check [C:\Windows\Panther\setupact.log] for this case. [ 7:48:43.58] - got critical error during Audit-Pass. [ 7:48:43.58] Check [C:\Windows\Panther\UnattendGC\setupact.log] for this case. [ 7:48:43.58] - got critical error during SysPrep. [ 7:48:43.59] Check [C:\Windows\System32\Sysprep\Panther\setupact.log] for this case. [ 7:48:43.59] [ 7:48:43.59] [ 7:48:43.59] ------------------------------------------------------------ [ 7:54:49.49] ------------------------------------------------------------ [ 7:54:49.49] [31/03/2018] [ 7:54:49.49] Windows has detected critical error and has triggered ErrorHandler.cmd. [ 7:54:49.49] [ 7:54:49.49] Possible cause[s]: [ 7:54:49.49] - got critical error during Specialize-Pass. [ 7:54:49.49] Check [C:\Windows\Panther\setupact.log] for this case. [ 7:54:49.49] - got critical error during Audit-Pass. [ 7:54:49.49] Check [C:\Windows\Panther\UnattendGC\setupact.log] for this case. [ 7:54:49.49] - got critical error during SysPrep. [ 7:54:49.49] Check [C:\Windows\System32\Sysprep\Panther\setupact.log] for this case. [ 7:54:49.49] [ 7:54:49.49] [ 7:54:49.50] ------------------------------------------------------------ [ 7:57:02.10] ------------------------------------------------------------ [ 7:57:02.10] [31/03/2018] [ 7:57:02.10] Windows has detected critical error and has triggered ErrorHandler.cmd. [ 7:57:02.10] [ 7:57:02.10] Possible cause[s]: [ 7:57:02.10] - got critical error during Specialize-Pass. [ 7:57:02.10] Check [C:\Windows\Panther\setupact.log] for this case. [ 7:57:02.10] - got critical error during Audit-Pass. [ 7:57:02.10] Check [C:\Windows\Panther\UnattendGC\setupact.log] for this case. [ 7:57:02.10] - got critical error during SysPrep. [ 7:57:02.10] Check [C:\Windows\System32\Sysprep\Panther\setupact.log] for this case. [ 7:57:02.10] [ 7:57:02.10] [ 7:57:02.12] ------------------------------------------------------------ [18:30:16.74] ------------------------------------------------------------ [18:30:16.74] [19/04/2018] [18:30:16.74] Windows has detected critical error and has triggered ErrorHandler.cmd. [18:30:16.74] [18:30:16.74] Possible cause[s]: [18:30:16.74] - got critical error during Specialize-Pass. [18:30:16.74] Check [C:\Windows\Panther\setupact.log] for this case. [18:30:16.74] - got critical error during Audit-Pass. [18:30:16.74] Check [C:\Windows\Panther\UnattendGC\setupact.log] for this case. [18:30:16.74] - got critical error during SysPrep. [18:30:16.74] Check [C:\Windows\System32\Sysprep\Panther\setupact.log] for this case. [18:30:16.74] [18:30:16.74] [18:30:16.75] ------------------------------------------------------------ [18:33:36.27] ------------------------------------------------------------ [18:33:36.27] [19/04/2018] [18:33:36.27] Windows has detected critical error and has triggered ErrorHandler.cmd. [18:33:36.27] [18:33:36.27] Possible cause[s]: [18:33:36.27] - got critical error during Specialize-Pass. [18:33:36.27] Check [C:\Windows\Panther\setupact.log] for this case. [18:33:36.27] - got critical error during Audit-Pass. [18:33:36.27] Check [C:\Windows\Panther\UnattendGC\setupact.log] for this case. [18:33:36.27] - got critical error during SysPrep. [18:33:36.28] Check [C:\Windows\System32\Sysprep\Panther\setupact.log] for this case. [18:33:36.28] [18:33:36.28] [18:33:36.28] ------------------------------------------------------------
File created by the HP Recovery program Manager.
https://yadi.sk/d/S5RtFrsB3UauLr
Solved! Go to Solution.
Accepted Solutions
04-19-2018 09:48 PM
Have you created HP recovery USB using HP recovery manager software just after initial setup of this notebook?
If so, use this to boot from and perform factory reset.
Keep notebook plugged in to AC power. Remove all peripheral devices except HP recovery media. Close all other programs other than Recovery.
Nevertheless, if you desire, you can clean install Windows 10 in this notebook by creating UEFI bootable Windows 10 installation USB using Microsoft Windows media creation tool.
Windows will be automatically activated after installation while connected to internet
You can try the below steps to clean install Windows 10 latest build,
Follow option 1 here: https://www.tenforums.com/tutorials/2376-create-bootable-usb-flash-drive-install-windows-10-a.html
This will allow you create bootable Windows 10 (build 1709) USB using Microsoft windows media creation tool from ANOTHER WORKING COMPUTER.
Next disable secure boot from BIOS, plug in the installation USB, change boot order to USB, then proceed with clean installation of Windows 10 1709 build.
Disable secure boot:
https://support.hp.com/in-en/document/c04784866
Change boot order to USB: https://support.hp.com/in-en/document/c01443326
Clean install:
https://www.tenforums.com/tutorials/1950-clean-install-windows-10-a.html
Windows 10 activation licence key is embedded in the BIOS chip on motherboard from factory. The key automatically activates Windows 10 upon installation while connected to internet, provided you're installing same edition i.e., Windows 10 Home.
You can download additional drivers from your HP support page:
https://support.hp.com/in-en/drivers/selfservice/hp-pavilion-14-ba100-x360-convertible-pc/16851098
04-19-2018 09:48 PM
Have you created HP recovery USB using HP recovery manager software just after initial setup of this notebook?
If so, use this to boot from and perform factory reset.
Keep notebook plugged in to AC power. Remove all peripheral devices except HP recovery media. Close all other programs other than Recovery.
Nevertheless, if you desire, you can clean install Windows 10 in this notebook by creating UEFI bootable Windows 10 installation USB using Microsoft Windows media creation tool.
Windows will be automatically activated after installation while connected to internet
You can try the below steps to clean install Windows 10 latest build,
Follow option 1 here: https://www.tenforums.com/tutorials/2376-create-bootable-usb-flash-drive-install-windows-10-a.html
This will allow you create bootable Windows 10 (build 1709) USB using Microsoft windows media creation tool from ANOTHER WORKING COMPUTER.
Next disable secure boot from BIOS, plug in the installation USB, change boot order to USB, then proceed with clean installation of Windows 10 1709 build.
Disable secure boot:
https://support.hp.com/in-en/document/c04784866
Change boot order to USB: https://support.hp.com/in-en/document/c01443326
Clean install:
https://www.tenforums.com/tutorials/1950-clean-install-windows-10-a.html
Windows 10 activation licence key is embedded in the BIOS chip on motherboard from factory. The key automatically activates Windows 10 upon installation while connected to internet, provided you're installing same edition i.e., Windows 10 Home.
You can download additional drivers from your HP support page:
https://support.hp.com/in-en/drivers/selfservice/hp-pavilion-14-ba100-x360-convertible-pc/16851098
04-20-2018 03:53 PM
1. I would like to know why this error arose? The system was recharged for the first time. And the first time recovery, there was this error.
2. And how often does the error happen?
3. And how can you solve the problem by the means that are in the laptop?
4. When deciding the question, according to the above answer, I want to say that the recovery partition and all data will be deleted from the disk.
5. What do I need to create a recovery partition?
04-20-2018 04:22 PM
Usually this happens when HP Recovery partition gets corrupted, which can be due to:
Windows feature upgrades that Microsoft is pushing every 6 months
Saving any other files into HP recovery partition than what is originally present in it
Changing partition system of the hard drive
This can also happen when during the HP system recovery: other external peripheral devices were connected, laptop was not plugged in to AC adapter power, any other background processes were running other than recovery etc.
Once HP recovery partition is corrupted, you cannot successfully complete recovery process. It would result in definite failure.
Few ways: Keep in mind the points given above and Tap away f11 key as soon as you power on notebook, enter HP Recovery console and perform factory reset. If there is a corrupted HP recovery partition to start with, this process will also fail.
You ought to have created HP recovery USB using HP recovery manager software just after initial setup of the notebook. This USB can also be used to do factory reset by booting from it.
Doing a clean installation of Windows 10 will format/delete everything in the hard drive and give you bare Windows 10 operating system without any HP drivers or softwares or HP recovery partition. You've to download the additional drivers from HP support page linked in my previous post. You cannot get HP recovery partition once it is gone, unless you order them directly from HP technical support specific to your model.
04-21-2018 03:03 AM
Here: https://support.hp.com/in-en/contact-hp/product/HP-Pavilion-14-ba100-x360-Convertible-PC/16851098
Phone assist: http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html
Get Recovery USB compatible with your specific model.
04-21-2018 04:34 AM
You've request the the official technical support team. This is not the official HP technical support. This is a peer-to-peer public support forum where all the members are end users like you.
I would not spend my money for HP recovery media for all that HP stuff. I can easily do a clean install of Windows 10 following above steps and later download the required drivers and softwares from support page directly.