Need Suggestions for a failed 1809 update

Page 3 of 6 FirstFirst 12345 ... LastLast
  1.    #21

    So it's been going for almost 8 hours now.

    Took about 35 minutes to go through the initial stuff. Downloading updates and such. I saw it doing whatever and it had a progress percentage that got to 100%. Did its first reboot (I think unless I missed one) and hung as in prior attempts at the 4 blue pane window. Been sitting there for a bit over 7 hours now. When I check it, I've never seen any disk activity.

    So unless you/anyone thinks this should take this long, I figure I'll kill it around the 9 hour mark.
      My ComputerSystem Spec


  2. Posts : 26,133
    windows 10 professional version 1607 build 14393.969 64 bit
       #22

    Look for an error code and message.
    Run setupdiag > post a share link into the thread

    Run the BETA log collector and post a zip into the thread
    BSOD - Posting Instructions - Windows 10 Forums

    Make a backup image using Macrium (free version)
    Macrium Software | Your Image is Everything
    Save the backup image to another drive or to the cloud

    The last error code was:


    Code
    0xC1900101 - 0x20017

    Cause
    A driver has caused an illegal operation.
    Windows was not able to migrate the driver, resulting in a rollback of the operating system.
    This is a SafeOS boot failure, typically caused by drivers or non-Microsoft disk encryption software.


    Mitigation
    Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
    Contact your hardware vendor to obtain updated device drivers.
    Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.


    Windows driver verifier is a tool to find misbehaving drivers.

    Read this link and learn the methods to turn off and / or recover from using the tool:
    Enable and Disable Driver Verifier in Windows 10 | Tutorials

    Make a brand new restore point:
    Create System Restore Point in Windows 10 | Tutorials

    Do not use the tool until:
    a) there is an up to date Macrium backup image saved to a different disk or to the cloud
    b) there is a brand new restore point
    c) you understand the methods to use the computer's windows advanced troubleshooting menu to turn off and / or recover from using the tool
      My ComputerSystem Spec

  3.    #23

    Got the same results as before

    Unfortunately I misplaced the setupdiag so I don't have that, but the VENUS-(2019-02-17_15-39-22).zip file is at https://www.dropbox.com/sh/bagayzchk...hgJ1f-Doa?dl=0 if this is worth anything.

    I couldn't just run setupdiag again as I've tried the update again. I've posted those results next. The error screen below is the same as the prior attempts

    I did run the driver verifier. Ran it first for awhile as the link states, but nothing was happening and it wasn't running sluggish as the tutorial suggests. So I restarted it marking all (microsoft & non-microsoft) drivers. That did slow the machine down quite noticeably. Unfortunately (?), it never did blue screen. Left it running for 46 hours before giving up and resetting the verifier off.
    Attached Thumbnails Attached Thumbnails UpdateErrorScreen.png  
      My ComputerSystem Spec

  4.    #24

    Out of curiosity, based on your prior question about drivers, I tried the Vista drivers and installed the Dell supplied graphics, sound, and network drivers. The only noticeable difference is now I can get the screen back up to the native resolution so that's a good thing.

    I retried the update. Let it run for about 5 hours last night with the same results. It looks like it successfully does its thing prior to the first reboot. The initial step from start, downloading any updates through whatever it's doing when the percentage ticker is slowing climbing takes 30-40 minutes. Then it reboots and there is a brief disk activity and it gets to the screen with the four window panes. There is no progress (circle of spinning dots) and no disk activity. Obviously I don't / didn't sit there and stare at it for five hours but do check it from time to time and never see the disk activity led after the initial few seconds.

    The setupdiag log for this is Logs.zip at https://www.dropbox.com/sh/ri4nlo5dy...Bug0MpR3a?dl=0 .

    The beta log is VENUS-(2019-02-26_10-47-46).zip (attached)

    I have not tried running the driver verifier again since putting the Dell drivers in as except for this, all the same update failures happened with the MS drivers that I did run the driver verifier against.
    Need Suggestions for a failed 1809 update Attached Files
      My ComputerSystem Spec


  5. Posts : 26,133
    windows 10 professional version 1607 build 14393.969 64 bit
       #25

    1) Download and install: Everything
    voidtools

    2) Use Everything to search for: PDCRevocation-20190220-1543.dmp

    3) Zip the file > post a separate share link into the thread using one drive, drop box, or google drive


    Code:
    Name                            LastWriteTime        Size (MB)
    ----                            -------------        ---------
    PDCRevocation-20190220-1543.dmp 2/20/2019 3:43:59 PM   1202.52

    4) Create a brand new system restore point:
    Create System Restore Point in Windows 10 | Tutorials


    5) Windows driver verifier has customized settings for drivers and for tests.
    For the customized settings select all non-Microsoft drivers.
    And select approximately 19 simultaneous customized test as in this link:

    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    6) For all upgrade attempts make sure that the upgrade assistant is not used (only use a Windows 10 iso for upgrades). For the option to perform updates select the option to perform updates later after a successful upgrade.


    7) Uninstall software and drivers for the Canon product:

    Canon MX860 series MP Drivers

    8) Open administrative command prompt and type or copy and paste:
    chkdsk /r /v
    This may take many hours so plan to run overnight.
    The chkdsk command was already ran on C: using the command chkdsk /r /v
    Run the chkdsk command on all other drives: I and J

    PS C:\WINDOWS\system32> chkdsk /r /v C:
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot

    Run this command on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

    Code:
    ------------------------
    Disk & DVD/CD-ROM Drives
    ------------------------
          Drive: C:
     Free Space: 66.2 GB
    Total Space: 102.4 GB
    File System: NTFS
          Model: Samsung SSD 850 EVO 500GB ATA Device
    
          Drive: I:
     Free Space: 17.9 GB
    Total Space: 30.7 GB
    File System: NTFS
          Model: Samsung SSD 850 EVO 500GB ATA Device
    
          Drive: J:
     Free Space: 20.0 GB
    Total Space: 20.5 GB
    File System: NTFS
          Model: Samsung SSD 850 EVO 500GB ATA Device
    9) Use the text and images in this link to find the chkdsk reports in the event viewer > copy and paste > notepad > post share links into the thread using one drive, drop box, or google drive


    Read Chkdsk Log in Event Viewer in Windows 10 | Tutorials

    10) For all upgrade attempts make sure that there is only one drive (windows drive) connected at the time of the upgrade.

    11) There was an image of computer management posted earlier in the thread. Does the computer have disk management? If so post an image into the thread.
      My ComputerSystem Spec

  6.    #26

    I'll have to wait till the weekend for the driver test. I can't have it crash in the middle of some senior's tax prep.

    But in the meantime, the PDCRevocation-20190220-1543.dmp
    is in https://www.dropbox.com/sh/ri4nlo5dy...Bug0MpR3a?dl=0. xx

    6) For all upgrade attempts . . . only use a Windows 10 iso
    I've been using a USB stick and not a CD/DVD. That OK? Or are you saying it must be a mounted ISO file?

    11) There was an image of computer management posted earlier in the thread. Does the computer have disk management? If so post an image into the thread.


    Not sure what you're asking here. i think there was an image of the MS built-in disk management posted. Posted below. The machine does have the Mini-tool Partition Wizard installed. But that only runs on demand.
    Attached Thumbnails Attached Thumbnails Snap2.png  
      My ComputerSystem Spec



  7. Posts : 26,133
    windows 10 professional version 1607 build 14393.969 64 bit
       #27

    Ordinarily mini and memory dumps are debugged to find misbehaving drivers.
    In the kernel dump there was no misbehaving driver seen in the debugging.

    When there is a Windows upgrade failure the error codes can be displayed as only a result code or a result code with an extend code.

    The extend code provides more information.

    Using the upgrade assistant typically only displays a result code and no extend code.


    In contrast, using a bootable Windows 10 iso and mounting the file typically creates a result code with an extend code.

    Upgrade error codes - Windows IT Pro | Microsoft Docs

    Code:
    Note: If only a result code is returned, this can be because a tool is being used that was not able to capture the extend code. For example, if you are using the Windows 10 Upgrade Assistant then only a result code might be returned.


    The prior image of disk management in post #12 did not display the row for disk 0.
    The latest image displayed the results.

    Please post an image of the Minitool partition wizard.

    The next step will be to see if there are any misbehaving drivers using the approximately 19 tests for Windows driver verifier.

    Before using the tool please make sure that the Macrium image is up to date and create a brand new restore point:
    Create System Restore Point in Windows 10 | Tutorials
      My ComputerSystem Spec

  8.    #28

    here's the partition magic snapshot
    Attached Thumbnails Attached Thumbnails PartMagic.png  
      My ComputerSystem Spec


  9. Posts : 26,133
    windows 10 professional version 1607 build 14393.969 64 bit
       #29

    Open administrative command prompt and type or copy and paste all of these commands at one time:

    Code:
    bcdedit /enum all
    reagentc /info
    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

    Code:
    diskpart
    list disk
    list volume
    select disk 0
    detail disk
    list partition
    select partition 1
    detail partition
    select partition 2
    detail partition
    select partition 3
    detail partition
    select partition 4
    detail partition
    select partition 5
    detail partition
    select partition 6
    detail partition 
    select partition 7
    detail partition
    select partition 8
    detail partition
    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
      My ComputerSystem Spec

  10.    #30

    bcdedit /enum all
    reagentc /info

    Code:
    Microsoft Windows [Version 10.0.17134.590]
    (c) 2018 Microsoft Corporation. All rights reserved.
    
    C:\WINDOWS\system32>bcdedit /enum all
    
    Windows Boot Manager
    --------------------
    identifier              {bootmgr}
    device                  partition=C:
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {globalsettings}
    default                 {current}
    resumeobject            {b4d2774c-16e9-11e9-8992-f809234f9954}
    displayorder            {current}
    toolsdisplayorder       {memdiag}
    timeout                 30
    
    Windows Boot Loader
    -------------------
    identifier              {19fc0721-1864-11e9-bc5f-d5b701671652}
    device                  ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{19fc0722-1864-11e9-bc5f-d5b701671652}
    path                    \windows\system32\winload.exe
    description             Windows Recovery Environment
    locale                  en-US
    inherit                 {bootloadersettings}
    displaymessage          Recovery
    osdevice                ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{19fc0722-1864-11e9-bc5f-d5b701671652}
    systemroot              \windows
    nx                      OptIn
    bootmenupolicy          Standard
    winpe                   Yes
    
    Windows Boot Loader
    -------------------
    identifier              {current}
    device                  partition=C:
    path                    \WINDOWS\system32\winload.exe
    description             Windows 10
    locale                  en-US
    inherit                 {bootloadersettings}
    recoverysequence        {19fc0721-1864-11e9-bc5f-d5b701671652}
    displaymessageoverride  CommandPrompt
    recoveryenabled         Yes
    allowedinmemorysettings 0x15000075
    osdevice                partition=C:
    systemroot              \WINDOWS
    resumeobject            {b4d2774c-16e9-11e9-8992-f809234f9954}
    nx                      OptIn
    bootmenupolicy          Standard
    
    Resume from Hibernate
    ---------------------
    identifier              {b4d2774c-16e9-11e9-8992-f809234f9954}
    device                  partition=C:
    path                    \WINDOWS\system32\winresume.exe
    description             Windows Resume Application
    locale                  en-US
    inherit                 {resumeloadersettings}
    recoverysequence        {19fc0721-1864-11e9-bc5f-d5b701671652}
    recoveryenabled         Yes
    allowedinmemorysettings 0x15000075
    filedevice              partition=C:
    filepath                \hiberfil.sys
    bootmenupolicy          Standard
    pae                     Yes
    debugoptionenabled      No
    
    Windows Memory Tester
    ---------------------
    identifier              {memdiag}
    device                  partition=C:
    path                    \boot\memtest.exe
    description             Windows Memory Diagnostic
    locale                  en-US
    inherit                 {globalsettings}
    badmemoryaccess         Yes
    
    EMS Settings
    ------------
    identifier              {emssettings}
    bootems                 No
    
    Debugger Settings
    -----------------
    identifier              {dbgsettings}
    debugtype               Serial
    debugport               1
    baudrate                115200
    
    RAM Defects
    -----------
    identifier              {badmemory}
    
    Global Settings
    ---------------
    identifier              {globalsettings}
    inherit                 {dbgsettings}
                            {emssettings}
                            {badmemory}
    
    Boot Loader Settings
    --------------------
    identifier              {bootloadersettings}
    inherit                 {globalsettings}
                            {hypervisorsettings}
    
    Hypervisor Settings
    -------------------
    identifier              {hypervisorsettings}
    hypervisordebugtype     Serial
    hypervisordebugport     1
    hypervisorbaudrate      115200
    
    Resume Loader Settings
    ----------------------
    identifier              {resumeloadersettings}
    inherit                 {globalsettings}
    
    Device options
    --------------
    identifier              {19fc0722-1864-11e9-bc5f-d5b701671652}
    description             Windows Recovery
    ramdisksdidevice        partition=C:
    ramdisksdipath          \Recovery\WindowsRE\boot.sdi
    
    C:\WINDOWS\system32>reagentc /info
    Windows Recovery Environment (Windows RE) and system reset configuration
    Information:
    
        Windows RE status:         Enabled
        Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE
        Boot Configuration Data (BCD) identifier: 19fc0721-1864-11e9-bc5f-d5b701671652
        Recovery image location:
        Recovery image index:      0
        Custom image location:
        Custom image index:        0
    
    REAGENTC.EXE: Operation Successful.
    
    
    C:\WINDOWS\system32>


    the diskpart stuff. Note that there are only 4 partitions. The other areas are unpartioned space.


    Code:
    C:\WINDOWS\system32>diskpart
    
    Microsoft DiskPart version 10.0.17134.1
    
    Copyright (C) Microsoft Corporation.
    On computer: VENUS
    
    DISKPART> list disk
    
      Disk ###  Status         Size     Free     Dyn  Gpt
      --------  -------------  -------  -------  ---  ---
      Disk 0    Online          465 GB      0 B
    
    DISKPART> list volume
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 0     W                       DVD-ROM         0 B  No Media
      Volume 1     C                NTFS   Partition    100 GB  Healthy    System
      Volume 2     I   Data         NTFS   Partition     29 GB  Healthy
      Volume 3     J   Database     NTFS   Partition     19 GB  Healthy
    
    DISKPART> select disk 0
    
    Disk 0 is now the selected disk.
    
    DISKPART> detail disk
    
    Samsung SSD 850 EVO 500GB ATA Device
    Disk ID: 41AB2316
    Type   : ATA
    Status : Online
    Path   : 0
    Target : 0
    LUN ID : 0
    Location Path : ACPI(_SB_)#ACPI(PCI0)#ACPI(IDE0)#ACPI(PRI_)#ATA(C00T00L00)
    Current Read-only State : No
    Read-only  : No
    Boot Disk  : Yes
    Pagefile Disk  : Yes
    Hibernation File Disk  : No
    Crashdump Disk  : Yes
    Clustered Disk  : No
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 1     C                NTFS   Partition    100 GB  Healthy    System
      Volume 2     I   Data         NTFS   Partition     29 GB  Healthy
      Volume 3     J   Database     NTFS   Partition     19 GB  Healthy
    
    DISKPART> list partition
    
      Partition ###  Type              Size     Offset
      -------------  ----------------  -------  -------
      Partition 1    OEM                 54 MB    31 KB
      Partition 2    Primary            100 GB    31 GB
      Partition 3    Primary             29 GB   249 GB
      Partition 4    Primary             19 GB   389 GB
    
    DISKPART> select partition 1
    
    Partition 1 is now the selected partition.
    
    DISKPART> detail partition
    
    Partition 1
    Type  : DE
    Hidden: Yes
    Active: No
    Offset in Bytes: 32256
    
    There is no volume associated with this partition.
    
    DISKPART> select partition 2
    
    Partition 2 is now the selected partition.
    
    DISKPART> detail partition
    
    Partition 2
    Type  : 07
    Hidden: No
    Active: Yes
    Offset in Bytes: 33363591168
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
    * Volume 1     C                NTFS   Partition    100 GB  Healthy    System
    
    DISKPART> select partition 2
    
    Partition 2 is now the selected partition.
    
    DISKPART> detail partition
    
    Partition 2
    Type  : 07
    Hidden: No
    Active: Yes
    Offset in Bytes: 33363591168
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
    * Volume 1     C                NTFS   Partition    100 GB  Healthy    System
    
    DISKPART> select partition 3
    
    Partition 3 is now the selected partition.
    
    DISKPART> detail partition
    
    Partition 3
    Type  : 07
    Hidden: No
    Active: No
    Offset in Bytes: 268088377344
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
    * Volume 2     I   Data         NTFS   Partition     29 GB  Healthy
    
    DISKPART> select partition 4
    
    Partition 4 is now the selected partition.  Note that there are only 4 partititions
    
    DISKPART> detail partition
    
    Partition 4
    Type  : 07
    Hidden: No
    Active: No
    Offset in Bytes: 418034745344
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
    * Volume 3     J   Database     NTFS   Partition     19 GB  Healthy
    
    
    DISKPART>
      My ComputerSystem Spec


 
Page 3 of 6 FirstFirst 12345 ... LastLast

Related Threads
A few days ago Windows Update tried to install Windows 10 Version 1809 on my laptop. It failed and corrupted the Windows Update database. I deleted the database and let it get rebuilt. Now Windows isn't trying any more to install 1809. I was told...
Updated (and Failed) 1803, not updated to 1809 in Windows Updates and Activation
I don't understand this: The update to Version 1809 was released 09Oct2018. On my wife's computer, after the first attempt failed, a retry was offered; I took it, and later there was a "Restart" icon, so I clicked on it, after noticing something...
Hi, Windows 10 1809 feature update was installed through Windows Update on the 2nd October on my laptop. Ive only just found out on here that Microsoft have since pulled the update because of problems. I don't appear to have lost any files...
As per title. old Alienware M17X-R3 laptop, running previous version 100% fine. The update failed. I tried rebooting and for the last hour it’s been saying “restarting”. Any advice please?
Hello everyone, I recently upgraded from Windows 7 to Windows 10. Trouble is I am now stuck with earliest version of Windows 10 and cannot update to ANY newer version in order to fix numerous Windows 10 problems I am encountering - most importantly...
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 17:23.
Find Us