1. 600415

    600415 MDL Member

    Aug 31, 2015
    191
    239
    10
    @Schroedinger2015 yes, they removed some components in .329, and also .327 had a corrupt component
    I will post a fix in a few hours
     
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    35,591
    59,669
    450
    Your fixes seem to work but i am having a hard time with the conclusion that every post 18362.239 update contains the same faults.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. 600415

    600415 MDL Member

    Aug 31, 2015
    191
    239
    10
    no, they are different types of faults
    Most of the time problems occur because new update reverts components back to .1 — I guess this happens because they're built from a different branch
    The only two actually corrupt updates i noticed were
    .10013 (amd64_microsoft-windows-c..cal.desktop.cortana had a corrupt reverse delta bc it had less files than .1 version of same components)
    .327 (amd64_hyperv-compute-guestcomputeservice component is incorrectly marked as new instead of updated — and that's on top of the trouble with .329 reverting some components back to .1)
    In short, the new forward-reverse delta system generates more trouble than it's worth. “Agile” development at its finest.

    IIRC they have solved the .263 problem in later updates by re-adding the relevant component. I think solving .10013 and .327 requires either a servicing stack/WU update or a change in how the updates are built bc the process does not know the old update has bugs

    That's to say, i haven't noticed these problems in any public updates, only RP ones
     
  4. Schroedinger2015

    Schroedinger2015 MDL Member

    Jul 16, 2015
    172
    115
    10
    I'll be waiting for your fix. ;)

    I tried the one you posted in the other thread and I assume is not for 18363 but for 18362.
     
  5. SM03

    SM03 MDL Expert

    Dec 16, 2012
    1,068
    527
    60
    IDK why you can't see the image in my post but just to let you know, it's the same error that am getting too.
     
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    35,591
    59,669
    450
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. iFlaX

    iFlaX MDL Senior Member

    Apr 10, 2015
    328
    288
    10
  8. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    35,591
    59,669
    450
    #4728 Enthousiast, Aug 30, 2019
    Last edited: Aug 30, 2019
    (OP)
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. 600415

    600415 MDL Member

    Aug 31, 2015
    191
    239
    10
    there is no 18363 build of windows
    there is a package which changes the displayed number in winver and enables some features, but the actual build is still 18362
     
  10. usama_2006

    usama_2006 MDL Novice

    Sep 29, 2012
    26
    0
    0
    KB4512941 not installed
     

    Attached Files:

  11. petok

    petok MDL Senior Member

    May 4, 2009
    287
    173
    10
    Do you have remove offline holographic ? If is removed then is problem... Also I have this error when remove holographic packages.
     
  12. MS_User

    MS_User MDL Guru

    Nov 30, 2014
    3,987
    871
    120
    is a optional update.

    upload_2019-8-30_17-26-44.png
     
  13. thejester77

    thejester77 MDL Junior Member

    Aug 6, 2012
    98
    36
    0
    #4733 thejester77, Aug 30, 2019
    Last edited: Aug 31, 2019
    Does anyone have any information regarding 10015 19h2... I have looked but haven't seen anything officially from Microsoft.

    Lots of us here had problems installing the CU updates which only error out.

    The same problems causing the error most likely screwed up DISM functioning because I couldn't do any DISM upgrades to my ISO's.

    I downloaded the 18363.327 ISO and going to try right now to upgrade from 18362.10015 to 18363.327 because I don't want to be left out of an upgrade channel when final build hits.

    For MS to fork the 19h2 (3 different ways) and not address 10015 besides were looking into it responses, I'm not feeling really confident on a solution.

    If the upgrade works, I will let you guys know.

    Any info anybody has, would be great as well...

    Thanx

    UPDATE:

    Upgrade from 18362.10015 to 18363.327 went without a hitch... Windows update had a couple CU's to get current... Everything is good except Windows is saying something about driver issues with Intel Optane (however it's spelled).

    I just looked at Intel's site to see if there's any updates, but there's none.

    System still seems to be running fine with that error.

    Intel Optane fix: Uninstall Intel Optane Extension
     
  14. Konstantinos

    Konstantinos MDL Member

    Sep 8, 2012
    182
    74
    10
    #4734 Konstantinos, Aug 30, 2019
    Last edited: Aug 30, 2019
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. Konstantinos

    Konstantinos MDL Member

    Sep 8, 2012
    182
    74
    10
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    35,591
    59,669
    450
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    35,591
    59,669
    450
    Or any chopping or modification? Set telemetry to full?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...