none
WIndows 2012 Upgrade - Black Screen

    Question

  • Hi,

    I was trying to upgrade from windows 2008 r2 sp1 DC to windows 2012. Once the installation is complete the system boots with black screen with a mouse cursor and stays like that. It does not display anything. I need to rollback the installation...

    Any help would be appreciated

    Thanks

    Wednesday, September 05, 2012 7:10 AM

Answers

  • See MKSB 2734222

    Title: An upgrade to Windows Server 2012 Release Candidate is not completed
    successfully on a server that is running the domain controller role or the DNS
    server role

    V 1.0 of the article is "release candidate" centric but the problem applies equally to the RTM release of Windows Server 2012.

    The Windows product team researched the fresh install vs. in-place upgrade topic and found that given the 5-7 year useful life and criticality of a server-class OS release, the overwhelming # of IT Admins strongly preferred fresh OS installs on critical server-role computers to avoid persisting a configuration or upgrade-specific problem from the previous OS version. That was my personal take when asked. The Microsoft IT group is a strong proponent of fresh installs during OS version upgrades (and beyond) and would have certainly influenced the discussion. Of course, there are always exceptions as this this is pointing out.

    Continuing to reboot the in-place upgraded server-core DC should detect the failed upgrade and trigger rollback to the previous OS version and state. Please reply back to the thread if that is not the case.

    From there you can promote new full or core replica DCs on new virtual or physical machines and retire the old W2K8 R2 DCs as required.

    Is anyone on this thread encountering an in-place upgrade failure on a GUI (i.e. non-server core) DC?

    Also, for the benefit of those reading the thread, are the server-core DCs that are failing in-place upgrade production DCs, or lab | test DCs?


    Tuesday, October 09, 2012 12:03 AM

All replies

  • Yes, I Have this problem too.

    I install update An update that enables Windows 8 or Windows Server 2012 to be hosted in a Hyper-V virtual machine on Windows Server 2008 R2but it not resolve the problem :-(

    I have one unsupported device during installation: "Microsoft Emulated S3 Device Cap"


    Не забывайте отмечать поcты как ответы, а также помечать полезные сообщения!



    Wednesday, September 05, 2012 9:33 AM
  • i hope the update is required when we are running win 2012 as VM in win 2008 r2 hyper v....since i am doing the upgrade in physical machine i did not apply the update. i did not have any unsupported device reported at the time of installation... the installation completes all the steps and when it restarts it stays black with arrow mouse cursor..
    Wednesday, September 05, 2012 11:03 AM
  • I'm upgrade VM (w2k8r2 std core) and have some symptoms:  it stays black with arrow mouse cursor..

    Не забывайте отмечать поcты как ответы, а также помечать полезные сообщения!


    Wednesday, September 05, 2012 11:40 AM
  • Hi,

    If you would like to do the upgrade Domain controller to Windows Server 2012, I think you need to first take a look at this article especially the requirements and prerequisites:

    Title: Upgrade Domain Controllers to Windows Server 2012

    URL: http://technet.microsoft.com/en-us/library/hh994618.aspx

    At the same time, there ia an additional article for you with snapshot procedures:

    Upgrading Active Directory to Windows Server 2012 (Screenshot Gallery)

    Regards,

    James


    James Xiong

    TechNet Community Support

    Friday, September 07, 2012 7:40 AM
    Moderator
  • thanks for the info...i followed the technet document and ended up with black screen. i gave up and installed from scratch..which works fine in the same machine.

    Regards

    Friday, September 07, 2012 1:06 PM
  • Hi,

    i would like to update a Hyper-V Gest: Guest OS: Windows Server 2008 R2 (with SQL Server 2008 )
    Problem says: System Device: Microsoft Emulated S3 Device Cap

    it was a testserver... therefore i ignored the message....

    • Rebbot VM
    • thame message
    • Continue
    • and run

    I have to check the error messages f.e:
    The Network Connectivity Assistant service depends on the IP Helper service which failed to start because of the following error:
    The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
    The time service encountered an error and was forced to shut down. The error was: 0x80070700: An attempt was made to logon, but the network logon service was not started.
    The Windows Time service terminated with the following error: An attempt was made to logon, but the network logon service was not started.
    The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.
    The WinRM service is not listening for WS-Management requests.
    The Network List Service service terminated with the following error: The device is not ready.
    Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

    But the system is running !


    Hans Brender, sqtm

    Friday, September 07, 2012 1:51 PM
  • Uninstall the graphics driver on Windows Server 2008 R2 and upgrade. Then use Windows Update to reinstall graphics driver.

    Best Regards,


    Steve Kline
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Technology Specialist: Active Directory, Network Infrastructure, Application Platform, Windows 7
    Microsoft Certified Product Specialist & Network Product Specialist
    Red Hat Certified System Administrator
    Microsoft® Community Contributor Award 2011
    All opinions expressed on my own behalf and not that of my company.
    This posting is "as is" without warranties and confers no rights.

    Friday, September 07, 2012 2:33 PM
  • Same issue, just did in place upgrade in 2008 R2 and now have a black screen. I will try to rollback and remove the display driver however that's a pretty sorry work around if you ask me. Better testing should be have been done to make this a rare occurrence. 
    Saturday, September 15, 2012 10:41 PM
  • After rolling back I found that I was already using the windows generic vga driver. I suspected I probably was, old habit from x86 days trying to eek out every kb of non-paged pool memory possible. Does anyone where I might be able to find a log from the upgrade that may show what was failing? Looked at the system logs and didn't see anything. 
    Sunday, September 16, 2012 1:30 AM
  • Same issue. I have two Domain Controllers running as 2008 R2 Core. When I try and upgrade to 2012, I get a blank screen with the curser. If I reboot, I can boot it in safe mode which prompt it to revert back to 2008 R2

    Both these machines are test machines running in VMWare Player.

    Tuesday, September 25, 2012 10:25 PM
  • Do you have the latest version of VMware Player?  Earlier versions did not support 2012.


    tim

    Tuesday, September 25, 2012 11:22 PM
  • Are you looking at the C:\Windows\Panther log files?

    tim

    Tuesday, September 25, 2012 11:24 PM
  • This has happened to me too. I upgraded my single 2008 R2 Core DC last night running on 2008 R2 Hyper-V (with the required KB2526776). I had followed the technet article on doing it and even after leaving it overnight for 8 hours the screen remained black with a mouse-cursor.

    I rebooted a few times and was able to roll back to the pre-upgrade state which was a relief. I've just repeated the whole process again (this time with the network adapter disabled - which I recall used to be a solution to a similar issue when installing 2008 R2 in a VMware environment a few years back) and the problem has occurred again in exactly the same fashion.

      • start setup from in windows logged in as domain admin
      • setup does the source file expansion then reboots
      • upgrade is performed followed by a reboot
      • spinning dots appear then the server boots to black screen with cursor

    Seems to me this should be easily reproducible. I suppose I could stand up a new vanilla 2012 DC so I can blow away my old one, kind of isn't the point though is it.

    Wednesday, September 26, 2012 9:47 AM
  • Exact same issue here as well. I've tried deleting the S3 driver, and I've also tried deleting the SynthVid driver, neither of which helped. I start the upgrade, boot into a black screen + cursor, and after a couple of reboots eventually get it to roll back.
    Wednesday, September 26, 2012 6:01 PM
  • @Tim; I've looked at the Panther logs and am not seeing anything that is obviously an error. Is there something in particular we should be looking for?
    Wednesday, September 26, 2012 6:03 PM
  • You should look at the setuperr.log and setupact.log.  I'd be interested to see your logs as well to see if there is anything in there.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Thursday, September 27, 2012 2:33 PM
    Moderator
  • Thursday, September 27, 2012 6:55 PM
  • Blast, I thought I had found a solution. I tried un-installing the Hyper-V integration components from my Core VM and the upgrade went much further. After the first reboot the installer actually completed the upgrade fully (or appeared to anyway), then did a second restart. Then I was back to the black screen + cursor :(

    Even after removing the integration components (and rebooting) I still saw the warning about the unsupported device "Microsoft Emulated S3 Device Cap"

    If anyone else wants to try removing the components you will need to run this command to find the feature name to remove (it will be the first one probably):
    DISM /Online /Get-Packages | find "Hyper-V-Gic"

    Then this one to remove it (given the Hyper-V integration components package name):
    DISM /Online /Remove-Package /PackageName:<package name here>

    For me the command was:
    DISM /Online /Remove-Package /PackageName:Microsoft-Hyper-V-Gic-Win61-Package~31bf3856ad364e35~amd64~~6.1.7601.17514

    Thursday, September 27, 2012 11:06 PM
  • Why is Kevin proposing this as the answer? @NeedsCoffee was pretty clear that this *wasn't* the answer...


    Friday, September 28, 2012 11:18 AM
  • Can you unmark it as the answer? I don't have that option...
    Friday, September 28, 2012 11:20 AM
  • Thanks for the logs, I'll look over them now and see if there is anything that stands out.

    Are all of these instances virtual machines? 


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Friday, September 28, 2012 4:34 PM
    Moderator
  • Hi Joseph, I think we're looking at a mixture of all scenarios here. The thread starter did his upgrade on a physical DC, and a bunch of us are getting the same thing on Hyper-V VMs. And another person is having the same problem from inside VMware Player.

    The commonality just seems to be that we're all upgrading Core edition Domain Controllers.

    Personally I was convinced of it being a vm issue - but now that i've re-read all the comments in here I think it's purely a DC-upgrade issue.

    Friday, September 28, 2012 4:51 PM
  • Thanks.  I don't see anything that stands out to me in the logs provided by Andy.  If possible, can some of you capture the entire \Windows\Panther directory for me and post them here?  It will help in trying to determine whats happening.  I'll try and find some time to work on a repro here internally as well.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Friday, September 28, 2012 4:54 PM
    Moderator
  • Thanks Joseph. I'll certainly contribute to that for you. I should have something for you in a few hours.
    Friday, September 28, 2012 4:57 PM
  • Hi Joseph, have managed to get you some logs you asked for. I mounted the vhd after turning off the vm and zipped from there directly. I got all files from c:\windows\panther and c:\$windows.~bt\sources\panther

    My logs are here

    Hope that helps.



    • Edited by NeedsCoffee Friday, September 28, 2012 9:45 PM
    Friday, September 28, 2012 8:48 PM
  • Awesome, thanks!

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Saturday, September 29, 2012 3:51 AM
    Moderator
  • I can report that this problem is easy to replicate in a test environment. Here's a list of what I have just done this evening to reproduce the issue in a reliable fashion:

    installed server 2008 r2 sp1 standard core in a hyper-v vm (with the intention of making a stand-alone core-dc)
    configured using sconfig:

    • assigned an ip and a public dns
    • named the server
    • enabled powershell
    • enabled all remote management
    • installed all updates (x2)

    shutdown and snapshot
    dcpromo using this unattend file:

    [DCINSTALL] 
    InstallDNS=yes
    NewDomain=forest
    NewDomainDNSName=contoso.local
    DomainNetBiosName=CONTOSO
    ReplicaOrNewDomain=domain
    ForestLevel=4
    DomainLevel=4
    RebootOnCompletion=yes 
    SafeModeAdminPassword=Password1

    restart, wait 30 minutes, then shutdown and snapshot
    boot vm
    mount 2012 iso
    d:\support\adprep\adprep /forestprep
    d:\support\adprep\adprep /domainprep
    d:\setup.exe
    (online update, std core, upgrade)

    Setup goes through the motions collecting files and settings, reboots, completes the upgrade, reboots again and then leaves you with a black screen and mouse pointer.

    Here are the panther logs from this test, which also includes the $upgrade.~os folder


    Saturday, September 29, 2012 11:54 PM
  • I think a problem in ". net Framework" but when I tried to delete this role, I received the blue screen in case of each loading.

    Не забывайте отмечать поcты как ответы, а также помечать полезные сообщения!

    Sunday, September 30, 2012 10:33 PM
  • Thanks NeedsCoffee, I'll look into these as well.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Monday, October 01, 2012 4:34 PM
    Moderator
  • As Tim Cerling suggests that was a known issue in vSphere too. Which version of VMware Player are you using?

    Wednesday, October 03, 2012 11:01 AM
  • @Rich Eveleigh - just so you know, and so this thread doesn't get confused with "vmware doesn't support it" comments, I would like to quickly highlight that the thread starter (rbmanian751) experiences the issue on a physical machine, and I have also managed to reproduce the exact same issue in a supported hyper-v environment.

    This issue is being experienced in a variety of environments and that sings out to me as being completely unrelated to the environment. If vmware player's non-support of 2012 were a problem it is likely the machine wouldn't even boot, or would at least bluescreen.


    • Edited by NeedsCoffee Wednesday, October 03, 2012 3:57 PM
    Wednesday, October 03, 2012 11:50 AM
  • Looking for a solution to this problem as well.
    Saturday, October 06, 2012 8:02 PM
  • Hello,

    Before any upgrade you must use the MPR tool, http://www.microsoftplatformready.com/us/testing.

    For your issue, you will need to recover your Windows Server 2012 using cd/iso.

    Eli.


    אירוע Unified Communication User Group יצא לדרך, המפגש יתקיים בתאריך ה-28.6 בשעה 17:30. אשמח לראותכם.

    Sunday, October 07, 2012 12:59 PM
  • See MKSB 2734222

    Title: An upgrade to Windows Server 2012 Release Candidate is not completed
    successfully on a server that is running the domain controller role or the DNS
    server role

    V 1.0 of the article is "release candidate" centric but the problem applies equally to the RTM release of Windows Server 2012.

    The Windows product team researched the fresh install vs. in-place upgrade topic and found that given the 5-7 year useful life and criticality of a server-class OS release, the overwhelming # of IT Admins strongly preferred fresh OS installs on critical server-role computers to avoid persisting a configuration or upgrade-specific problem from the previous OS version. That was my personal take when asked. The Microsoft IT group is a strong proponent of fresh installs during OS version upgrades (and beyond) and would have certainly influenced the discussion. Of course, there are always exceptions as this this is pointing out.

    Continuing to reboot the in-place upgraded server-core DC should detect the failed upgrade and trigger rollback to the previous OS version and state. Please reply back to the thread if that is not the case.

    From there you can promote new full or core replica DCs on new virtual or physical machines and retire the old W2K8 R2 DCs as required.

    Is anyone on this thread encountering an in-place upgrade failure on a GUI (i.e. non-server core) DC?

    Also, for the benefit of those reading the thread, are the server-core DCs that are failing in-place upgrade production DCs, or lab | test DCs?


    Tuesday, October 09, 2012 12:03 AM
  • Good luck!
    Looking for a solution to this problem as well.

    Tomás Mason
    Tuesday, October 16, 2012 1:02 AM
  • From blue screen of death to black screen with command prompt, yes thats an improvement. Have the same issue in my case SQL 2012 needed .NET Framework 3.5 and after install I ended up at this state


    Chandrashekar

    Monday, October 29, 2012 5:39 PM
  • Hi rbmanian751,

    1. Please update your graphics card driver and re-install windows 2012.

    2. Please un-plug any outside devices.

    3. If the issue persists, please format your system disk (Note: all the data will lost after the format) and re-install windows 2012 again.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, October 31, 2012 12:46 PM
  • We're still looking into this, for now, use the following content: http://support.microsoft.com/kb/2734222/EN-US

    And yes, I know its from RC but it still applies :)


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Wednesday, October 31, 2012 1:25 PM
    Moderator
  • So how goes the looking into this?  Seems like by now there should be a way to insure a positive outcome on an in-place upgrade from 2008r2 to 2012 where said box is the DC and/or DNS.  I have just upgraded a physical box and now have the black screen with mouse arrow blinking... I really do not want to pull all of my file shares off and rebuild a clean server...  Not too pleased...
    Sunday, November 18, 2012 12:12 AM
  • We're still working on this.  I hope to have some sort of update soon.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Sunday, November 18, 2012 2:09 AM
    Moderator
  • What is interesting that while I have a black screen and blinking mouse arrow, the server is still serving its files shares, and DNS.
    Sunday, November 18, 2012 5:03 AM
  • See MKSB 2734222

    Title: An upgrade to Windows Server 2012 Release Candidate is not completed
    successfully on a server that is running the domain controller role or the DNS
    server role

    V 1.0 of the article is "release candidate" centric but the problem applies equally to the RTM release of Windows Server 2012.

    The Windows product team researched the fresh install vs. in-place upgrade topic and found that given the 5-7 year useful life and criticality of a server-class OS release, the overwhelming # of IT Admins strongly preferred fresh OS installs on critical server-role computers to avoid persisting a configuration or upgrade-specific problem from the previous OS version. That was my personal take when asked. The Microsoft IT group is a strong proponent of fresh installs during OS version upgrades (and beyond) and would have certainly influenced the discussion. Of course, there are always exceptions as this this is pointing out.

    Continuing to reboot the in-place upgraded server-core DC should detect the failed upgrade and trigger rollback to the previous OS version and state. Please reply back to the thread if that is not the case.

    From there you can promote new full or core replica DCs on new virtual or physical machines and retire the old W2K8 R2 DCs as required.


    The Windows product team is a bunch of lazy people to have concluded the research with the above result. Anyway, I don't see that as an answer. Is there a way for the community to vote it out as answer?
    Tuesday, November 20, 2012 4:33 AM
  • The answer above is correct currently.  Core upgrades with the DC role installed are not supported.  We're looking into other options that would allow this to be a supported scenario.


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Tuesday, November 20, 2012 2:49 PM
    Moderator
  • Hi Joseph

    In your response on the 20 Nov 2012 you refer to a "Core" upgrade.

    I chose the "GUI" upgrade not the "Core" upgrade (ie full GUI interface on Server 2012).

    Does your response include the "GUI" install, in other words ALL upgrades to Windows Server 2008 R2 providing a DC or DNS role are not supported?

    If so, and I am creating a new install is not an option for me, then do I need to roll-back the upgrade and

    1. wait for a release of Windows Server 2012 that will support the upgrade or
    2. am I doomed to remain on 2008 R2 until I am able to build a fresh machine?

    Regards
    Siggy

    Wednesday, January 30, 2013 2:09 AM
  • Upgrades of Gui to Gui should work properly as far as I'm aware, these issues have mostly been seen on Core upgrades.  We're currently working on a fix for the Core problems and I hope to have an update to the thread once that's finalized.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Wednesday, January 30, 2013 3:14 AM
    Moderator
  • Thanks for your response Joseph.

    My upgrade is from GUI (Server 2008 R2 Enterprise) to GUI (Server 2012 Datacentre) and I experience the same black screen symptoms as described above.

    What I have now done is the following:

    Action 1 - remove AD DS, DNS and DHCP roles before update (failed)

    a) I restored my system from a "bare metal" backup.
    b) Removed the AD DS, DNS and DHCP roles leaving only the File Services, Hyper-V and IIS
    (This is a development machine hence running all these services)
    c) Performed a GUI to GUI upgrade BUT again was presented with a black screen.
    d) Rolled back the failed upgrade (I was presented with a roll back installation option)
    e) Found that my "bare metal" backup was no longer accessible to me (nor any other system state backups)!!! and decided to perform Action 2 below.

    Action 2 - fresh install (Succeeded)

    a) Installed new Server 2012 (and not an upgrade) - all working as expected.
    b) Now I have to build up the machine again...

    Siggy

    Sunday, February 03, 2013 11:43 PM
  • Siggy;

    Thanks for the update.  Sorry to hear that GUI to GUI failed on you, I haven't seen that occur for the specific items we're looking at for the Core installs.  I'm glad a clean install fixed the problem, but ideally, no one would have to do that to upgrade the OS.  If this happens on another machine in your environment, please keep the logs in the \Windows\Panther folder and send them to me so we can investigate.


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Monday, February 04, 2013 3:47 PM
    Moderator
  • I've been following this thread as I want to upgrade my 2008 R2 Server Core DCs to 2012. They are running on ESXi 5.1.

    Is there any update from Microsoft?

    I noted that Hans Brender mentions that WinRM was not working. Is that the case for everyone? If not, has anyone tried using PS Remote to add the Full GUI feature to the upgraded DC?

    Invoke-Command -ComputerName COMPUTER -ScriptBlock { Install-WindowsFeature Server-Gui-Mgmt-Infra Server-Gui-Shell -Restart } -credential USERNAME

    I haven't tested myself but will try to do so and provide an update.

    Thanks

    Friday, April 19, 2013 1:09 PM
  • We have a fix for this now in the form of a replacement manifest.  You can call in and request KB2769252.  There shouldn't be a charge for the call.  I'm working to get the article published externally as well so you wont need to call in the future.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Friday, April 19, 2013 2:17 PM
    Moderator
  • Isn't there a Website to open the KB article? http://support.microsoft.com/kb/2769252 does not work.

    Another KB article describes in short words that the work around for upgrading Server Core Domain Controllers is to reinstall the howl machine.
    Is there a fix for this blank screen problem available, yet?

    Saturday, April 27, 2013 2:14 PM
  • The fix is available now, you just have to call in to request it.  We're working to make the KB article public now but it will be a little bit before that's done. 

    As to why this occurs, its due to a change in one of the manifests that needs to be resolved, the fix available is the proper manifest file.


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Saturday, April 27, 2013 8:17 PM
    Moderator
  • Thank you very much for the details. I will wait a few days then.

    Isn't there a need to update the installation files then?

    By the way, removing the Intel Wired ProSet for compatibility reasons is not fun if the msi-file does only allow Windows Vista systems (Server was 2008 before) ;). A lots of devcon and MsiZapU.exe was needed to get it going. (and after I removed the network adapters I remembered that a sysprep is needed)


    Saturday, April 27, 2013 8:47 PM
  • The installation files don't need to change, its just one manifest that needs to be replaced.  If you need it now, you should call in and have someone send it to you.  I don't know how long the publishing process might take.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Saturday, April 27, 2013 11:43 PM
    Moderator
  • The article is public now: http://support.microsoft.com/kb/2843034

    Thanks for everyone's patience on this.


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    • Proposed as answer by NeedsCoffee Monday, May 06, 2013 2:36 PM
    Monday, May 06, 2013 2:04 PM
    Moderator
  • Joseph, thank you so much for your efforts in diagnosing and providing a fix for this. The detail with which you've gone to in the KB article is greatly appreciated too! I'm sure those of us still following this thread will be chuffed to bits and will be testing this out forthwith.

    Many thanks, NickC.

    Monday, May 06, 2013 9:10 PM
  • I'm having the same issues described here by everyone except...We're still running 2008 RTM GUI domain controllers and are trying to upgrade to 2012.  The upgrades seems to go ok but end up with a black screen and cursor (on every server).  Nothing else.  Several reboots rolls it back.  I don't know if the fix I read about regarding the manifests will work.  Any thoughts??

    Thanks!

    Monday, May 13, 2013 4:55 PM
  • The article is public now: http://support.microsoft.com/kb/2843034

    Thanks for everyone's patience on this.


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/


    I have opened a Support Call and received the manifest file. The migration of my physical Server Core 2008 R2 Ent. was successfully finished. For some unknown reason the DHCP Server was not installed after migration. But I think this is a special situation and can be ignored (reinstalling worked).
    Monday, May 13, 2013 5:30 PM
  • Nice to see this is working out for everyone and I'm happy to help.  I don't believe we did a test pass on this for 2008 but the manifest may work, feel free to try it and let me know.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Monday, May 13, 2013 5:35 PM
    Moderator
  • Nice to see this is working out for everyone and I'm happy to help.  I don't believe we did a test pass on this for 2008 but the manifest may work, feel free to try it and let me know.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/


    Sorry, I was wrong. I have missed the 'R2'.
    Monday, May 13, 2013 5:43 PM
  • Thanks for helping out with this, jascon.

    I've got to ask - Why on God's green earth can you or someone else at Microsoft not simply post a link to the manifest file???  I've just spent 30 minutes trying to get some recent university graduate in India to send me the file and she had no idea where to find it.  Plus, the technical team isn't available on the weekend, when BTW we tend to do upgrades.  Therefore, I can't get the file until Monday at earliest!

    Also...

    Microsoft is still promoting server core as a great solution.  If so, why in the world didn't someone in QA catch such a common use of server core (i.e. as a DC)?

    Sorry for the rant - just frustrated with Microsoft's downward spiral and the fact I can't upgrade my server this weekend.

    Saturday, May 25, 2013 3:32 PM
  • The article is public now: http://support.microsoft.com/kb/2843034

    Thanks for everyone's patience on this.


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/


    I have opened a Support Call and received the manifest file. The migration of my physical Server Core 2008 R2 Ent. was successfully finished. For some unknown reason the DHCP Server was not installed after migration. But I think this is a special situation and can be ignored (reinstalling worked).

    care to post that file??
    Saturday, May 25, 2013 3:33 PM
  • Understood, I'm sorry that the process is frustrating.  We have engineering staff on 24x7 but with the Memorial Day holiday, there might be a larger than normal amount of people out which could explain some of the issues (that's just a guess on my part, I don't have a clue on their staffing). They should be able to send you the file though.

    We require you to call in for the file because we like to track the impact of the fix.  In this case, because its a manifest, its not something we just want to post that could possibly be modified and re-posted somewhere else.  It's more about file integrity than security though.  This was something that was noted in beta (I believe it's referenced somewhere further up in this thread) but the feedback we received is that many admins preferred clean installs to upgrades for new operating system versions.  Once we noticed this thread, we wanted to get a fix out that would allow upgrades to be unblocked.


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Saturday, May 25, 2013 3:59 PM
    Moderator
  • Thanks for the info, Joseph.

    If MS wants to track, why not post it the same way as a hot fix, which requires the user to enter their info?

    Can you possibly point me to the file?  I need to get things moving.

    Saturday, May 25, 2013 4:17 PM
  • Hotfixes require special packaging and this is a single file.  The file is on an internal share that is in the internal version of the article.  A tech should be able to send that to you easily.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Saturday, May 25, 2013 7:02 PM
    Moderator
  • Hotfixes require special packaging and this is a single file.  The file is on an internal share that is in the internal version of the article.  A tech should be able to send that to you easily.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/


    Yes, you would think it would be no problem having someone get me the file immediately.  Apparently, they can't get ahold of any techs.  Perhaps, I'm not going the appropriate route.  What phone number or email address do *you* think I should be using?
    Saturday, May 25, 2013 8:00 PM
  • Wish I had it handy but I don't.  I usually tell folks to go through the site but it looks like the FWLinks to the phone number are down.  I'll see if I can find you something.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Saturday, May 25, 2013 9:35 PM
    Moderator
  • Sorry it took so long, the number is 800-936-4900

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Monday, May 27, 2013 4:15 PM
    Moderator
  • HI

    i also faced the same issue in one of the dell server where i tried to do in-place upgrade from Windows 2008 R2 with SP1 to Windows 2012. this server was Domain controller. I found the issue is related to display driver software and its utilities which is additionally installed in 2008 sever. After uninstalling this utilities  related to display  in-place upgrade worked like a charm.

    So my suggestion is if the in-place upgrade giving black screen after the reboot please roll back to 2008 R2 and uninstall all the display related utilities and drivers ( keep generic display driver). then it should work.

    Thursday, May 30, 2013 5:04 AM
  • The article is public now: http://support.microsoft.com/kb/2843034

    Thanks for everyone's patience on this.


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/


    I have opened a Support Call and received the manifest file. The migration of my physical Server Core 2008 R2 Ent. was successfully finished. For some unknown reason the DHCP Server was not installed after migration. But I think this is a special situation and can be ignored (reinstalling worked).


    care to post that file??

    Hello, I have encountered a very similar problem on my brand new HP Proliant ML350 G8 and I am wondering if this fix is appropriate for my situation. Basically we are performing an in-place upgrade of a Windows 2012 cluster node to Windows 2012 R2 RC. The process starts correctly (BTW I have performed all the preliminary steps such as shutting down all VM,s and evicting the target node from the cluster) and I see the colorful fish on the initial Windows Server 2012 RC preview boot up along with the dotted circles cycling around, then the screen goes BLACK... I do not get a mouse or anything else on the screen.  This is not a DC and there is no DHCP or DNS services running, it's just a hyper-v host and part of a two node failover cluster.  No special software or 3rd party drivers have been installed.  I have even let this sit overnight (upgrading) but without change.

    I have tried to apply the  latest server firmware and even applied an update from HP that applies directly to the Windows 2012 Preview http://h20195.www2.hp.com/V2/GetPDF.aspx%2F4AA4-7658ENW.pdf) But to no avail.  My question is, will this fix for Core and AD apply to my situation with Windows 2012 Datacenter -> Windows 2012 R2 Datacenter Preview? 

    Thanks for any direction!

    P.S.  I followed this section in the HP document:

    Download the Windows Server 2012 R2 Supplement Release for Service Pack for ProLiant at:

    hp.com/pub/softlib2/software1/supportpack-generic/p1215540406/v88252

    For details, see the Installing the Windows Server 2012 R2 Supplement for Service Pack for ProLiant section of this paper.


    hp.com/pub/softlib2/software1/supportpack-generic/p1215540406/v88252

    .

    hp.com/pub/softlib2/software1/supportpack-generic/p1215540406/v88252. For details, see the Installing the Windows Server 2012 R2 Supplement for Service Pack for ProLiant section of this paper.

     

    Cpt


    • Edited by Cpt.Scarlet Wednesday, August 07, 2013 5:40 PM
    Wednesday, August 07, 2013 3:54 PM
  • We haven't seen reports of this on 2012 R2, I'll ask around and see if anyone else has

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Wednesday, August 07, 2013 7:44 PM
    Moderator
  • Thanks for checking on this for us!

    Just to provide a little more information in the form of an update... I have now upgraded the HP Proliant ML 350 G8 firmware to the latest HP July 2013 BIOS. Power cycled the equipment and allowed it to reattempt the in-place upgrade. 

    Same results, black screen!  I think I may have to go ahead and completely reinstall and reconfigure back into the cluster unless I hear back regarding the aforementioned patch.

    Thanks for any information you can provide!

    -Cpt


    Cpt

    Thursday, August 08, 2013 8:12 PM
  • Cpt-

    I haven't forgotten about you and we're working on a couple of repros on that hardware to see if we can hit the same issue you're seeing.  Since its not a DC, the patch isn't applicable here.  Can you do me a favor and put the output of your MSINFO32 and event logs somewhere I can get to them?  If you're hesitant to post the link here, you can feel free to send it to me directly. 


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Monday, August 12, 2013 5:17 PM
    Moderator
  • Cpt-

    Another suggestion from the team was to unplug any active network connections you have on the server and retry the operation.  Either way, let me know the results, I'm happy to try to help you here.


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Monday, August 12, 2013 8:00 PM
    Moderator
  • Thanks very much,

    Coz I tried to press on and just install Windows 2012 R2 RC from scratch, but that exhibited the same symptoms.  Then I got the idea that maybe the ISO was corrupted, so I burned another from a linux machine.  I then re-attempted the inplace upgrade however there was no change.  Same symptoms.

    So basically I can't even install from scratch and I have several copies of the preview ISO.

    I have collected the MSInfo and will send it shortly...

    Just removing username and domain name strings.


    Cpt

    Monday, August 12, 2013 8:03 PM
  • OK, I tried to restart the upgrade process using the ISO with all network connections disconnected.  That was a no go, same symptom.  Seems something happens to either the video processes, or when its time to switch the processor modes, the screen blinks almost imperceptable and just goes black. 


    Cpt


    • Edited by Cpt.Scarlet Monday, August 12, 2013 9:03 PM
    Monday, August 12, 2013 9:02 PM
  • Ok, I'm not quite sure what happened, but after I received your message that the bare metal ISO install should work otherwise it points to hardware, I shutdown and combed through all the settings to ensure that I didn't miss anything. 

    I wound up blowing away the entire array and recreating it.  The only other change I made was to set the logical drive #1 to be the boot device (but it was already booting from there) but other than that, no other changes were made. 

    However I am happy to report that it is now working!!! R2 just finished installing and I am going to recreate the switch and try to in-place upgrade the sister node.  Hopefully that one will work better.  Wish I could more definitively say 'what happened'!  Sorry to consume your time, I will post the outcome of the second attempt shortly.

    Thanks for your support!


    Cpt

    Tuesday, August 13, 2013 5:56 PM
  • Glad to hear that the clean install worked properly Cpt.  Let me know the results of the other install.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Tuesday, August 13, 2013 7:48 PM
    Moderator
  • The second node upgraded in-place without problems.  Seems I was dealing with a glitch of some kind, but all went well with the second node I am happy to report.  I only had to recreate the NIC team and recreate the switch with PowerShell.  No problem.

    I did run into a problem that might have been my fault.  I will probably post it on another forum unless you can direct me.  Here is a brief description:

    To get the initial node up and running so as to migrate all the roles, I created an AD Detached Cluster and joined the upgraded host to that cluster.  This allowed me to copy over all the roles from the original cluster and I used the -nostorage option, which worked well.  Then I had to destroy the original cluster and upgrade the remaining host to R2 to match the first one (also went well).  Problem is when all was done it seems that one volume (Volume1) on my shared storage (HP P2000) is unable to be added to the Cluster Shared Volumes.  "Volume2" and the Quorum disk did add just fine, but the System Volume (where all my C: drive VHD's Lived) "Volume1" is visible, I can put it offline or online but when I try to Add it with Failover Cluster Manager, I get the message that "No suitable disks for Cluster Disks could be found."  I have tried everything, it seems like something got corrupted on it. I have exported the VM's to the second volume so I have a copy, but it really would be nice to know what happened as I am trying to nail down a procedure for future rolling upgrades.  Any advice would be appreciated!


    Cpt

    Monday, August 19, 2013 9:31 PM
  • Glad that worked out for you.  Unfortunately, I'm the last guy you want around your cluster so I don't have any suggestions that would be useful for you there.  You might want to start a new thread on that side of things.

    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Monday, August 19, 2013 9:39 PM
    Moderator
  • Hello, I have an update...

    As I performed additional updates and OS reinstalls I came to realize that the problem was really not resolved.  It was intermittent and returned upon my next installation attempt.  It also was seen with the MSDN version of Windows 2012 R2.  But I am happy to report that one of my team members was able to determine the cause.

    It seems that for some reason, Windows 2012 (Rx) gets confused during the OS install.  This happens when you have a P2000 shared storage array in the mix.  So in essence, even though we have set the boot drive to the internal RAID1 array within the HP Proliant ML350 G8, during the install it seems to go to a black screen if the P2000 is physically attached.  Once we detach the P2000 SAS device, the installation proceeds normally.  This does not happen with Windows 2008 R2 installs, but both with Windows 2012 and Windows 2012 R2 it is observed. 

    I have spent several days working on this problem, replaced a motherboard and lost hair!  yet now we have stumbled upon the real reason.  Just passing on the info!


    Cpt

    Thursday, September 26, 2013 12:59 PM
  • Hi Joseph,

    Do you know if we need to request the manifest file if we are trying an in-place upgrade from a Windows 2008 R2 DC to Windows 2012 R2?

    Thanks!

    Tuesday, October 22, 2013 1:16 PM
  • No, you shouldn't need it as the fix was rolled into 2012 R2.  If you do have a problem though, please let me know.


    --Joseph [MSFT] http://blogs.technet.com/b/joscon/

    Tuesday, October 22, 2013 1:30 PM
    Moderator