Error each time upgrading to 1903 from 1803


  1. Posts : 36
    windows 8.1
       #1

    Error each time upgrading to 1903 from 1803


    Error log at last failure to update:
    ---------------------
    I have tried every suggestion on multiple forums, but after more than a dozen tries, I cannot get Windows to update to 1903. Here is my most recent setuperr.log data in its entirety. I have no idea what it means but I assume someone at Microsoft would...
    -----------------------------------------------


    2019-08-06 13:53:06, Error DU DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057
    2019-08-06 13:53:25, Error CONX 0xd0000034 Failed to add user mode driver [%SystemRoot%\system32\DRIVERS\UMDF\uicciso.dll]


    2019-08-06 13:58:23, Error SP pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
    2019-08-06 13:58:49, Error CSI 00000001 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #38002# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 32 ): 3f003a005c007000610067006500660069006c0065002e007300790073000000 })
    [gle=0x80004005]
    2019-08-06 13:58:52, Error CSI 00000002 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #85712# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 12 ): 65006e002d00550053000000 })
    [gle=0x80004005]
    2019-08-06 13:58:53, Error CSI 00000003 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #98471# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 32 ): 3f003a005c007000610067006500660069006c0065002e007300790073000000 })
    [gle=0x80004005]
    2019-08-06 13:59:28, Error CSI 00000004 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #172753# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 32 ): 3f003a005c007000610067006500660069006c0065002e007300790073000000 })
    [gle=0x80004005]
    2019-08-06 13:59:42, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
    2019-08-06 14:02:58, Error CSetupAutomation::Resurrect: File not found: C:\$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]
    2019-08-06 14:02:58, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
    2019-08-06 14:37:08, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
      My Computer


  2. Posts : 43,086
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    With respect to uicciso.dll - this is a relatively common issue- please see e.g.
    SOLVED: Trouble updating to 1803 - TechTablets
    for an approach.

    Search result on this site:
    Error each time upgrading to 1903 from 1803-snap-2019-08-06-15.41.32.png
    from which you may find more helpful comment.

    Basics:
    - run
    chkdsk c: /scan
    from an admin command or Powershell prompt and check the result is clear
    - if ok, run similarly
    sfc /SCANNOW
    and check the result is clear

    Check you have, say 30Gb free disk space on C:

    If ok:
    - download the Win 10 iso
    - remove security software
    - disconnect unnecessary peripherals
    - log in as normal
    - mount the iso
    - run setup.exe from the newly created drive letter
    - do not accept updates as part of the upgrade procedure (you can also disconnect the internet).

    Please post the results of the above.

    I have no idea what it means but I assume someone at Microsoft would...
    That may be true- please note this is not a MS site but one where members are users like you.

    Note your specs say Windows 8.1 and nothing about your PC. Please complete your PC specs (see mine for comparison). thanks.
      My Computers


  3. Posts : 36
    windows 8.1
    Thread Starter
       #3

    I read the instructions for the use of the Media Creation Tool, but they didn't help me understand what you mean by "newly created drive letter."
    My specs are these:
    Dell Optiplex 9010, 64-bit, latest Bios update 02/22/18, version A29.00
    Windows 10 Pro ver. 10.0.1734
    Installed physical memory: 16 gb
      My Computer


  4. Posts : 43,086
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #4

    Thank you very much for your reply..

    If you Mount an iso file, that creates a new drive letter. That represents the new ram disk created whose content is the content of the iso file.

    You just have to look at the list of drives in file explorer before and after mounting the iso.

    Mount appears as an option in the rt click context menu so long as you have not associated iso files with any other program.

    Mounting such files is also possible using a number of 3rd party programs such as Power ISO.

    If you had searched for e,g,
    Mounting an iso file
    you would have found articles like this:
    How to Mount an ISO image in Windows 7, 8, and 10

    A search engine can be very helpful when you don't understand something.
      My Computers


  5. Posts : 9,765
    Mac OS Catalina
       #5

    Personally I would stick with 1803 due in part with all of the issues that 1809 and 1903 have introduced 1803 is still getting updates to it because so many machines still run it, especially in the Enterprise.
      My Computer


  6. Posts : 43,086
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #6

    https://support.microsoft.com/en-gb/...cle-fact-sheet

    1803 end of life is November 12, 2019 for Home/Pro

    1809 had a very bad start, but became stable.
    1903 seems pretty good with a few known problems.

    In any event, make sure you have a current disk image before upgrading to make sure youcan revert should you wish. Keeping a build after the end of service life means you would have to disable Windows Update - or at least the relevant feature update.
      My Computers


  7. Posts : 9,765
    Mac OS Catalina
       #7

    Right know MS is starting to suspend updates for certain hardware with that list growing until they find a fix for their mess. It has always been a trial by fire with Windows 10 from the beginning. Even MacOS and Linux had these growing pains abd you took the risks.

    Home is the only version that MS is forcing into a EOL status. As for the OP, their best bet will be doing a clean install with another hard drive to keep the current one safe from losing any data.
      My Computer


  8. Posts : 41,498
    windows 10 professional version 1607 build 14393.969 64 bit
       #8

    There was no error and result codes seen in the opening post.
    It can take a lot of time to troubleshoot upgrade failures.
    Alternatives include reset save files, reset save files equivalent, and clean install.
    The time that it takes to reinstall drivers and applications should be compared.
    If you prefer to troubleshoot then run setupdiag and post a share link into the thread using one drive, drop box, or google drive
    https://docs.microsoft.com/en-us/win...rade/setupdiag
      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 18:33.
Find Us




Windows 10 Forums