Discussion in 'Windows Server' started by sebus, Sep 4, 2023.
You need to login to view this posts content.
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.
is there more info in the logs at the Panther folder ?
$windows. xx folders
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
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..
That didn't work too?
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