reason for failed in-plce upgrade 2008 r2 to 2012 r2

bill emery 1 Reputation point
2021-04-18T16:22:45.703+00:00

getting the error message
Windows Server 2008 R2 Standard cannot be upgraded to Windows Server 2012 R2 Standard
when attempting an in-place upgrade with no reason given.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,731 questions
0 comments No comments
{count} votes

7 answers

Sort by: Most helpful
  1. Anonymous
    2021-04-18T17:39:59.127+00:00

    One reason could be evaluation media which is not possible to do, licensed media must be used.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

  2. bill emery 1 Reputation point
    2021-04-18T17:55:33.247+00:00

    it does not involve eavaluation media. just want to know why and pls do not post gueses

    0 comments No comments

  3. Anonymous
    2021-04-18T18:02:08.517+00:00

    Too funny. You can review the logs here.
    https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/windows-setup-log-file-locations

    --please don't forget to Accept as answer if the reply is helpful--


  4. Anonymous
    2021-04-18T20:26:36.07+00:00

    There could be any number of reasons. First I'd check the 2008 is patched fully and that health is 100%
    I'd verify system and servicing health by running;
    sfc /scannow

    also system update readiness tool

    https://learn.microsoft.com/en-US/troubleshoot/windows-server/deployment/fix-windows-update-errors#resolution-for-windows-7-service-pack-1-sp1-and-windows-server-2008-r2-sp1

    Then check for errors in;
    %SYSTEMROOT%\Logs\CBS\CheckSUR.log

    • check here and with manufacturer about support for Server 2012 R2
      https://www.windowsservercatalog.com/
    • check the server manufacturer's site for the latest firmware, ROM bios, chipset and driver support pack
    • uninstall conflicting applications, roles or features
    • but the safer / cleaner method is to stand up a new one, patch fully, migrate the roles over to new instance.

    --please don't forget to Accept as answer if the reply is helpful--


  5. Anonymous
    2021-04-18T20:48:19.56+00:00

    unless the conflicting application roles or features are known

    and they're still unknown to us. Other options were mentioned. I'd suggest contacting the application developer or starting a case here with product support.
    https://support.serviceshub.microsoft.com/supportforbusiness

    --please don't forget to Accept as answer if the reply is helpful--


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.