Ryfujk

An Undercover Army

Will the concrete slab in a partially heated shed conduct a lot of heat to the unconditioned area?

Does the US political system, in principle, allow for a no-party system?

What is the purpose of a disclaimer like "this is not legal advice"?

Can multiple states demand income tax from an LLC?

If nine coins are tossed, what is the probability that the number of heads is even?

Can I challenge the interviewer to give me a proper technical feedback?

How does learning spells work when leveling a multiclass character?

Is it a Cyclops number? "Nobody" knows!

How do you make a gun that shoots melee weapons and/or swords?

Why do we say 'Pairwise Disjoint', rather than 'Disjoint'?

Too soon for a plot twist?

Paper published similar to PhD thesis

What does *dead* mean in *What do you mean, dead?*?

Draw this image in the TIKZ package

Insult for someone who "doesn't know anything"

What can I do if someone tampers with my SSH public key?

Why do we call complex numbers “numbers” but we don’t consider 2-vectors numbers?

Short story about an infectious indestructible metal bar?

Why restrict private health insurance?

Short story about cities being connected by a conveyor belt

Precision notation for voltmeters

Use Mercury as quenching liquid for swords?

Giving a talk in my old university, how prominently should I tell students my salary?

Windows server 2019 fails after hyper-v role install

Does adding Hyper-V role affect host server performance when no guests are running?Hyper-V host - PFN_LIST_CORRUPTWindows Server 2008 Stops Responding (Hyper-V Role Enabled)How to install windows server 2008 r2 Hyper-V on Windows 7, through virtual machine?Is it Ok to remove the Hyper-V role from Windows Server 2008 R2Removing Hyper-V role from Windows Server 2012 R2Windows Server 2012 R2 (Hyper-V VMs) - random BSODStorage Pool Keeps Disconnecting After Reboot on Hyper-VError 0xc0000225 after Hyper-V Role Install Win 2012 - A Required device isn't connected or can't be accessedCannot remote connect to Windows 2019 core

2

1

I have an HP MicroServer that I use for dev/test. I've successfully installed Windows 2019 Server Standard on it (a dozen times now!) - and everything works great until I add the Hyper-V role. (This server was previously running Windows Server 2016 with Hyper-V with no issues.)

Once I add the Hyper-V role, and reboot, the thing just goes into a boot loop. When the boot loop happens, there is no BSOD, just a reboot every time. I've tried to boot into "safe mode" and remove the role, but even after doing that, it just continues in a reboot loop. After a few failed boots, it'll kick into the automatic repair screen, and that appears to be no help.

What is the best way to troubleshoot this and get Hyper-V installed? I've tried adding the role via the server manager, powershell, the new Windows Admin Center - and have the same results every time. Am I missing some sort of prerequisite for Hyper-V that the installer isn't adding automatically?

hyper-v windows-server-2019

share|improve this question

edited Oct 26 '18 at 15:48

bodgit

3,534925

asked Oct 26 '18 at 15:42

Scott IveyScott Ivey

4251518

add a comment | 

2

1

I have an HP MicroServer that I use for dev/test. I've successfully installed Windows 2019 Server Standard on it (a dozen times now!) - and everything works great until I add the Hyper-V role. (This server was previously running Windows Server 2016 with Hyper-V with no issues.)

Once I add the Hyper-V role, and reboot, the thing just goes into a boot loop. When the boot loop happens, there is no BSOD, just a reboot every time. I've tried to boot into "safe mode" and remove the role, but even after doing that, it just continues in a reboot loop. After a few failed boots, it'll kick into the automatic repair screen, and that appears to be no help.

What is the best way to troubleshoot this and get Hyper-V installed? I've tried adding the role via the server manager, powershell, the new Windows Admin Center - and have the same results every time. Am I missing some sort of prerequisite for Hyper-V that the installer isn't adding automatically?

hyper-v windows-server-2019

share|improve this question

edited Oct 26 '18 at 15:48

bodgit

3,534925

asked Oct 26 '18 at 15:42

Scott IveyScott Ivey

4251518

add a comment | 

I have an HP MicroServer that I use for dev/test. I've successfully installed Windows 2019 Server Standard on it (a dozen times now!) - and everything works great until I add the Hyper-V role. (This server was previously running Windows Server 2016 with Hyper-V with no issues.)

Once I add the Hyper-V role, and reboot, the thing just goes into a boot loop. When the boot loop happens, there is no BSOD, just a reboot every time. I've tried to boot into "safe mode" and remove the role, but even after doing that, it just continues in a reboot loop. After a few failed boots, it'll kick into the automatic repair screen, and that appears to be no help.

What is the best way to troubleshoot this and get Hyper-V installed? I've tried adding the role via the server manager, powershell, the new Windows Admin Center - and have the same results every time. Am I missing some sort of prerequisite for Hyper-V that the installer isn't adding automatically?

hyper-v windows-server-2019

share|improve this question

edited Oct 26 '18 at 15:48

bodgit

3,534925

asked Oct 26 '18 at 15:42

Scott IveyScott Ivey

4251518

share|improve this question

edited Oct 26 '18 at 15:48

bodgit

3,534925

asked Oct 26 '18 at 15:42

Scott IveyScott Ivey

4251518

share|improve this question

edited Oct 26 '18 at 15:48

bodgit

3,534925

asked Oct 26 '18 at 15:42

Scott IveyScott Ivey

4251518

edited Oct 26 '18 at 15:48

bodgit

3,534925

edited Oct 26 '18 at 15:48

bodgit

3,534925

asked Oct 26 '18 at 15:42

Scott IveyScott Ivey

4251518

asked Oct 26 '18 at 15:42

Scott IveyScott Ivey

4251518

2 Answers
2

active

oldest

votes

2

In fact Windows 2019 is very buggy now. I would suggest avoiding it for now and wait for the new stable release.

According to the Microsoft Evaluation Center:

"We have temporarily removed all media for Windows Server 2019 and Windows Server, version 1809. We have also paused the rollout of the latest feature update to Windows 10 inclusive of versions 1809, as we are investigating isolated reports of users missing some files after updating. If you have already downloaded media, please don’t install it and wait until more information is available to proceed. We apologize for any inconvenience this may have caused. We will provide an update when refreshed media is available. For reference, we also have a support article with additional information."

However, you can try a possible workaround - install Windows 2019 in BIOS (Legacy) mode instead of UEFI and then Hyper-V should not cause the boot loop.

share|improve this answer

answered Nov 5 '18 at 10:07

batistuta09batistuta09

3,598410

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Yes - i'm aware of those issues. Since I was wiping the machine, none of the upgrade data loss issues affected me. This machine does have BIOS instead of UEFI - i'm unaware of any "mode" to choose during the install, am I missing something?
  
  – Scott Ivey
  Nov 5 '18 at 14:56
  

  
  
  
  

add a comment | 

0

I'm having a similar problem, I might just do Server 2016 for now as this is a major problem.

share|improve this answer

answered 14 mins ago

user513571

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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
});


}
});

draft saved

draft discarded

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

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f937402%2fwindows-server-2019-fails-after-hyper-v-role-install%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

2

In fact Windows 2019 is very buggy now. I would suggest avoiding it for now and wait for the new stable release.

According to the Microsoft Evaluation Center:

"We have temporarily removed all media for Windows Server 2019 and Windows Server, version 1809. We have also paused the rollout of the latest feature update to Windows 10 inclusive of versions 1809, as we are investigating isolated reports of users missing some files after updating. If you have already downloaded media, please don’t install it and wait until more information is available to proceed. We apologize for any inconvenience this may have caused. We will provide an update when refreshed media is available. For reference, we also have a support article with additional information."

However, you can try a possible workaround - install Windows 2019 in BIOS (Legacy) mode instead of UEFI and then Hyper-V should not cause the boot loop.

share|improve this answer

answered Nov 5 '18 at 10:07

batistuta09batistuta09

3,598410

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Yes - i'm aware of those issues. Since I was wiping the machine, none of the upgrade data loss issues affected me. This machine does have BIOS instead of UEFI - i'm unaware of any "mode" to choose during the install, am I missing something?
  
  – Scott Ivey
  Nov 5 '18 at 14:56
  

  
  
  
  

add a comment | 

2

In fact Windows 2019 is very buggy now. I would suggest avoiding it for now and wait for the new stable release.

According to the Microsoft Evaluation Center:

"We have temporarily removed all media for Windows Server 2019 and Windows Server, version 1809. We have also paused the rollout of the latest feature update to Windows 10 inclusive of versions 1809, as we are investigating isolated reports of users missing some files after updating. If you have already downloaded media, please don’t install it and wait until more information is available to proceed. We apologize for any inconvenience this may have caused. We will provide an update when refreshed media is available. For reference, we also have a support article with additional information."

However, you can try a possible workaround - install Windows 2019 in BIOS (Legacy) mode instead of UEFI and then Hyper-V should not cause the boot loop.

share|improve this answer

answered Nov 5 '18 at 10:07

batistuta09batistuta09

3,598410

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Yes - i'm aware of those issues. Since I was wiping the machine, none of the upgrade data loss issues affected me. This machine does have BIOS instead of UEFI - i'm unaware of any "mode" to choose during the install, am I missing something?
  
  – Scott Ivey
  Nov 5 '18 at 14:56
  

  
  
  
  

add a comment | 

In fact Windows 2019 is very buggy now. I would suggest avoiding it for now and wait for the new stable release.

According to the Microsoft Evaluation Center:

"We have temporarily removed all media for Windows Server 2019 and Windows Server, version 1809. We have also paused the rollout of the latest feature update to Windows 10 inclusive of versions 1809, as we are investigating isolated reports of users missing some files after updating. If you have already downloaded media, please don’t install it and wait until more information is available to proceed. We apologize for any inconvenience this may have caused. We will provide an update when refreshed media is available. For reference, we also have a support article with additional information."

However, you can try a possible workaround - install Windows 2019 in BIOS (Legacy) mode instead of UEFI and then Hyper-V should not cause the boot loop.

share|improve this answer

answered Nov 5 '18 at 10:07

batistuta09batistuta09

3,598410

share|improve this answer

answered Nov 5 '18 at 10:07

batistuta09batistuta09

3,598410

answered Nov 5 '18 at 10:07

batistuta09batistuta09

3,598410

answered Nov 5 '18 at 10:07

batistuta09batistuta09

3,598410