Windows Server 2012 upgrade stuck at “Getting Ready”
The entire installation process seemed successful without any errors, and yet upon first boot, after completing the "getting devices ready" stage, it goes into a "Getting ready" stage and hangs with the little dots spinning.
This is an upgrade of Windows Server 2008 on a WM Ware Virtual Machine. At first I thought it was an issue with Windows Server 2012 not being supported on VM Ware version 7, but after upgrading to VM Version 9 (ESXi 5.1), the same exact problem occurs. It just sits there and spins forever at "Getting ready".
Does this indicate something is wrong, or should I just wait longer? It's been sitting there for at least half and hour already. The first time I tried this, I just powered it down and tried again and it said the installation could not be completed because it was interrupted, so I had no choice but to revert to the old OS, upgrade the VM version, and try again. But I'm right back at this "Getting ready" screen again.
freeze windows-server-2012 windows-installation
asked Apr 14 '15 at 20:23
TriynkoTriynko
1,51951722
add a comment |
The entire installation process seemed successful without any errors, and yet upon first boot, after completing the "getting devices ready" stage, it goes into a "Getting ready" stage and hangs with the little dots spinning.
This is an upgrade of Windows Server 2008 on a WM Ware Virtual Machine. At first I thought it was an issue with Windows Server 2012 not being supported on VM Ware version 7, but after upgrading to VM Version 9 (ESXi 5.1), the same exact problem occurs. It just sits there and spins forever at "Getting ready".
Does this indicate something is wrong, or should I just wait longer? It's been sitting there for at least half and hour already. The first time I tried this, I just powered it down and tried again and it said the installation could not be completed because it was interrupted, so I had no choice but to revert to the old OS, upgrade the VM version, and try again. But I'm right back at this "Getting ready" screen again.
freeze windows-server-2012 windows-installation
asked Apr 14 '15 at 20:23
TriynkoTriynko
1,51951722
I experienced the same thing on bare metal. I was contemplating a reboot, when finally it came back to life and rebooted on its own. Facts: in my case, I had not wiped the drive -- I was in that situation in which the OS offers to leave you with the windows.old folder Also, the BIOS on the server when back to Nov 2008. I also suspect it may have been testing for linux devices and trying to install drivers for them (?) because when you run HP's SPP (Support Paq for Proliant) it will probe the system and try to determine whichof the500drivers HP might deem the server to need IFlinux were loaded.
– user459492
Jun 16 '15 at 16:22
add a comment |
The entire installation process seemed successful without any errors, and yet upon first boot, after completing the "getting devices ready" stage, it goes into a "Getting ready" stage and hangs with the little dots spinning.
This is an upgrade of Windows Server 2008 on a WM Ware Virtual Machine. At first I thought it was an issue with Windows Server 2012 not being supported on VM Ware version 7, but after upgrading to VM Version 9 (ESXi 5.1), the same exact problem occurs. It just sits there and spins forever at "Getting ready".
Does this indicate something is wrong, or should I just wait longer? It's been sitting there for at least half and hour already. The first time I tried this, I just powered it down and tried again and it said the installation could not be completed because it was interrupted, so I had no choice but to revert to the old OS, upgrade the VM version, and try again. But I'm right back at this "Getting ready" screen again.
freeze windows-server-2012 windows-installation
asked Apr 14 '15 at 20:23
TriynkoTriynko
1,51951722
The entire installation process seemed successful without any errors, and yet upon first boot, after completing the "getting devices ready" stage, it goes into a "Getting ready" stage and hangs with the little dots spinning.
This is an upgrade of Windows Server 2008 on a WM Ware Virtual Machine. At first I thought it was an issue with Windows Server 2012 not being supported on VM Ware version 7, but after upgrading to VM Version 9 (ESXi 5.1), the same exact problem occurs. It just sits there and spins forever at "Getting ready".
Does this indicate something is wrong, or should I just wait longer? It's been sitting there for at least half and hour already. The first time I tried this, I just powered it down and tried again and it said the installation could not be completed because it was interrupted, so I had no choice but to revert to the old OS, upgrade the VM version, and try again. But I'm right back at this "Getting ready" screen again.
freeze windows-server-2012 windows-installation
freeze windows-server-2012 windows-installation
asked Apr 14 '15 at 20:23
TriynkoTriynko
1,51951722
asked Apr 14 '15 at 20:23
TriynkoTriynko
1,51951722
asked Apr 14 '15 at 20:23
TriynkoTriynko
1,51951722
asked Apr 14 '15 at 20:23
TriynkoTriynko
1,51951722
asked Apr 14 '15 at 20:23
TriynkoTriynko
1,51951722
1,51951722
I experienced the same thing on bare metal. I was contemplating a reboot, when finally it came back to life and rebooted on its own. Facts: in my case, I had not wiped the drive -- I was in that situation in which the OS offers to leave you with the windows.old folder Also, the BIOS on the server when back to Nov 2008. I also suspect it may have been testing for linux devices and trying to install drivers for them (?) because when you run HP's SPP (Support Paq for Proliant) it will probe the system and try to determine whichof the500drivers HP might deem the server to need IFlinux were loaded.
– user459492
Jun 16 '15 at 16:22
add a comment |
I experienced the same thing on bare metal. I was contemplating a reboot, when finally it came back to life and rebooted on its own. Facts: in my case, I had not wiped the drive -- I was in that situation in which the OS offers to leave you with the windows.old folder Also, the BIOS on the server when back to Nov 2008. I also suspect it may have been testing for linux devices and trying to install drivers for them (?) because when you run HP's SPP (Support Paq for Proliant) it will probe the system and try to determine whichof the500drivers HP might deem the server to need IFlinux were loaded.
– user459492
Jun 16 '15 at 16:22
I experienced the same thing on bare metal. I was contemplating a reboot, when finally it came back to life and rebooted on its own. Facts: in my case, I had not wiped the drive -- I was in that situation in which the OS offers to leave you with the windows.old folder Also, the BIOS on the server when back to Nov 2008. I also suspect it may have been testing for linux devices and trying to install drivers for them (?) because when you run HP's SPP (Support Paq for Proliant) it will probe the system and try to determine whichof the500drivers HP might deem the server to need IFlinux were loaded.
– user459492
Jun 16 '15 at 16:22
I experienced the same thing on bare metal. I was contemplating a reboot, when finally it came back to life and rebooted on its own. Facts: in my case, I had not wiped the drive -- I was in that situation in which the OS offers to leave you with the windows.old folder Also, the BIOS on the server when back to Nov 2008. I also suspect it may have been testing for linux devices and trying to install drivers for them (?) because when you run HP's SPP (Support Paq for Proliant) it will probe the system and try to determine whichof the500drivers HP might deem the server to need IFlinux were loaded.
– user459492
Jun 16 '15 at 16:22
add a comment |
4 Answers
4
active
oldest
votes
I decided to just wait it out this time. After almost an hour, it finally finished successfully.
I have no idea why it took so long. Perhaps it was some kind of network timeout. After upgrading the VM hardware, I noticed the network card must have changed, because I lost all my network settings (IP addresses, VPN settings, etc.). I'm going to try to recover them from the registry settings for the old card if possible. Anyone know of any good utilities for doing so?
answered Apr 14 '15 at 20:51
TriynkoTriynko
1,51951722
Had the same problem, did exactly what you did and just left it to play the second time - there were some errors to clear up but seems to be stable enough to move on to Server 2016 > 2019 upgrades now
– gchq
Dec 9 '18 at 19:23
add a comment |
I experienced this as well going upgrading from Windows Server 2008 R2 to Windows Server 2012 R2. Watching that Getting ready sit there forever was maddening and I was about to punch the monitor. But changing the NIC (network/ethernet) card worked. I was using VMware VMXNet 3 removed that and used Intel E1000 instead. That worked like a charm. What a PITA though!
answered Jul 1 '17 at 13:36
Irate SysAdmins IncorporatedIrate SysAdmins Incorporated
1
add a comment |
Establish a link with your disconnected NICs. This "problem" goes as far back as SBS 2000 or 2003, AFAI remember.
If you're an integration house or system builder, keep a cheap powered-on switch nearby. It isn't looking to make connection to anything. It just needs a link status of not disconnected.
danielkr
answered Oct 9 '18 at 14:50
user2961382user2961382
1
add a comment |
Can confirm this also happened when I tried to in-place upgrade our DC from 2008 R2 to 2012 R2. Disconnecting the NIC in VMware immediately resolved the "Getting Ready" freezing issue.
answered Jan 11 at 15:44
SDevinoSDevino
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f901604%2fwindows-server-2012-upgrade-stuck-at-getting-ready%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
I decided to just wait it out this time. After almost an hour, it finally finished successfully.
I have no idea why it took so long. Perhaps it was some kind of network timeout. After upgrading the VM hardware, I noticed the network card must have changed, because I lost all my network settings (IP addresses, VPN settings, etc.). I'm going to try to recover them from the registry settings for the old card if possible. Anyone know of any good utilities for doing so?
answered Apr 14 '15 at 20:51
TriynkoTriynko
1,51951722
Had the same problem, did exactly what you did and just left it to play the second time - there were some errors to clear up but seems to be stable enough to move on to Server 2016 > 2019 upgrades now
– gchq
Dec 9 '18 at 19:23
add a comment |
I decided to just wait it out this time. After almost an hour, it finally finished successfully.
I have no idea why it took so long. Perhaps it was some kind of network timeout. After upgrading the VM hardware, I noticed the network card must have changed, because I lost all my network settings (IP addresses, VPN settings, etc.). I'm going to try to recover them from the registry settings for the old card if possible. Anyone know of any good utilities for doing so?
answered Apr 14 '15 at 20:51
TriynkoTriynko
1,51951722
Had the same problem, did exactly what you did and just left it to play the second time - there were some errors to clear up but seems to be stable enough to move on to Server 2016 > 2019 upgrades now
– gchq
Dec 9 '18 at 19:23
add a comment |
I decided to just wait it out this time. After almost an hour, it finally finished successfully.
I have no idea why it took so long. Perhaps it was some kind of network timeout. After upgrading the VM hardware, I noticed the network card must have changed, because I lost all my network settings (IP addresses, VPN settings, etc.). I'm going to try to recover them from the registry settings for the old card if possible. Anyone know of any good utilities for doing so?
answered Apr 14 '15 at 20:51
TriynkoTriynko
1,51951722
I decided to just wait it out this time. After almost an hour, it finally finished successfully.
I have no idea why it took so long. Perhaps it was some kind of network timeout. After upgrading the VM hardware, I noticed the network card must have changed, because I lost all my network settings (IP addresses, VPN settings, etc.). I'm going to try to recover them from the registry settings for the old card if possible. Anyone know of any good utilities for doing so?
answered Apr 14 '15 at 20:51
TriynkoTriynko
1,51951722
answered Apr 14 '15 at 20:51
TriynkoTriynko
1,51951722
answered Apr 14 '15 at 20:51
TriynkoTriynko
1,51951722
answered Apr 14 '15 at 20:51
TriynkoTriynko
1,51951722
1,51951722
Had the same problem, did exactly what you did and just left it to play the second time - there were some errors to clear up but seems to be stable enough to move on to Server 2016 > 2019 upgrades now
– gchq
Dec 9 '18 at 19:23
add a comment |
Had the same problem, did exactly what you did and just left it to play the second time - there were some errors to clear up but seems to be stable enough to move on to Server 2016 > 2019 upgrades now
– gchq
Dec 9 '18 at 19:23
Had the same problem, did exactly what you did and just left it to play the second time - there were some errors to clear up but seems to be stable enough to move on to Server 2016 > 2019 upgrades now
– gchq
Dec 9 '18 at 19:23
Had the same problem, did exactly what you did and just left it to play the second time - there were some errors to clear up but seems to be stable enough to move on to Server 2016 > 2019 upgrades now
– gchq
Dec 9 '18 at 19:23
add a comment |
I experienced this as well going upgrading from Windows Server 2008 R2 to Windows Server 2012 R2. Watching that Getting ready sit there forever was maddening and I was about to punch the monitor. But changing the NIC (network/ethernet) card worked. I was using VMware VMXNet 3 removed that and used Intel E1000 instead. That worked like a charm. What a PITA though!
answered Jul 1 '17 at 13:36
Irate SysAdmins IncorporatedIrate SysAdmins Incorporated
1
add a comment |
I experienced this as well going upgrading from Windows Server 2008 R2 to Windows Server 2012 R2. Watching that Getting ready sit there forever was maddening and I was about to punch the monitor. But changing the NIC (network/ethernet) card worked. I was using VMware VMXNet 3 removed that and used Intel E1000 instead. That worked like a charm. What a PITA though!
answered Jul 1 '17 at 13:36
Irate SysAdmins IncorporatedIrate SysAdmins Incorporated
1
add a comment |
I experienced this as well going upgrading from Windows Server 2008 R2 to Windows Server 2012 R2. Watching that Getting ready sit there forever was maddening and I was about to punch the monitor. But changing the NIC (network/ethernet) card worked. I was using VMware VMXNet 3 removed that and used Intel E1000 instead. That worked like a charm. What a PITA though!
answered Jul 1 '17 at 13:36
Irate SysAdmins IncorporatedIrate SysAdmins Incorporated
1
I experienced this as well going upgrading from Windows Server 2008 R2 to Windows Server 2012 R2. Watching that Getting ready sit there forever was maddening and I was about to punch the monitor. But changing the NIC (network/ethernet) card worked. I was using VMware VMXNet 3 removed that and used Intel E1000 instead. That worked like a charm. What a PITA though!
answered Jul 1 '17 at 13:36
Irate SysAdmins IncorporatedIrate SysAdmins Incorporated
1
answered Jul 1 '17 at 13:36
Irate SysAdmins IncorporatedIrate SysAdmins Incorporated
1
answered Jul 1 '17 at 13:36
Irate SysAdmins IncorporatedIrate SysAdmins Incorporated
1
answered Jul 1 '17 at 13:36
Irate SysAdmins IncorporatedIrate SysAdmins Incorporated
1
1
add a comment |
add a comment |
Establish a link with your disconnected NICs. This "problem" goes as far back as SBS 2000 or 2003, AFAI remember.
If you're an integration house or system builder, keep a cheap powered-on switch nearby. It isn't looking to make connection to anything. It just needs a link status of not disconnected.
danielkr
answered Oct 9 '18 at 14:50
user2961382user2961382
1
add a comment |
Establish a link with your disconnected NICs. This "problem" goes as far back as SBS 2000 or 2003, AFAI remember.
If you're an integration house or system builder, keep a cheap powered-on switch nearby. It isn't looking to make connection to anything. It just needs a link status of not disconnected.
danielkr
answered Oct 9 '18 at 14:50
user2961382user2961382
1
add a comment |
Establish a link with your disconnected NICs. This "problem" goes as far back as SBS 2000 or 2003, AFAI remember.
If you're an integration house or system builder, keep a cheap powered-on switch nearby. It isn't looking to make connection to anything. It just needs a link status of not disconnected.
danielkr
answered Oct 9 '18 at 14:50
user2961382user2961382
1
Establish a link with your disconnected NICs. This "problem" goes as far back as SBS 2000 or 2003, AFAI remember.
If you're an integration house or system builder, keep a cheap powered-on switch nearby. It isn't looking to make connection to anything. It just needs a link status of not disconnected.
danielkr
answered Oct 9 '18 at 14:50
user2961382user2961382
1
answered Oct 9 '18 at 14:50
user2961382user2961382
1
answered Oct 9 '18 at 14:50
user2961382user2961382
1
answered Oct 9 '18 at 14:50
user2961382user2961382
1
1
add a comment |
add a comment |
Can confirm this also happened when I tried to in-place upgrade our DC from 2008 R2 to 2012 R2. Disconnecting the NIC in VMware immediately resolved the "Getting Ready" freezing issue.
answered Jan 11 at 15:44
SDevinoSDevino
1
add a comment |
Can confirm this also happened when I tried to in-place upgrade our DC from 2008 R2 to 2012 R2. Disconnecting the NIC in VMware immediately resolved the "Getting Ready" freezing issue.
answered Jan 11 at 15:44
SDevinoSDevino
1
add a comment |
Can confirm this also happened when I tried to in-place upgrade our DC from 2008 R2 to 2012 R2. Disconnecting the NIC in VMware immediately resolved the "Getting Ready" freezing issue.
answered Jan 11 at 15:44
SDevinoSDevino
1
Can confirm this also happened when I tried to in-place upgrade our DC from 2008 R2 to 2012 R2. Disconnecting the NIC in VMware immediately resolved the "Getting Ready" freezing issue.
answered Jan 11 at 15:44
SDevinoSDevino
1
answered Jan 11 at 15:44
SDevinoSDevino
1
answered Jan 11 at 15:44
SDevinoSDevino
1
answered Jan 11 at 15:44
SDevinoSDevino
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f901604%2fwindows-server-2012-upgrade-stuck-at-getting-ready%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I experienced the same thing on bare metal. I was contemplating a reboot, when finally it came back to life and rebooted on its own. Facts: in my case, I had not wiped the drive -- I was in that situation in which the OS offers to leave you with the windows.old folder Also, the BIOS on the server when back to Nov 2008. I also suspect it may have been testing for linux devices and trying to install drivers for them (?) because when you run HP's SPP (Support Paq for Proliant) it will probe the system and try to determine whichof the500drivers HP might deem the server to need IFlinux were loaded.
– user459492
Jun 16 '15 at 16:22