Exact same scenario for me. Going from 2012R2 to 2022 on a hyper-v role. I’ve done 6 of these so far without issue. For whatever reason, this one wanted to be a pain. I always disable antivirus before starting the upgrade, so that wasn’t the issue. Took me three tries before I got it by “DISABLING THE NETWORK ADAPTER BEFORE STARTING THE UPGRADE”. It’s working now! Thanks for the video.
@@sengdao3 I think so. I believe I tried unchecking the “install updates” first and that didn’t work. So maybe both of them just to be sure, disable network and uncheck the “install updates”.
Thanks, man! I ran into the same error, and on the same platform- VMware esxi. I had the same thing for another server but I decided to do clean reinstall for that one. Antivirus was already uninstalled but I still got the error. The only piece I was missing- was to disconnect the NIC, thanks to you, the upgrade from Server 2012 R2 to Server 2022 finished successfully! the only downside is that it takes some time to catch up with the updates.
That’s excellent to hear. I found on my next try that I didn’t have to disable my NIC, but I opted to not apply updates on the first screen of the Wizard and it went through.
I believe removing the option to install updates is the cause of this error - just tested it.The possible network adapter issue could be incompatibility - in this case the installation would have told you the adapter [vm adapter in my case] must be removed
I was doing in in place upgrade to Windows Server 2019 from 2012 r2 and was having the same issue. Upgrading the VM hardware to match the host worked. I tried the steps from the video without success but the video gave me the idea. Thank you.
I ran into this error going from 2019 to 2022. What I did was uncheck the option to install the updates. The server than successfully did an in place upgrade.
im running into this right now..only thing i didnt do differently was disable the vmxnet3 adapter so ill try that as ive done all the others. I also upgraded the tools but no luck with that..UPDATE - that didnt work either. I lock up on boot, have to power off the VM, power on and then it comes back to 2012R2 and i get the error. Crazy...
An update to this don't use a newer Windows 2022 .iso. I still had that problem with the newer .iso but also had the RTM release which worked fine combined with not allowing updates to install during installation.
I ran across this same situation this morning. I tried uninstalling Antivirus first and installing the upgrade, which yielded the same error. I disabled the network adapter and ran the upgrade again. This time it completed. I'll try that step first on the next server to upgrade.
help my We couldn't install Windows 11 We've set your PC back to the way it was right before you started installing Windows 11. OxC1900101 -Ox20017 The installation failed in the SAFE_ OS phase with an error during BOOT operation
I have the same problem. I'm trying to upgrade from windows 11 21h2 to 22h2 and it displaying this same error you've posted. Have you found a way around it and please help if you have?
I was trying to go from Win 10 Ver 1909 to 22H2. So this is what I did....using the media I created for the install(Windows iso DVD), I had to update my BIOS to the latest version, and then tried again and unplugged all external USB devices before the reboot. It worked like a charm. I believe the issue was really related to my old BIOS version (it was over 5 yrs old 😞)...but either both of one of those two things fixed this issue for me. Hope this helps someone.
UPDATE: All I had to do was uncheck the option to not allow / don't install updates at the beginning of the Install Wizard.
I can vouch for that!
Yes! I suggest before doing anything else, do this first.
I think it's all about drivers issues
Exact same scenario for me. Going from 2012R2 to 2022 on a hyper-v role. I’ve done 6 of these so far without issue. For whatever reason, this one wanted to be a pain. I always disable antivirus before starting the upgrade, so that wasn’t the issue. Took me three tries before I got it by “DISABLING THE NETWORK ADAPTER BEFORE STARTING THE UPGRADE”. It’s working now! Thanks for the video.
Did you have to disable network adapter and then uncheck the install updates then proceed with the in-place OS upgrade?
@@sengdao3 I think so. I believe I tried unchecking the “install updates” first and that didn’t work. So maybe both of them just to be sure, disable network and uncheck the “install updates”.
@@alohaitguy6891 but what if it doesn't give us the option to uncheck the update
Thanks, man! I ran into the same error, and on the same platform- VMware esxi.
I had the same thing for another server but I decided to do clean reinstall for that one.
Antivirus was already uninstalled but I still got the error.
The only piece I was missing- was to disconnect the NIC, thanks to you, the upgrade from Server 2012 R2 to Server 2022 finished successfully! the only downside is that it takes some time to catch up with the updates.
That’s excellent to hear. I found on my next try that I didn’t have to disable my NIC, but I opted to not apply updates on the first screen of the Wizard and it went through.
@@technubawhere
I believe removing the option to install updates is the cause of this error - just tested it.The possible network adapter issue could be incompatibility - in this case the installation would have told you the adapter [vm adapter in my case] must be removed
I was doing in in place upgrade to Windows Server 2019 from 2012 r2 and was having the same issue. Upgrading the VM hardware to match the host worked. I tried the steps from the video without success but the video gave me the idea. Thank you.
Make sure you check your VM compatibility level as well.
Thanks for reminding me, this was also my issue.
Which antivirus did you uninstall? I can't seem to uninstall the one included with Windows.
I ran into this error going from 2019 to 2022. What I did was uncheck the option to install the updates. The server than successfully did an in place upgrade.
Where
im running into this right now..only thing i didnt do differently was disable the vmxnet3 adapter so ill try that as ive done all the others. I also upgraded the tools but no luck with that..UPDATE - that didnt work either. I lock up on boot, have to power off the VM, power on and then it comes back to 2012R2 and i get the error. Crazy...
For me, once I cleared all the snapshots I found that the upgrade went flawlessly
what do you mean by cleared the snapshots? thanks
An update to this don't use a newer Windows 2022 .iso. I still had that problem with the newer .iso but also had the RTM release which worked fine combined with not allowing updates to install during installation.
I ran across this same situation this morning. I tried uninstalling Antivirus first and installing the upgrade, which yielded the same error. I disabled the network adapter and ran the upgrade again. This time it completed. I'll try that step first on the next server to upgrade.
Bro plz tell me
In my it's not working
help my
We couldn't install Windows 11
We've set your PC back to the way it was right before you started installing Windows 11.
OxC1900101 -Ox20017
The installation failed in the SAFE_ OS phase with an error during BOOT operation
I have the same problem. I'm trying to upgrade from windows 11 21h2 to 22h2 and it displaying this same error you've posted. Have you found a way around it and please help if you have?
@@glennmbilishi3542i have same problem too, how to fix it?
@@RendiApakah u guys ever figure this out? still cant update it myself
@@PhrostOG yeah having same problem, ill try my best to find a solution ill come back after getting it fixed
DISABLING THE NETWORK ADAPTER BEFORE STARTING THE UPGRADE AND USE THE FIRST ISO RELEASE OF 2022 SERVER
Thanks, this worked for me too
I got second_boot phase. Any help?
Did'nt work for me in any way. Tried chaging the Network from VMXNET3 to E1000 to.
Did you try telling windows to not apply updates? It’s one of the first choices. I think it’s a checkbox.
I was trying to go from Win 10 Ver 1909 to 22H2. So this is what I did....using the media I created for the install(Windows iso DVD), I had to update my BIOS to the latest version, and then tried again and unplugged all external USB devices before the reboot. It worked like a charm. I believe the issue was really related to my old BIOS version (it was over 5 yrs old 😞)...but either both of one of those two things fixed this issue for me. Hope this helps someone.
Thank yoyy❤
Bro I love you❤
@@Johnpradhan-u6s Glad it helped!!
I was struggling 2 3 days
And I read your comment God bless you
Gracias, quitando las actualizaciones ya funciona.
It did not work for me but I fix it by updating the gpu driver with gefore now