1. vreduru

    vreduru MDL Novice

    Jan 28, 2013
    5
    1
    0
    Failed for me also, when I tried WIS2RP, after unpermanize fix I got "The source files could not be found" error.
    Yeah it's strange thing. Had same exact situation - 16363.10022 after iso upgrade..
     
  2. sokolovs

    sokolovs MDL Novice

    Oct 13, 2019
    2
    0
    0
    I forgot about RTM fix completely...
     
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,656
    103,421
    450
    #6123 Enthousiast, Oct 14, 2019
    Last edited: Oct 14, 2019
    (OP)
    Read, on cleaned up installs, you need to run the RTM fix before the unpermanize commands and as last you can run WIS2RP and all will work.

    From 18362.10022 the upgrade, using a 18363.418 iso, will do a full upgrade to 18363.418 with keeping all files and apps or by running the WIS2RP fix and you will end up on 18363.418 too

    From 18363.10022 (which is a f**ked up scenario, nobody should install the 1909 EP on 18362.10022), but can be fixed by running the WIS2RP fix and you will end up on 18363.418 too.

    ONLY when the updates can't be uninstalled anymore, because of running any cleanup, you need to do the workaround and also will endup on 18363.418.
     
  4. vreduru

    vreduru MDL Novice

    Jan 28, 2013
    5
    1
    0
    Too late for me - already clean installed 18363.418 but thanks.
     
  5. bfoos

    bfoos MDL Guide Dog

    Jun 15, 2008
    757
    703
    30
    And that's honestly the best way to go about it. Congrats!
     
  6. SAM-R

    SAM-R MDL Guru

    Mar 21, 2015
    5,914
    5,753
    180
    OK Thank you Didn't know it wasn't new.
     
  7. bfoos

    bfoos MDL Guide Dog

    Jun 15, 2008
    757
    703
    30
    Not your fault. A small site posted about it and called it new and now other tech sites are gobbling it up and puking out practically verbatim articles of their own.
     
  8. MS_User

    MS_User MDL Guru

    Nov 30, 2014
    4,656
    1,361
    150
    their suppose to bring out the new file explorer thats not it ...i assume MS still working on it:rolleyes:
     
  9. dzem

    dzem MDL Senior Member

    Oct 15, 2015
    274
    56
    10
    I don't know why all this agony about 1909, or any new build, as we are jumping from windows 95 to windows xp, or xp to win 10. C'mon people, is that really matter ... as it is question of life and death question about 1903 and 1909 and upgrade and all that build number. Hallooooo
     
  10. Bat21UK

    Bat21UK MDL Novice

    May 24, 2007
    42
    3
    0
    hi all I hope I have put this in the right place
    with this build number I cannot not get my wd mycloud to show up in explore at all
    any help :(
     
  11. EaglePC

    EaglePC MDL Expert

    Feb 13, 2012
    1,254
    524
    60
    whatever 1903 build you are on come 1st tuesday november windowsupdate you will have 1909
     
  12. chlynx

    chlynx MDL Member

    Mar 27, 2017
    127
    25
    10
    to the point of exasperation. :D
     
  13. bonesz

    bonesz MDL Addicted

    Jun 30, 2013
    644
    371
    30
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. jithin0007

    jithin0007 MDL Novice

    Oct 15, 2019
    1
    0
    0
    i have been experiencing hibernation issues with 1903, where when u wake up from hibernation it get stuck at logo screen. tried every solution available on internet. then i uninstalled the update and its working perfectly well now
     
  15. W7U

    W7U MDL Junior Member

    Feb 19, 2017
    57
    11
    0
    It is very fortunate that I bought NTlite, although I have decided that the KMS thing (the only blocker in the unattended script) can be done manually. What really annoys me however is that even with the Windows Update MiniTool, the latest roll-up updates reinstate Microsoft Edge, although I cannot confirm if it replaces Firefox as the default browser. I do not know if there is something that allows me to trim the packages, without having to reinstall Windows 10 after all the modifications that I have made so far.

    Rest assured that I do not think Windows Update MiniTool is not at fault.