Need help..in place upgrade grom 2022 to 2025 issue

Discussion in 'Windows Server' started by alien2xx, Nov 8, 2024.

  1. alien2xx

    alien2xx MDL Senior Member

    Aug 5, 2009
    404
    197
    10
    Hi,
    I have been trying to upgrade windows server 2022 to 2025 with no success, it runs all the setup/upgrade as normal and at the end I get the message that reads 'windows server installation failed'.
    Attached are the 2 logs from C:\old2\Sources\Panther after failed installation and one screenshot I got once after it failed one of the times I tried.. maybe you can suggest a solution...
    Interesting thing is that I can get a clean install just fine on same pc, just upgrade does not work (I tried clean install - I have a macrium backup that I restored so I know it can be installed in this pc - just too much to reinstall and configure back from scratch so I'd like in-place upgrade).
    Any suggestions would be very much appreciated.
    "setupact.log" its too large to add so I am adding a portion/snip of it (last part), hopefully is enough.

    Thanks in advance...
     

    Attached Files:

  2. pm67310

    pm67310 MDL Guru

    Sep 6, 2011
    3,349
    2,521
    120
    Stay at server 2022

    2025 same as windows 11 24h2 very unstable builds atm wait !!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. alien2xx

    alien2xx MDL Senior Member

    Aug 5, 2009
    404
    197
    10
    Thanks for your suggestion, I think I will wait for the next month's release that will be updated with bug fixes, maybe try again then.
     
  4. kaljukass

    kaljukass MDL Guru

    Nov 26, 2012
    3,446
    1,340
    120
    Yes, good suggestion, but it won't help you. Error message 0x80070002 means that some files cannot be found. This could be because some of the downloaded files are missing, or because your current computer has damage directly related to the upgrade.
    If there is a situation that the update package was not fully correct or not fully downloaded, you can clean your computer and download it again. However, if your current Windows has such damage that prevents the upgrade process from proceeding normally, you will need to fix your current OS before upgrading. If it is not possible, it will also fail to update using your desired method and You must to clean install.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. sanjosetour

    sanjosetour MDL Novice

    Apr 18, 2015
    10
    0
    0
    please update us when u can succesfuly upgrade to 2025, what license key are u using for dc desktop version?
     
  6. alien2xx

    alien2xx MDL Senior Member

    Aug 5, 2009
    404
    197
    10
    Sure, I will keep you posted. I am using Server Standard GVLK Volume key against my local kms.
     
  7. atgpud2003

    atgpud2003 MDL Addicted

    Apr 30, 2015
    618
    111
    30
    Keep in 2022 because it stable... 2025 still buggy..

    ATGPUD2003
     
  8. alien2xx

    alien2xx MDL Senior Member

    Aug 5, 2009
    404
    197
    10
    Thanks for the insight..
    I decided to create a full backup image of the system so I can go back and installed 2025 from scratch (as a test)... check if everything works correctly and if drivers are loaded and all went well without any issues; drivers for the full system installed and working properly and also whatever MS patches were available downloaded just fine... I took me part of the weekend to reinstall/configure all my stuff.. I am happy to inform that so far so good and no issues I have encountered, the system seems snappy and I can even say it runs faster and more responsive than 2022.
    It was easier than I thought and gave me the chance to have a clean start (maybe the issue of the in-place upgrade was due to had upgraded originally from 2019 to 2022 version and many patches over the few years I had it already running, not sure).
    I will run it as is for a couple of weeks and see if it works for me - hopefully I don't have to go back to 2022!... I am sure some other people configures the server in a more complex way and they encountered issues (buggy) but so far it seems ok and meet my needs.
    As a test loaded the backup 2022 image to a Hyper-V VM and I had the same issue upgrading, it must be something corrupted within the OS itself so 2025 should do for now, I will try to figure out the upgrade issue using the Hyper-V VM, maybe I can find the solution.
    Thank you again for your suggestion.
     
  9. pm67310

    pm67310 MDL Guru

    Sep 6, 2011
    3,349
    2,521
    120
    2025 = 24h2 big issue stay at 2022 and wait ... you have time no ?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. atgpud2003

    atgpud2003 MDL Addicted

    Apr 30, 2015
    618
    111
    30
    BTW the Windows 2022 (Any Editions) EOL is 2031 so, you may want to stay 2022 for now until Windows 2025 is more stables I had tested and got some odd behaviors with this 2025.. I already bought legit licensee key for now and this way, I am prepare next project on Clean install 2025.. I am gonna wait about a 6 to 8 months (maybe 1 more year?) SO... Keep focus on 2022 on 3 Editions.. Please make good advised to other teams who already have Windows Server 2022 (3 Editions) and as myself too.. Good idea have Virtual Machine to test Windows Server 2025.. ;)

    ATGPUD2003