Unable to install Windows Server Backup


Recommended Posts

Hi guys and girls,

 

I have inherited a server 2012r2 host with a 2012r2 DC. I am trying to install the Windows Server Backup role using the add roles and features wizard, but keep getting errors (see attached capture).

 

When looking through the server manager dashboard I found the following 3 errors which I think are linked.

 

Faulting application name: tasklist.exe, version: 6.3.9600.17415, time stamp: 0x545042cc
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17736, time stamp: 0x550f42c2
Exception code: 0xc0000142
Fault offset: 0x0009d4f2
Faulting process id: 0x2014
Faulting application start time: 0x01d17626609f5ad4
Faulting application path: C:\Windows\SysWOW64\tasklist.exe
Faulting module path: KERNELBASE.dll
Report Id: 9e4f9edc-e219-11e5-80d0-00155d078e00
Faulting package full name: 
Faulting package-relative application ID: 

Faulting application name: tasklist.exe, version: 6.3.9600.17415, time stamp: 0x545042cc
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17736, time stamp: 0x550f42c2
Exception code: 0xc0000142
Fault offset: 0x0009d4f2
Faulting process id: 0x255c
Faulting application start time: 0x01d1762660b9e79e
Faulting application path: C:\Windows\SysWOW64\tasklist.exe
Faulting module path: KERNELBASE.dll
Report Id: 9e68cc24-e219-11e5-80d0-00155d078e00
Faulting package full name: 
Faulting package-relative application ID: 

Faulting application name: tasklist.exe, version: 6.3.9600.17415, time stamp: 0x545042cc
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17736, time stamp: 0x550f42c2
Exception code: 0xc0000142
Fault offset: 0x0009d4f2
Faulting process id: 0x3498
Faulting application start time: 0x01d1762660dab5fd
Faulting application path: C:\Windows\SysWOW64\tasklist.exe
Faulting module path: KERNELBASE.dll
Report Id: 9e89c183-e219-11e5-80d0-00155d078e00
Faulting package full name: 
Faulting package-relative application ID: 

I have also tried installing Windows Server Backup using powershell but receive the following error:

 

Add-WindowsFeature Windows-Server-Backup

Add-WindowsFeature : Server execution failed
At line:1 char:1
+ Add-WindowsFeature Windows-Server-Backup
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : DeviceError: (Microsoft.Manag...rDetailsHandle):CimException) [Install-WindowsFeature],
   Exception
    + FullyQualifiedErrorId : UnSupportedTargetDevice,Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureComman
   d

I'm not really sure where to start looking to solve this, would anyone be able to help??

 

Many thanks

 

Mike

Capture2.PNG

  • 2 weeks later...

Apologies for the late reply. Seems the previous company in charge of this server didn't believe in updating servers. After installing a butt load of updates I was finally able to install windows server backup. Thanks for your help :)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Just give a great simple monitor. No AI nonsense. What's next? AI mouse that knows where you want to move?
    • Certificates for one of Windows 11's hardware requirements expire soon, here is what to know by Taras Buria Secure Boot is a known term for Windows 11 users. It is one of Windows 11's hardware requirements, and without it, the operating system cannot be installed, at least officially. Secure Boot was introduced in 2012 with the release of Windows 8, and its certificates, first issued in 2011, are set to expire soon. Now, Microsoft has posted a blog post about the importance of this event and why organizations and users must ensure their Secure Boot certificates are up to date. In a nutshell, Secure Boot is a special mechanism that ensures that your PC is using verified firmware and a trusted bootloader. Certificates released in 2011 will expire in June 2026, and if left outdated, will disrupt the integrity of the device startup process. Without new certificates, Windows Boot Manager and Secure Boot components can't receive security fixes, leaving affected devices exposed to bootkit malware (such as BlackLotus), which is very hard to detect with standard antivirus software. Other results of having expired Secure Boot certificates include the inability to trust software signed with new certificates. PCs that could be affected by expired certificates include physical and virtual machines (VMs) with supported versions of Windows 10, Windows 11, Windows Server 2025, Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012, Windows Server 2012 R2. Copilot+ PCs released in 2025 are not affected. To avoid these potentially disastrous consequences, Microsoft urges organizations and users to update their entire PC fleet to newer certificates, which were released in 2023: Expiration Date Expiration Certificate Updated Certificate What it does Storing Location June 2026 Microsoft Corporation KEK CA 2011 Microsoft Corporation KEK 2K CA 2023 Signs updates to DB and DBX Key Enrollment Key (KEK) Microsoft Corporation UEFI CA 2011 (or third-party UEFI CA)* Microsoft Corporation UEFI CA 2023 Microsoft Option ROM UEFI CA 2023 Signs third-party OS and hardware driver components Signs third-party option ROMs Allowed Signature database (DB) October 2026 Microsoft Windows Production PCA 2011 Windows UEFI CA 2023 Signs the Windows bootloader and boot components So, what do you need to do? Microsoft says that the easiest solution is to let Microsoft manage your Windows updates. In the upcoming months, Microsoft will release new certificates as part of monthly cumulative updates, so it will take care of everything for you. The company also recommends enrolling Windows 10 devices in the Extended Security Updates program, which is free for regular consumers and paid for enterprises. Microsoft will also provide the necessary certificates for Linux systems that dual-boot Windows. Of course, not every Windows PC can receive such updates. For example, so-called "air-gapped" devices, which are physically isolated from the internet and local networks, cannot receive updates like your home PC does. For such devices, Microsoft offers limited support, which is detailed in the blog post. You can also track Windows Secure Boot certificate updates on a newly published support document. You can check if your system has Secure Boot enabled by pressing Win + R, typing msinfo32, and checking "Secure Boot State."
  • Recent Achievements

    • One Month Later
      jfam earned a badge
      One Month Later
    • First Post
      TheRingmaster earned a badge
      First Post
    • Conversation Starter
      Kavin25 earned a badge
      Conversation Starter
    • One Month Later
      Leonard grant earned a badge
      One Month Later
    • Week One Done
      pcdoctorsnet earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      547
    2. 2
      ATLien_0
      201
    3. 3
      +FloatingFatMan
      176
    4. 4
      Michael Scrip
      147
    5. 5
      snowy owl
      114
  • Tell a friend

    Love Neowin? Tell a friend!