How to block an update restart and troubleshoot


  1. Posts : 39,175
    windows 10 professional version 1607 build 14393.969 64 bit
       #1

    How to block an update restart and troubleshoot


    This computer has Windows 10 20H2 (OS Build 19042.1165).

    Windows spontaneously downloaded an update and at a later time rebooted.

    There was failure to boot with various error messages and codes.

    Using a bootable Windows 10 iso RE uninstallation of the update was attempted and failed.

    A startup repair was able to uninstall the update.

    This link later appeared:

    Startup Failure: “We removed some recently installed updates…”

    https://support.microsoft.com/en-us/...c-1e80ed9f4a00


    Code:
    If the removal of these updates enables the machine to start up successfully, 
    
    Windows will also prevent the removed updates from installing automatically for the next 30 days. 
    
    This is intended to give Microsoft and our partners the opportunity to investigate the failure and resolve any issues.


    A manual BIOS update was performed which required a reboot.
    Upon reboot there was another Windows update.

    It failed to prevent the removed updates from installing automatically for the next 30 days.

    The computer failed to boot.
    An attempt to manually remove the update failed.
    Another startup repair was performed which removed the update.



    Now in the right lower corner is a Windows Update notice:
    Your device will restart to update outside of active hours
    Remember to leave it on. Open settings to adjust
    your active hours and whether you want reminders.

    Restart now............OK are the available buttons.


    These are some images:

    How to block an update restart and troubleshoot-recurrent-update-followed-failure-boot-09202021.png

    How to block an update restart and troubleshoot-recurrent-update-part-2-followed-failure-boot-09202021.png



    How can this restart be blocked (besides pause for 7 days)?

    When the Microsoft message indicated block for 30 days what was this supposed to modify?
    How can this be checked or verified?
    How can this be modified manually?


    Sfc /scannow cannot run as it displayed pending repair (the windows update):

    Code:
    Microsoft Windows [Version 10.0.19042.1165]
    (c) Microsoft Corporation. All rights reserved.
    
    C:\WINDOWS\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    
    There is a system repair pending which requires reboot to complete.  Restart
    Windows and run sfc again.
    
    C:\WINDOWS\system32>


    At a later time I was planning to perform an in place upgrade repair.
    Would this be impacted by any of the possible modifications to cancel the current restart?
    If the in place upgrade repair fails how could this update that causes boot failure be blocked again?
      My Computer

  2. dalchina's Avatar
    Posts : 33,805
    Win 10 Pro (1903) (2nd PC is 21H2)
       #2

    It seems you have a pending update - have you tried removing it thus?
    How to delete pending updates on Windows 10 • Pureinfotech

    You would need to remove the pending update, then block it. Various means available as I think you know. One is given towards the end of the page above.

    You can also use various 3rd party tools.

    There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again.
    See:
    Fix: There is a system repair pending which requires reboot to complete - Appuals.com
      My Computers


  3. Posts : 39,175
    windows 10 professional version 1607 build 14393.969 64 bit
    Thread Starter
       #3

    In this link it indicated that contents of the software distribution folder (downloads) be deleted.
    This was done with a right click.

    Thx.

    The power button remained the same with options to update and restart, update and shutdown, and restart.

    So I'll click restart and see what happens.
    If the scannow does not run upon reboot I'll follow the steps in the above link.

    Yesterday I'd downloaded a new Windows 10 iso to the desktop.

    If there are no reboot problems I'll plan an in place upgrade repair in clean boot.
    This computer has defender and no drive encryption.
      My Computer

  4. dalchina's Avatar
    Posts : 33,805
    Win 10 Pro (1903) (2nd PC is 21H2)
       #4

    This may be clearer and more complete:
    How to delete Downloaded, Failed & Pending Windows Updates
      My Computers

  5. Brink's Avatar
    Posts : 60,030
    64-bit Windows 11 Pro for Workstations
       #5

    Hello @zbook,

    In addition, you should be able to reset Windows Update below to clear this.

    Reset Windows Update in Windows 10

    Afterwards, be able to pause Windows Update.

    Pause Updates or Resume Updates for Windows Update in Windows 10
      My Computers


  6. Posts : 39,175
    windows 10 professional version 1607 build 14393.969 64 bit
    Thread Starter
       #6

    The above post was not seen as the computer was rebooted.

    The initial reboot worked without problems after deletion of the software distribution downloads.

    The HP BIOS was then downloaded.
    An automatic reboot was performed.

    Upon reboot it displayed:

    Just a moment let's finish setting up your device.
    Remind me in 3 days was clicked.

    Working on updates.
    Don't turn off your computer.

    It rebooted.

    Working on updates.....100%

    Winver: 20H2 (OS Build 19042.1237)

    So the deletion of only the software distribution downloads failed to block the update.

    The restart and update was not clicked.

    Somehow updating the HP BIOS restart caused Windows to update??? or were these unrelated?

    It updated from 19042.1165 to 1237.

    There were no failures to boot this time.

    Scannow was able to run and reported corrupted files that it was unable to repair.
    Checkhealth and scanhealth were ok.
    Restorehealth could not find source files: 0x800f081f

    The Windows update did not fix the Windows problems.
    So I'll see if an in place can fix the restorhealth and scannow.

    The BIOS was updated twice.
    The first and second BIOS updates each had a Windows update.

    The error messages and codes in the opening post had included:
    CMO checksum is incorrect.
    CMOS reboot 502

    (This may mean that the CMOS battery needs replacement on the notebook)???

    With the above I'd performed the BIOS reinstallation twice (same most up to date version).



    The Deployment Image Servicing Management Tool Version seen in the restorehealth command was
    10.0,19041.844
    and the image version is
    10.0,19042,1237

    so 19041.844 could not fix 19042.1237.



    Code:
        Started on Mon 09/20/2021 at 16:47:53.75 
    
            [SFC /ScanNow] 
    
    Beginning system scan.  This process will take some time.
    
    Results: 
     
    Windows Resource Protection found corrupt files but was unable to fix some of them.
    
    For online repairs, details are included in the CBS log file located at 
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.
     
    ==================================================================
    
        Started on Mon 09/20/2021 at 16:50:08.76 
    
            [DISM /online /cleanup-image /ScanHealth] 
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.19042.1237 
     
    The component store is repairable.
    
    The operation completed successfully. 
     
    ==================================================================
    
        Started on Mon 09/20/2021 at 16:52:31.89 
    
            [DISM /online /cleanup-image /RestoreHealth] 
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.19042.1237 
     
    Error: 0x800f081f
    
    The source files could not be found.  
     
    Use the "Source" option to specify the location of the files that are required to restore the feature. 
    For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077. 
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
     
    ==================================================================
    
        Started on Mon 09/20/2021 at 17:02:34.62 
    
            [SFC /ScanNow] 
    
    Beginning system scan.  This process will take some time.
    
    Results: 
     
    Windows Resource Protection found corrupt files but was unable to fix some of them.
    
    For online repairs, details are included in the CBS log file located at 
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.
     
    ==================================================================
    
    A TXT file named SFC_details.txt has been created.
     
    ==================================================================
    
        Started on Mon 09/20/2021 at 17:04:53.79 
    
            [ChkDsk /Scan]  
     
    The type of the file system is NTFS.
    Volume label is Windows.
     
    Stage 1: Examining basic file system structure ... 
    765184 file records processed.                                                        
    File verification completed.
    Phase duration (File record verification): 14.48 seconds.
    11110 large file records processed.                                   
    Phase duration (Orphan file record recovery): 0.00 milliseconds.
    0 bad file records processed.                                     
    Phase duration (Bad file record checking): 0.04 milliseconds.
     
    Stage 2: Examining file name linkage ... 
    815 reparse records processed.                                      
    1130720 index entries processed.                                                       
    Index verification completed.
    Phase duration (Index verification): 3.15 minutes.
    0 unindexed files scanned.                                        
    Phase duration (Orphan reconnection): 5.29 seconds.
    0 unindexed files recovered to lost and found.                    
    Phase duration (Orphan recovery to lost and found): 0.11 milliseconds.
    815 reparse records processed.                                      
    Phase duration (Reparse point and Object ID verification): 5.71 milliseconds.
     
    Stage 3: Examining security descriptors ... 
    Security descriptor verification completed.
    Phase duration (Security descriptor verification): 113.08 milliseconds.
    182769 data files processed.                                           
    Phase duration (Data attribute verification): 0.09 milliseconds.
    CHKDSK is verifying Usn Journal...
    35645080 USN bytes processed.                                                           
    Usn Journal verification completed.
    Phase duration (USN journal verification): 330.73 milliseconds.
    
    Windows has scanned the file system and found no problems.
    
    No further action is required.
     
    722633727 KB total disk space. 
    206381356 KB in 510670 files.
    444616 KB in 182770 indexes.
    0 KB in bad sectors.
    894947 KB in use by the system.
    65536 KB occupied by the log file.
    514912808 KB available on disk.
     
    4096 bytes in each allocation unit. 
    180658431 total allocation units on disk.
    128728202 allocation units available on disk.
    Total duration: 3.48 minutes (209385 ms).
     
    ==================================================================
     
        Started on Mon 09/20/2021 at 17:09:02.17 
     
    AutoReboot   
     
    FALSE       
     
    ==================================================================
     
            [Set AutoReboot = False] 
     
    Updating property(s) of '\\DESKTOP-K2CP43S\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
    
    Property(s) update successful.
    
    ==================================================================
     
    AutoReboot   
     
    FALSE       
     
    ==================================================================
     
    DebugInfoType   
     
    7              
     
    ==================================================================
    
            [Set DebugInfoType = 7]
    
    Updating property(s) of '\\DESKTOP-K2CP43S\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
    
    Property(s) update successful.
    
    ==================================================================
     
    DebugInfoType   
     
    7              
     
    ==================================================================
    
            [WMIC PageFile list]
    
    AllocatedBaseSize=29696
    CurrentUsage=64
    Description=C:\pagefile.sys
    InstallDate=20210123182308.249920-360
    Name=C:\pagefile.sys
    PeakUsage=66
    Status=
    TempPageFile=FALSE
     
    ==================================================================
     
    AutomaticManagedPagefile   
     
    TRUE                      
     
    ==================================================================
    
            [Set AutomaticManagedPagefile = True]
    
    Updating property(s) of '\\DESKTOP-K2CP43S\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP-K2CP43S"'
    
    Property(s) update successful.
    
    ==================================================================
     
    AutomaticManagedPagefile   
     
    TRUE                      
     
    ==================================================================
    
            [BcdEdit /enum {badmemory}]
    
    RAM Defects
    -----------
    identifier              {badmemory}
     
    ==================================================================
    
        Finished on Mon 09/20/2021 at 17:09:03.16



    Code:
    2021-09-20 17:04:51, Info                  CSI    0000046b [SR] Cannot repair member file [l:34]'System.Web.ApplicationServices.dll' of System.Web.ApplicationServices, version 4.0.15805.295, arch amd64, versionScope neutral, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2021-09-20 17:04:51, Info                  CSI    0000046d [SR] Cannot repair member file [l:34]'System.Web.ApplicationServices.dll' of System.Web.ApplicationServices, version 4.0.15805.295, arch amd64, versionScope neutral, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2021-09-20 17:04:51, Info                  CSI    0000046e [SR] This component was referenced by [l:78]'Package_3_for_KB5004331~31bf3856ad364e35~amd64~~10.0.4400.1.5004331-92_neutral'
    2021-09-20 17:04:51, Info                  CSI    00000471 [SR] Could not reproject corrupted file \??\C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\\System.Web.ApplicationServices.dll; source file in store is also corrupted
    2021-09-20 17:04:51, Info                  CSI    00000472 [SR] Could not reproject corrupted file \??\C:\WINDOWS\Microsoft.NET\Assembly\GAC_MSIL\System.Web.ApplicationServices\v4.0_4.0.0.0__31bf3856ad364e35\\System.Web.ApplicationServices.dll; source file in store is also corrupted
    2021-09-20 17:04:51, Info                  CSI    00000473 [SR] Could not reproject corrupted file \??\C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\\System.Web.ApplicationServices.dll; source file in store is also corrupted


    The first reboot did not force the update.
    So the deletion of the software distribution downloads worked?

    Somehow BIOS updates trigger windows updates?

    I'll consider performing a third BIOS update to see if it triggers a Windows update?

    Causation or Coincidence?

    Unless there are other suggestions, later this evening / night I'll attempt an in place upgrade to see if it will fix the scannow and restorehealth issues.
    Last edited by zbook; 20 Sep 2021 at 18:12.
      My Computer



  7. Posts : 39,175
    windows 10 professional version 1607 build 14393.969 64 bit
    Thread Starter
       #7

    Thx Shawn I'd missed the post earlier.

    Matthew Wai also commented that he had created a script similar to sledgehammer to block Windows updates.

    I'd forgotten about the available tutorials while troubleshooting the failed boots.



    During the failed boots these were some of the error messages:
    The CMOS checksum is incorrect.
    CMOS reboot 502
    There isn't enough memory available to create a ram disk device 0xc0000017
    Cannot lock the current drive.
    Windows cannot run a disk check on the volume because it is write protected.
    The operating system could not be loaded because a critical system drive is missing or contains errors windows\system32\drivers\ksecpkg.sys 0xc0000000d
    bootrec /fixboot access denied
    We couldn't complete the updates-undoing changes don't turn off your computer



    monitoring - How do I check the status of the CMOS battery? - Ask Ubuntu.

    https://www.techwalla.com/articles/t...d-cmos-battery

    It appears that this notebook needs it's CMOS battery replaced.




    The in place upgrade repair completed.

    A new scannow found corrupt files and fixed them.

    A repeat scannow found no integrity violations.


    I'm considering another BIOS update to see if it triggers a Windows update.

    If it does trigger updates I'm considering testing the methods to block Windows updates.
    Last edited by zbook; 21 Sep 2021 at 01:54.
      My Computer

  8. Matthew Wai's Avatar
    Posts : 6,453
    Windows 10 Home 20H2
       #8

    zbook said:
    Matthew Wai also commented that he had created a script similar to sledgehammer to block Windows updates.
    Note that if you have used the script to control Windows Update, you have to select (1) below before running "SFC /scannow". Otherwise, the results must be "Windows Resource Protection found corrupt files but was unable to fix some of them".



    After running "SFC /scannow", you may re-run "#_Control_Windows_Update.vbs".
      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 02:49.
Find Us




Windows 10 Forums