How to "upgrade" from 18363.10022 (slow ring) to 18363.418 (release)

Discussion in 'Windows 10' started by Euclid, Oct 11, 2019.

  1. Euclid

    Euclid MDL Novice

    Jul 24, 2009
    29
    11
    0
    I currently have build 18363.10022 from the insider slow ring installed. I did try to "upgrade" to the 1909 release build 18363.418 using the 18363.418 ISO. When running the setup.exe of 18363.418, I'm not able to keep the Personal Files and Apps, because the setup complains that this is not possible when installing an older version. The setup most likely believes that I have a new build installed because the build patch number 10022 is greater than 418.

    I have tried to "trick" the setup by manually changing the version numbers in the registyr key (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion) without success.

    I cannot go back to a previous build as I have the build from the slow ring installed for over 10 days.

    Any advice?
     
  2. Euclid

    Euclid MDL Novice

    Jul 24, 2009
    29
    11
    0
  3. SAM-R

    SAM-R MDL Guru

    Mar 21, 2015
    3,835
    3,187
    120
    Already been covered. You have use 18363.327 .ISO or 18363.356 .ISO for the Upgrade to work.
    Read the Forum Post I gave you.
     
  4. 600415

    600415 MDL Member

    Aug 31, 2015
    148
    202
    10
    Switch to RP ring and just wait until it gets .100XX patches. An inplace upgrade seems thoroughly unnecessary to me.
     
  5. Euclid

    Euclid MDL Novice

    Jul 24, 2009
    29
    11
    0
    No, it's not covered (my build is 18363.10022) and if it is, it doesn't work. I have tried it with the 18363.356 ISO (18363.356.190908-0900.19H2_RELEASE_SVC_PROD1_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO) now from the link above as well. The apps and files cannot be kept.
     
  6. SAM-R

    SAM-R MDL Guru

    Mar 21, 2015
    3,835
    3,187
    120
    Then go with 18363.327 .ISO. Enthousiast has already confirmed that 18363.327 .ISO works.

    https://forums.mydigitallife.net/th...-18362-3-xxx-pc-19h1-2-release.79259/page-291
    Post #5814 with Pics
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    26,810
    38,836
    390
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. Euclid

    Euclid MDL Novice

    Jul 24, 2009
    29
    11
    0
    This didn't work:
    1. The 1909 EP cannot be uninstalled (at least not in my case)
    2. But I was able to uninstall a cumulative update which brought the version number down to 18362.10019
    3. Now I was able to install 18363.356 .ISO
    4. The in-place upgrade went fine, without any errors. Meaning the old Windows build was not restored and the "update" was actually successful.
    5. After the restart the build number is still at 18362.10019. The kernel32.dll version number is 18362.10000
    6. So I do not believe things went well. I also tried it with the 18363.418 ISO and I see the same behavior.
     
  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    26,810
    38,836
    390
    Then your system is more f**ked up then mine was:D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. Euclid

    Euclid MDL Novice

    Jul 24, 2009
    29
    11
    0
    I don't quite understand how the in-place upgrade/downgrade can succeed but all the system files are still at the same version.
     
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    26,810
    38,836
    390
    Because of the mess MSFT made with releasing a mock build, even the original MSFT iso can't figure it out, that's why it doesn't offer the other keeping options.

    And those who installed the 1909 EP on 18362.10022, bumping it to 18363.10022, made it even more difficult, specially when the 1909 EP can't be uninstalled.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. Euclid

    Euclid MDL Novice

    Jul 24, 2009
    29
    11
    0