Posted  by  admin

Server 2008 R2 Microsoft Update

Learning has never been so easy!

Hey All,

I came across an issue the other day when trying to install windows updates on Server 2008R2 (yes I know it's old will be decomm'd)

There were about 5 updates to install so I assumed it wouldn't take too long. So after downloading/installing the updates I rebooted the server.

Then I saw the 'preparing to configure windows. Do not turn off....' screen.
I waited over half an hour and knew something was wrong as it was still showing the same screen with no progress.

Windows Server 2008 R2. To start the download, click the Download button and then do one of the following, or select another language from Change Language and then click Change. Click Run to start the installation immediately. Click Save to copy the download to your computer for installation at a later time. Windows Server 2008 R2 windows update stuck. Ask Question Asked 4 months ago. Viewed 326 times 0. I have a 2008 R2 Standard server (on VMware) that is stuck.

Method 2: Microsoft Update Catalog. To get the standalone package for this update, go to the Microsoft Update Catalog website. Update detail information. Windows 7 and Windows Server 2008 R2 file information. The MANIFEST files (.manifest) and MUM files (.mum) that are installed are not listed. For all supported ia64-based versions.

I did not want to cold reboot the server obviously. So after some searching on the net I found out the windows module installer service was stuck(stopping)

3 Steps total

Step 1: Windows Server is stuck on 'Preparing to configure windows. Do not turn off..' screen

2008

You are stuck on this screen for longer than usual after rebooting the server to finish installing windows updates.

Step 2: Check the windows module installer service

If the windows module installer service is stuck the service will show 'stopping'. When you check the properties of the service the path to the exe shows C:windowsservicingtrustedinstaller.exe.

*Note you can check the service status of the server remotely from your local machine via computer management or command prompt.

Step 3: Kill trustedinstaller.exe

Kill the trustedinstaller executable by running this command in command prompt (using sysinternals from your local machine)

taskkill /S hostname /IM trustedinstaller.exe

*Taskkill.exe also works from command prompt(as admin). No need for sysinternals. Glad this has helped a few people so far!

After killing trustedinstaller.exe, the server finally shut down. I booted it up and everything was back to normal.

This may also work on other versions of Windows but I haven't tested it out.

Published: Feb 03, 2017 ยท Last Updated: Mar 23, 2019

References

  • Prashant Deshpande

4 Comments

  • Pimiento
    loganburt Aug 17, 2018 at 10:39am

    A thousand times, THANK YOU for posting this! This was spot on what was wrong with my update installation, and your article allowed me to recover from this hang-up.

    One small comment on this, though, for anyone else who needs this. The taskkill.exe command appears to be a a Windows system command rather than a SysInternals command.

    Thank you again for posting this.

  • Pimiento
    sporter51 Sep 16, 2018 at 04:55pm

    While this works well and will allow you to log back into the server, you will still need to remove the offending update(s), or you'll be in the same position with your next reboot.

    Still, this is just another tool to drop into your bag. Mahalo!

  • Pimiento
    William6895 Sep 26, 2018 at 08:57pm

    How do you check the services if you can not log in locally or connect remotely?

  • Pimiento
    JimboAccy Mar 18, 2019 at 01:42pm

    Worked a treat this for me - thank you very much indeed. It was exactly as you described (waiting for nearly an hour on the Preparing updates screen on SBS 2011) and the trustedinstaller kill worked perfectly - I just used the same command in an elevated CMD prompt on my PC.

    Many thanks indeed

    Jim

-->

Extended support for Windows Server 2008 and Windows Server 2008 R2 is ending on January 14, 2020. There are two modernization paths available: On-premises upgrade, or migration by rehosting in Azure. If you rehost in Azure, you can migrate your existing Server images free of charge.

On-premises upgrade

Server 2008 R2 Microsoft Update

If you need to keep your servers on-premises, and you are running Windows Server 2008 or Windows Server 2008 R2, you will need to upgrade to Windows Server 2012/2012 R2 before you can upgrade to Windows Server 2016. As you upgrade, you still have the option to migrate to Azure by rehosting.

See Upgrading from Windows Server 2008 R2 or Windows Server 2008, for more information about your on-premises upgrade options.

Server 2008 R2 Update Download

If you are running Windows Server 2003, you will need to upgrade to Windows Server 2008. See upgrade paths for Windows Server 2008 for more information about your on-premises upgrade options.

Migrate to Azure

You can migrate your on-premises Windows Server 2008 and Windows Server 2008 R2 servers to Azure, where you can continue to run them on virtual machines. In Azure you'll stay compliant, become more secure, and add cloud innovation to your work. The benefits of migrating to Azure include:

  • Security updates in Azure.
  • Get three more years of Windows Server 2008 R2 or 2008 critical and important security updates, included at no additional charge.
  • No-charge upgrades in Azure.
  • Adopt more cloud services as you are ready.
  • By migrating SQL Server to Azure Managed Instances or VMs, you get three more years of Windows Server 2008 R2 or 2008 critical security updates, included at no additional charge.
  • Leverage existing SQL Server and Windows Server licenses for cloud savings unique to Azure.

Server 2008 R2 Enable Microsoft Update

To get started migrating, see Upload a Windows Server 2008/2008 R2 specialized image to Azure.

To help you understand how to analyze existing IT resources, assess what you have, and identify the benefits of moving specific services and applications to the cloud or keeping workloads on-premises and upgrading to the latest version of Windows Server, see Migration Guide for Windows Server.

Upgrade SQL Server 2008/2008 R2 in parallel with your Windows Servers

Windows Server 2008 Support Lifecycle

If you are running SQL Server 2008/2008 R2, you can upgrade to SQL Server 2016 or 2017.

Update

Windows Update Troubleshooter 2008 R2

Additional resources