[Solved] Server 2012 R2 re-install/repair (for in-place upgrade fix)

Discussion in 'Windows Server' started by sebus, Sep 4, 2023.

  1. sebus

    sebus MDL Guru

    Jul 23, 2008
    6,384
    2,037
    210
    #1 sebus, Sep 4, 2023
    Last edited: Sep 7, 2023
  2. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    4,003
    2,923
    150
    It's bare metal or a VM?

    If it's a HV VM boot it using vmware, do the in place upgrade then reboot normally in HV.
     
  3. sebus

    sebus MDL Guru

    Jul 23, 2008
    6,384
    2,037
    210
    #3 sebus, Sep 4, 2023
    Last edited: Sep 7, 2023
    (OP)
    .
     
  4. LiteOS

    LiteOS Windowizer

    Mar 7, 2014
    2,343
    1,047
    90
    is there more info in the logs at the Panther folder ?
    $windows. xx folders
     
  5. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    4,003
    2,923
    150
    #5 acer-5100, Sep 4, 2023
    Last edited: Sep 5, 2023
    Then, like LiteOS said check the logs in the panther folders both in the hidden folder in the root and/or C:\windows, for any clue.

    Also keep in ind that sometimes setup estimates wrongly the space needed for the in place upgrade, allowing it even when the free space is not enough.

    So be sure you have plenty of free space, say at least 25 GB even if 16GB should be enough

    Also remove any AV/Antimalware you may have installed before attempting the upgrade
     
  6. atgpud2003

    atgpud2003 MDL Addicted

    Apr 30, 2015
    618
    111
    30
    Umm, I tried both way Windows Server 2019 on Bare PC or VM and never had a problems.. I SUGGEST to use 64GB SSD or bigger on C: Drive. Mostly Microsoft as recommended 60GB or bigger..For VMware or Virtual Machine is default 60GB or more depending your harddrive/SSD spaces to able run... Pretty straight forward..

    ATGPUD2003
     
  7. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,201
    90,743
    340
    That didn't work too?
     
  8. sebus

    sebus MDL Guru

    Jul 23, 2008
    6,384
    2,037
    210
    #8 sebus, Sep 7, 2023
    Last edited: Sep 7, 2023
    (OP)
    NO, did not do it after all, gave upgrade one more go with Disk2vhd and temporary VM in Virtualbox, but this time disabled a whole bunch of HP related services (that started even when not running any more on HP hardware), fixed missing Recovery partition (picked winre.wim from backup), 2019 upgrade still failed, but 2022 did upgrade correctly.
    Cloned it back to SSD & the server is happy again (as is me)

    Then had fun with ReFS version 1.2 (Server 2012 R2) not being read on 2022, had to boot with WinPE from ADK 8.1, copy data to USB drive, copy it back to newly formatted ReFS 3.4

    So what should have been an hour affair, ended up being 3 days exercise
    At least finished well