Share via

Windows 10 Home update failed with Failed execution of queue item Installer: Boot File Servicing (BFSVC) Installer from CBS log

Anonymous
2023-05-11T01:35:02+00:00

I've been experiencing non-stop Windows cumulative update failed since February and just can't fix it.

none of the solution in internet is working from :

  • using windows update troubleshooter
  • DISM,
  • SFC scan,
  • chkdsk command,
  • manually downloading and installing update from Windows Catalog,
  • Windows Update files reset

I'm not a tech worker so I don't know what's wrong and just recently discover there's CBS log and I checked that and found this error:

2023-05-11 06:53:34, Error [0x018049] CSI 00000b10 (F) Failed execution of queue item Installer: Boot File Servicing (BFSVC) Installer ({c5f0e9d7-e844-4507-89e4-701b5a747221}) with HRESULT 8031004a [Error,Facility=(0031),Code=74 (0x004a)]. Failure will be ignored: The failure was encountered during rollback; installer is reliable[gle=0x80004005]

2023-05-11 06:53:34, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]

2023-05-11 06:53:34, Info CBS Could not get file name for current session file logging [HRESULT = 0x80004003 - E_POINTER]

2023-05-11 06:53:35, Info CBS Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.

2023-05-11 06:53:35, Info CBS Startup: Changing logon timeout to a static timeout: 10800000

2023-05-11 06:53:36, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20230510225411.log to WER report.

2023-05-11 06:53:36, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20230507091652.cab to WER report.

2023-05-11 06:53:36, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20230429140639.cab to WER report.

2023-05-11 06:53:36, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20230429015406.cab to WER report.

2023-05-11 06:53:36, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2023-05-11 06:53:36, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2023-05-11 06:55:16, Info CSI 00000b11 Begin executing advanced installer phase 31 index 0 (sequence 0)

and I didn't know how to resolve it, there's one guide on the internet about repairing EFI bootloader but I didn't know how to do it since it's very complicated. I CAN'T JUST REINSTALL THE WINDOWS AS A SOLUTION because since I've had my first PC every windows error solutions are always reinstall reinstall reinstall, there's too many files to backup and I did not have any drives to back them up and there's also a lot of app that require some specific configuration that's just take forever to redo them all

please if you have any solutions beside reinstall it would be very much appreciated, if not then I'll just run my Windows without cumulative update for indefinite time

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

12 answers

Sort by: Most helpful
  1. Ramesh 176.3K Reputation points Volunteer Moderator
    2023-05-11T10:51:53+00:00

    The is no evidence from the log that the EFI boot partition is corrupt. However, it encounters the error 8031004a when servicing the boot files. The error code is a Bitlocker-related error.

    FVE_E_NOT_ON_STACK 0x8031004A BitLocker Drive Encryption cannot be used because critical BitLocker system files are missing or corrupted. Use Windows Startup Repair to restore these files to your computer.

    What's the status of Bitlocker on the computer?

    Please upload your System event log. It's located at "C:\windows\system32\winevt\Logs\System.evtx".

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-05-11T10:35:08+00:00

    Sorry for the late reply, I have tried to do a recovery from Windows Recovery Environment using the recovery option on setting and not bootable disk following guide online but the guide on Microsoft official page and non official site tells me to open the command prompt after getting into Windows Environment Recovery but after I click it the PC just normally restart and didn't open any command prompt

    Here's the CBS files:
    CBS.zip

    and here's the screenshot of Disk Management:

    Screenshot (669).png

    do I need to create bootable disk for this

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-05-11T10:30:38+00:00

    Sorry for the late reply

    here's the CBS files, I've zipped the folder:

    CBS.zip

    Was this answer helpful?

    0 comments No comments
  4. Ramesh 176.3K Reputation points Volunteer Moderator
    2023-05-11T03:26:20+00:00

    and I didn't know how to resolve it, there's one guide on the internet about repairing EFI bootloader but I didn't know how to do it since it's very complicated.

    The EFI boot partition can be rebuilt easily using a set of commands via the Windows Recovery Environment. It's a simple procedure. Will post further details after seeing your CBS logs.

    I CAN'T JUST REINSTALL THE WINDOWS AS A SOLUTION because since I've had my first PC every windows error solutions are always reinstall reinstall reinstall, there's too many files to backup and I did not have any drives to back them up and there's also a lot of app that require some specific configuration that's just take forever to redo them all

    A repair install will likely fail if the file system is corrupt in the EFI boot partition. Please zip and upload all the .log files in the "c:\windows\logs\cbs" to your OneDrive and share the link here. Also, post a full screenshot of your Disk Management window.

    Was this answer helpful?

    0 comments No comments
  5. Sumit D - IA 170.4K Reputation points Independent Advisor
    2023-05-11T02:07:49+00:00

    Hi Muhammad,

    I'm Sumit, here to answer your query at the Microsoft Community.

    Can you share the whole CBS.log file through Onedrive? It will be best if you try an update once, let it fail and then immediately share CBS log.

    If it is too big, please ZIP it and then share.

    I look forward to your answer.

    Was this answer helpful?

    0 comments No comments