Windows 10 Feature Update 20H2 consistently fails with 0x80242016

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 223
    Windows 10
    Thread Starter
       #11

    jaburmester said:
    Tuneup_Plus_Logfiles are attachech Attachment 324961
    Upgrade_failure_info files cannot be uploaded due to size.
    Can you please suggest how to upload Upgrade_failure_info files.
    Thank you for all help given
    Please see Dropbox - Errors - Simplify your life for results from Tuneup_plus_log.bat and Update_failure_info.bat.

    Thank you for all help.
      My Computer


  2. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit
       #12

    Please follow the instructions for tuneup:
    Batch files for use in BSOD debugging
    Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.






    If you're not able to follow them please indicate the part that is not understood,
    If the instructions need to be modified please comment.
      My Computer


  3. Posts : 223
    Windows 10
    Thread Starter
       #13

    zbook said:
    Please follow the instructions for tuneup:
    Batch files for use in BSOD debugging
    Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.






    If you're not able to follow them please indicate the part that is not understood,
    If the instructions need to be modified please comment.
    Please see Dropbox - Errors - Simplify your life

    Thank you for all help.
      My Computer


  4. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit
       #14

    The logs displayed recent BSOD.

    Please run V2 and DM:
    BSOD - Posting Instructions


    1) Open administrative command prompt (ACP) and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) wmic recoveros set DebugInfoType = 7
    9) wmic recoveros get autoreboot
    10) wmic recoveros get DebugInfoType
    11) wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
    12) wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
    13) bcdedit /enum {badmemory}

    14) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    Use this link as needed when posting results:
    How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com



    15) Uninstall VIPRE Advanced Security using the applicable uninstall tool:

    How to remove/uninstall VIPRE : Support.

    VIPRE Removal Tool (Business Agents) : VIPRE Business & VIPRE Business Premium

    16) Uninstall Malwarebytes using the applicable uninstall tool:
    https://downloads.malwarebytes.com/file/mb_clean

    16) Make sure Microsoft defender is on
      My Computer


  5. Posts : 223
    Windows 10
    Thread Starter
       #15

    zbook said:
    The logs displayed recent BSOD.

    Please run V2 and DM:
    BSOD - Posting Instructions


    1) Open administrative command prompt (ACP) and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) wmic recoveros set DebugInfoType = 7
    9) wmic recoveros get autoreboot
    10) wmic recoveros get DebugInfoType
    11) wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
    12) wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
    13) bcdedit /enum {badmemory}

    14) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    Use this link as needed when posting results:
    How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com



    15) Uninstall VIPRE Advanced Security using the applicable uninstall tool:

    How to remove/uninstall VIPRE : Support.

    VIPRE Removal Tool (Business Agents) : VIPRE Business & VIPRE Business Premium

    16) Uninstall Malwarebytes using the applicable uninstall tool:
    https://downloads.malwarebytes.com/file/mb_clean

    16) Make sure Microsoft defender is on
    Please see Dropbox - Errors - Simplify your life for V2 and DM results.

    Please note I have had
    VIPRE Advanced Security and Malwarebytes for years and do not understand why I should uninstall it.
      My Computer


  6. Posts : 821
    Win 10
       #16

    @jaburmester

    The installation failed with error code 0x80070013 what means: Error media write protect.

    2021-03-28 06:51:52, Error SP CAddBootEntry: Failure while adding the boot entry. Error: 0x80070013[gle=0x00000013]
    2021-03-28 06:51:52, Error SP Operation failed: Add boot entry for C:\$WINDOWS.~BT\NewOS\WINDOWS. Locale = en-GB. Error: 0x80070013[gle=0x000000b7]
    2021-03-28 06:51:52, Error SP ExecuteOperations: Failed execution phase Finalize. Error: 0x80070013
    2021-03-28 06:51:52, Error MOUPG MoSetupPlatform: Finalize reported failure!
    2021-03-28 06:51:52, Error MOUPG MoSetupPlatform: Using action error code: [0x80070013]
    2021-03-28 06:51:52, Error MOUPG CDlpActionFinalize::ExecuteSetupPlatformFinalize(1120): Result = 0x80070013
    2021-03-28 06:51:52, Error MOUPG CDlpActionFinalize::ExecuteRoutine(510): Result = 0x80070013
    2021-03-28 06:51:53, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Execute(493): Result = 0x80070013


    Uninstall Vipre Advanced Security temporary and then use the removal tool too:
    Download VIPRE Removal Tool 12.0.0.28

    When done, uninstall Malwarebytes temporary and use the Malwarebytes Removal tool to:
    https://downloads.malwarebytes.com/file/mbst

    Answers the “Reinstall Malwarebytes for Windows” Window with no.

    Then try the update with a 20h2 install media again.

    Friendly greetings
      My Computer


  7. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit
       #17

    Please fix the BSOD before the upgrade.
      My Computer


  8. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit
       #18

    Non-Microsoft antivirus software, firewall software, and drive encryption software are well known problems with Windows upgrades.
    The logs displayed problems with both software (WER).


    1) Make a new restore point:
    Create System Restore Point in Windows 10

    2) Open administrative command prompt (ACP) and type or copy and paste:

    3) reagentc /enable
    4) reagentc /info

    5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    6) Open Ccleaner > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

    7) update the progress with the steps in post #14





    8) Read these links on Windows driver verifier:

    a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

    b) do not use the tool until it is communicated in the thread


    Enable and Disable Driver Verifier in Windows 10
    https://answers.microsoft.com/en-us/...3-c48669e4c983

    Windows driver verifier is designed to stress test drivers.

    If there are misbehaving drivers the computer will crash.

    If dump files are created they can be debugged.

    Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

    The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

    If there are no further BSOD this concludes the use of the tool.

    After each BSOD you must turn off the tool in order to return to the desktop.

    Learn the Windows RE commands reset and bootmode.

    These are run in safe mode or safe mode with command prompt.

    In case these fail the next option is system restore.

    If system restore fails you can restore a backup image or use registry commands.

    Start the tool with the 3 customized test settings in the Ten Forums link.

    Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

    There can be performance problems and / or slow boot while using the tool.

    If necessary the customized test settings can be modified.

    Summary:
    a) make a new restore point
    b) test all non-Microsoft drivers
    c) test no Microsoft drivers
    d) after each BSOD use the reset command to turn off the tool
    e) if the reset command does not work then use the bootmode command
    f) only if both reset and bootmode command fail to turn off the tool then use restore
    g) start with the 3 customized test settings in the Ten Forums link
    h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
    i) report any performance problems or very slow boot so that the customized settings can be modified


    Code:
    Event[38229]:
      Log Name: System
      Source: Microsoft-Windows-WHEA-Logger
      Date: 2021-04-13T09:48:41.612
      Event ID: 3
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: WHEA Error Event Logs
      User: S-1-5-19
      User Name: NT AUTHORITY\LOCAL SERVICE
      Computer: SurfacePro4
      Description: 
    A hardware event has occurred. An informational record describing the condition is contained in the data section of this event.

    Code:
    Event[38122]:
      Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2021-04-07T02:28:30.207
      Event ID: 1001
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: SurfacePro4
      Description: 
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x0000000000000028, 0x0000000000000002, 0x0000000000000000, 0xfffff8073c8e8e85). A dump was saved in: C:\windows\Minidump\040721-21406-01.dmp. Report Id: 85c49d92-2bc8-4d22-9ce0-ca67947c6af5.

    Code:
    Windows Error Reporting:
    +++ WER0 +++:
    Fault bucket 1781117006522445390, type 4
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: mbamtray.exe
    P2: 4.0.0.974
    P3: 607861f0
    P4: Qt5Core.dll
    P5: 5.14.1.0
    P6: 603971ce
    P7: c0000005
    P8: 0000000000219dc5
    P9: 
    P10: 
    
    
    +++ WER1 +++:
    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: mbamtray.exe
    P2: 4.0.0.974
    P3: 607861f0
    P4: Qt5Core.dll
    P5: 5.14.1.0
    P6: 603971ce
    P7: c0000005
    P8: 0000000000219dc5
    P9: 
    P10:

    Code:
    4/7/2021 1:18 AM	Application Error	Faulting application name: VipreEdgeProtection.exe, version: 3.0.0.29, time stamp: 0x5b8653c4&#x000d;&#x000a;Faulting module name: combase.dll, version: 10.0.18362.1411, time stamp: 0xb445b2a6&#x000d;&#x000a;Exception code: 0xc0000005&#x000d;&#x000a;Fault offset: 0x000000000006f8f0&#x000d;&#x000a;Faulting process ID: 0x45a4&#x000d;&#x000a;Faulting application start time: 0x01d726e42cddeaa3&#x000d;&#x000a;Faulting application path: C:\Program Files (x86)\VIPRE\VipreEdgeProtection.exe&#x000d;&#x000a;Faulting module path: C:\windows\System32\combase.dll&#x000d;&#x000a;Report ID: aea3c08e-8b23-462c-810f-4ce740be2c31&#x000d;&#x000a;Faulting package full name: &#x000d;&#x000a;Faulting package-relative application ID:
    4/1/2021 10:45 AM	Application Error	Faulting application name: VipreEdgeProtection.exe, version: 3.0.0.29, time stamp: 0x5b8653c4&#x000d;&#x000a;Faulting module name: combase.dll, version: 10.0.18362.1411, time stamp: 0xb445b2a6&#x000d;&#x000a;Exception code: 0xc0000005&#x000d;&#x000a;Fault offset: 0x000000000006f8f0&#x000d;&#x000a;Faulting process ID: 0x3464&#x000d;&#x000a;Faulting application start time: 0x01d72396dcec3314&#x000d;&#x000a;Faulting application path: C:\Program Files (x86)\VIPRE\VipreEdgeProtection.exe&#x000d;&#x000a;Faulting module path: C:\windows\System32\combase.dll&#x000d;&#x000a;Report ID: 4455d534-3b1a-4245-9dfe-80b9d96a16ee&#x000d;&#x000a;Faulting package full name: &#x000d;&#x000a;Faulting package-relative application ID:
      My Computer


  9. Posts : 7,456
    Windows 10 Home 20H2
       #19

    jaburmester said:
    You have not run this script: 👉 Tuneup_plus_log.bat ✔️

    Please download the above new version and run it and then upload the "Tuneup.log" file created on your desktop.
    Do not run the old version you downloaded weeks ago.
    Last edited by Matthew Wai; 18 Apr 2021 at 06:12.
      My Computer


  10. Posts : 223
    Windows 10
    Thread Starter
       #20

    Matthew Wai said:
    You have not run this script: 👉 Tuneup_plus_log.bat ✔️

    Please download the above new version and run it and then upload the "Tuneup.log" file created on your desktop.
    Do not run the old version you downloaded weeks ago.
    Attached is Tuneup_plus_log results. Tuneup.log
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:38.
Find Us




Windows 10 Forums