Windows 10: Can't upgrade to Win10 2004 - at 57% BFSVC dies

Discus and support Can't upgrade to Win10 2004 - at 57% BFSVC dies in Windows 10 Installation and Upgrade to solve the problem; I'm trying to upgrade from 1909 to 2004. I'm seeing error code 0x80242016 in the settings "view update history" panel. It's the same error I've been... Discussion in 'Windows 10 Installation and Upgrade' started by KevinPNeal, Sep 14, 2020.

  1. KEVINPNEAL
    KevinPNeal Win User

    Can't upgrade to Win10 2004 - at 57% BFSVC dies


    I'm trying to upgrade from 1909 to 2004. I'm seeing error code 0x80242016 in the settings "view update history" panel. It's the same error I've been seeing for months. The upgrade proceeds, and then the percent down goes up to 57% before it says "restarting" and reboots me back into my old install.


    I've tried everything that I can get my hands on that looks like it might be helpful. I've used chkdsk, sfc, several others. I've tried clean boots. I've cleaned out caches. I really have no idea what to try next.


    This is my "work from home" machine, so I need to avoid down time as much as possible. I really don't want to spend a day reinstalling everything I need to get $DAYJOB done.


    I'd appreciate any help. TIA!


    I do have a log file that ends with this:

    2020-08-08 18:52:33, Info SP BFSVC: BfsInitializeBcdStore flags0x00001008 RetainElementData:n DelExistinObject:n

    2020-08-08 18:52:33, Info SP BFSVC: VolumePathName for C:\$WINDOWS.~BT\NewOS\WINDOWS is C:\

    2020-08-08 18:52:33, Info SP BFSVC: Opening template from \Device\HarddiskVolume4\$WINDOWS.~BT\NewOS\WINDOWS\System32\config\BCD-Template.

    2020-08-08 18:52:33, Info MOUPG Action: 57%, Delta: 18.22s, 57 ticks, Avg: 3.129 ticks/s

    2020-08-08 18:52:33, Info MOUPG Action progress: [57%]

    2020-08-08 18:52:33, Info MOUPG Task progress: [57%]

    2020-08-08 18:52:33, Info MOUPG Overall progress: [57%]

    2020-08-08 18:52:33, Info MOUPG Mapped Global progress: [57%]

    2020-08-08 18:52:33, Info SP BFSVC: Reopening system store.

    2020-08-08 18:52:33, FatalError SP Exception handler called! Details:

    2020-08-08 18:52:33, FatalError SP Exception record: 0

    2020-08-08 18:52:33, FatalError SP Exception code: 0xc0000005

    2020-08-08 18:52:33, FatalError SP Exception flags: 0x0

    2020-08-08 18:52:33, FatalError SP Exception address: 00007FFDCCEAD25D

    2020-08-08 18:52:33, FatalError SP Exception parameter 0: 0000000000000000

    2020-08-08 18:52:33, FatalError SP Exception parameter 1: 0000000000000000

    2020-08-08 18:52:33, Info SP SEH: Attempting to log exception

    2020-08-08 18:52:34, FatalError [0x090001] PANTHR Exception code 0xC0000005: ACCESS_VIOLATION occurred at 0x00007FFDCCEAD25D in C:\$WINDOWS.~BT\Sources\SetupPlatform.dll +00000000003ED25D. Minidump attached 135008 bytes to diagerr.xml and C:\$WINDOWS.~BT\Sources\Panther\mnd17C2.diagerr.mdmp.

    2020-08-08 18:52:34, Info SP SEH: Attempting to upload diagnostic data

    2020-08-08 18:52:34, Info SP Try to merge diagnostics data from default new system data file

    2020-08-08 18:52:34, Info Initializing diagnostics helper; data file = C:\$WINDOWS.~BT\Sources\Diagnostics\diagnostics.dat

    2020-08-08 18:52:34, Info Found existing diagnostics data, attempting to load it.

    2020-08-08 18:52:34, Info Merging diagnostics data for WatsonBucket

    2020-08-08 18:52:34, Info Merging diagnostics data success

    2020-08-08 18:52:34, Info SP Finish merge diagnostics data

    2020-08-08 18:52:34, Info DIAGER DiagERInitialize:Entry Also Initialized the log

    2020-08-08 18:52:34, Info DIAGER IDiagER::IDiagER:Entry

    2020-08-08 18:52:34, Info DIAGER CWfpER::Initialize:Entry

    2020-08-08 18:52:34, Info DIAGER CWfpER::Initialize:Entry

    2020-08-08 18:52:34, Info DIAGER Consent Value = HKCU\Software\Microsoft\Windows\Windows Error Reporting\Consent!WinSetupDiag02 has been set to 4

    2020-08-08 18:52:34, Info DIAGER DiagERAddBucketingParameters:Entry

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddBucketingParameters:Entry

    2020-08-08 18:52:34, Info DIAGER IDiagER::AddBucketingParameters:Entry

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=X

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=X

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=9

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=X

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=X

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=X

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=18363

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=X

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=19041

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddBucketingParameters:Adding bucketing param=vb_release

    2020-08-08 18:52:34, Info DIAGER DiagERSetHeader:Entry

    2020-08-08 18:52:34, Info DIAGER CWfpER::SetHeader:Entry

    2020-08-08 18:52:34, Info DIAGER IDiagER::SetHeader:Entry

    2020-08-08 18:52:34, Info DIAGER CWfpER::SetHeader:Setting header=Microsoft Windows Installation encountered a problem and needs to close. We are sorry for the inconvenience

    2020-08-08 18:52:34, Info CDiagnosticsHelper::GetWatsonFilesToAttach: Attaching file C:\$WINDOWS.~BT\Sources\Panther\SetupAct.log

    2020-08-08 18:52:34, Info CDiagnosticsHelper::GetWatsonFilesToAttach: Attaching file C:\$WINDOWS.~BT\Sources\Panther\diagerr.xml

    2020-08-08 18:52:34, Info DIAGER DiagERAddFiles:Entry

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddFiles:Entry

    2020-08-08 18:52:34, Info DIAGER IDiagER::AddFiles:Entry

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddFiles:Adding file=C:\$WINDOWS.~BT\Sources\Panther\SetupAct.log

    2020-08-08 18:52:34, Info DIAGER CWfpER::AddFiles:Adding file=C:\$WINDOWS.~BT\Sources\Panther\diagerr.xml

    2020-08-08 18:52:34, Info DIAGER DiagERSubmitEx:Entry

    2020-08-08 18:52:34, Info DIAGER CWfpER::Submit:Entry

    2020-08-08 18:52:34, Info DIAGER Watson Error Report submitted and Result=2

    2020-08-08 18:52:34, Info DIAGER DiagERTerminate:Entry

    2020-08-08 18:52:34, Info DIAGER CWfpER::~CWfpER:Entry

    2020-08-08 18:52:34, Info DIAGER Consent Value = HKCU\Software\Microsoft\Windows\Windows Error Reporting\Consent!WinSetupDiag02 has been cleaned out

    2020-08-08 18:52:34, Info DIAGER IDiagER::~IDiagER:Entry

    2020-08-08 18:52:34, Info SP SEH: Attempting to process telemetry

    2020-08-08 18:52:35, Info SP SEH: Attempting to clean up failed installation

    2020-08-08 18:52:35, Info SP SEH: One-time exception handling is enabled. De-activating.

    2020-08-08 18:52:35, FatalError [0x090001] PANTHR Exception code 0xC0000005: ACCESS_VIOLATION occurred at 0x00007FFDCCEAD25D in C:\$WINDOWS.~BT\Sources\SetupPlatform.dll +00000000003ED25D. Minidump attached 150078 bytes to diagerr.xml and C:\Windows\Minidump\mnd1CA7.diagerr.mdmp.

    :)
     
    KevinPNeal, Sep 14, 2020
    #1
  2. Y.REZAIE
    Y.Rezaie Win User

    upgrade from win10 build 1909 to build 2004.....

    hello i want to upgrade from win10 build 1909 to build 2004. how can i do it?

    or build 2004 is released?
     
    Y.Rezaie, Sep 14, 2020
    #2
  3. SIMONESERRA
    simoneserra Win User
    Error0x80004005 when upgrading Windows 10 1909 to 2004

    Hello,

    I have been trying to upgrade my system from 1909 to Windows 10 2004 but failed at several attempts with error code 0x80004005.

    I then tried with the Upgrade assistant and in c:\Windows\Logs\MoSetup\BlueBox.log I see the followiong error:

    Code:
     BFSVC: BfsRepairSystemPartition flags(0x00000050), system root: C:\Windows, online: False, boot files: None, caller: 3

BFSVC Error: BfsRepair: System volume too large for chkdsk. Size: 121619 MB Max: 1024 MB
I cannot find any reference about it online .
    Thanks
     
    simoneserra, Sep 14, 2020
    #3
  4. OLDNAVYGUY
    OldNavyGuy Win User

    Can't upgrade to Win10 2004 - at 57% BFSVC dies

    OldNavyGuy, Sep 14, 2020
    #4
Thema:

Can't upgrade to Win10 2004 - at 57% BFSVC dies

Loading...

  1. Can't upgrade to Win10 2004 - at 57% BFSVC dies - Similar Threads - Can't upgrade Win10

  2. win10 2004

    in Windows 10 Customization
    win10 2004: Twitchtwitch https://answers.microsoft.com/en-us/windows/forum/all/win10/0d6064e7-9ec6-4a5f-bb29-8a87b356ab36

  3. Can't upgrade to 2004 or 20H2

    in Windows 10 Installation and Upgrade
    Can't upgrade to 2004 or 20H2: Hi, For several months now, I've been getting offered the W10 2004 update, and it's always failed to install. Today I got offered the 20H2 update and that also failed. I've run SetupDiag and the results are: Error: SetupDiag reports rollback failure found. Last Phase =...

  4. can't upgrade to 2004 update in my win10 pc

    in Windows 10 Installation and Upgrade
    can't upgrade to 2004 update in my win10 pc: hello i bought a new computer of BMAX company who comes with win10 build in. i tried to upgrade to the 2004 update but the tool say "this pc can't be upgraded to windows 10. your pc isn't supported yet on this version of windows 10..." some ideas to solve it?...

  5. WIN10-2004 Security Can't Delete Virus

    in AntiVirus, Firewalls and System Security
    WIN10-2004 Security Can't Delete Virus: First, fix the Feedback Hub. I got tired of watched the six dots circle on my screen. My computer has a serious problem with how WIN10-2004 handles viruses. It complained that I had several viruses associated within the same sub-folder of the parent folder. I selected...

  6. WIN10 BEFORE & AFTER UPGRADE 2004: PRINTING PROBLEMS

    in Windows 10 Drivers and Hardware
    WIN10 BEFORE & AFTER UPGRADE 2004: PRINTING PROBLEMS: I am running Win10 x64 Pro desktop. Before the above: NO PROBLEMS!! After the upgrade: my PC and my HP OJ3833 wireless printer do not get along. 1 I choose the doc I want to print 2 Check 'File' 3 Check 'Print' 4 Printer screen returns 'print preview'; printer 'on...

  7. Win10 upgrade to 2004 error 0xC1900101-0x30018

    in Windows 10 Installation and Upgrade
    Win10 upgrade to 2004 error 0xC1900101-0x30018: hey all... I used the media creation tool to create a USB version Win10 2004 setup to upgrade my 1909 PC. After the long setup, the reboot failed and a rollback occurred. Ideas? setuperr.log has every event failing. So, I have nowhere or everywhere to point to. I am...

  8. win10 2004

    in Windows 10 Customization
    win10 2004: ?.?.. https://answers.microsoft.com/en-us/windows/forum/all/win10/391f881f-9cdc-4a8b-854d-94df7a204a56

  9. upgrade from win10 build 1909 to build 2004.....

    in Windows 10 Installation and Upgrade
    upgrade from win10 build 1909 to build 2004.....: hello i want to upgrade from win10 build 1909 to build 2004. how can i do it? or build 2004 is released? https://answers.microsoft.com/en-us/windows/forum/all/upgrade-from-win10-build-1909-to-build-2004/0784af86-c674-4b56-a2e8-9f52e84bf38d

  10. This pc can't be upgraded to WIN10

    in Windows 10 Installation and Upgrade
    This pc can't be upgraded to WIN10: Last few days, my pc gets updates prompt, but always freezes and failed to complete the update when I activated the update. So I had to forced restart it and PC undoing the changes made. I don't know what is this issue. This problem now re-appears after more than one year....