News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Reports: Server 2008 R2 systems boot to recovery mode after January patches applied

    Home Forums AskWoody blog Reports: Server 2008 R2 systems boot to recovery mode after January patches applied

    This topic contains 33 replies, has 15 voices, and was last updated by  anonymous 2 weeks ago.

    • Author
      Posts
    • #2087693 Reply

      woody
      Da Boss

      Not clear which patches are causing the problem, but I’m seeing multiple reports of a boot to recovery mode on Server 2008 R2 systems. Can anybody out
      [See the full post at: Reports: Server 2008 R2 systems boot to recovery mode after January patches applied]

    • #2087702 Reply

      matjazp72
      AskWoody Plus

      I had the same problem. The only way to recover server is to restore it from backup. Luckily for me it was an old SQL server with archaic databases – not in real production.

      I then tried to make a clean install of Windows 2008 R2, applied all patches, including the latest one and I couldn’t reproduce the problem. Maybe some weird combination with existing patches prior to 2020-01 or 2019-12?

      The simptom was – all patches have been successfully installed, reboot and then bang, straight into recovery mode. No way out from there…

      Final result – new clean install, rebuild SQL server, copied all databases from old server.

      • This reply was modified 1 month ago by  matjazp72.
      2 users thanked author for this post.
    • #2087726 Reply

      warrenrumak
      AskWoody Plus

      Well that’s certainly one way of fixing the RD Gateway security vulnerability…….

      1 user thanked author for this post.
    • #2087727 Reply

      jabeattyauditor
      AskWoody Lounger

      We’re not seeing that issue here with 2008 R2 VMs on top of VMware – any idea if the affected systems are physical or virtual?

    • #2087729 Reply

      kbecker1213
      AskWoody Plus

      seeing this on Vm on ESX hosts

      • #2087749 Reply

        jabeattyauditor
        AskWoody Lounger

        Thanks. We’re running on ESXi 6.5.

        Any common roles/features on the VMs that are failing? SQL? Terminal services?

        I’m thinking snapshots prior to patch installation as a safety net…

    • #2087740 Reply

      nazzy
      AskWoody Lounger

      A *potential* fix for physical servers (to avoid restoring from backup):

      https://community.spiceworks.com/how_to/164887-after-windows-server-2008-r2-update-the-server-won-t-boot-how-did-i-fixed-it

       

       

       

      • #2087748 Reply

        jabeattyauditor
        AskWoody Lounger

        That looks like a way around a patch failure from September, 2019.

        • #2087825 Reply

          nazzy
          AskWoody Lounger

          Which the method could possibly be useful for future patch failures. As a way to get around the “stuck in recovery mode” issue.

           

          • This reply was modified 1 month ago by  nazzy.
          1 user thanked author for this post.
    • #2087865 Reply

      anonymous

      Just got done with around 60 across 25+ separate clients. No issues with them so far.

      2 users thanked author for this post.
    • #2088033 Reply

      tbsky
      AskWoody Lounger

      Hi:

      is win7 January security only patch clean(ie: without telemetry or EOS notice)?  I already skip July,Sepetember,December. I hope this one can give win7 a happy ending.

      • #2088391 Reply

        anonymous

        @tbsky asked:

        is win7 January security only patch clean(ie: without telemetry or EOS notice)?

        No. KB4534314 (January 14, 2020 Security-only update) does not contain telemetry, but it contains a newer version of ‘EOSNotify.exe’ (the program that is responsible for displaying full-screen ‘End of Support’ notifications). It is mentioned in update description. You can also find some further details in file information (a *.csv file. Keyword: ‘EOSNotify’).

        You can prevent those nagware from displaying notifications by simply disabling it in Task Scheduler. There are instructions, for example here on Askwoody.com.

        1 user thanked author for this post.
    • #2088034 Reply

      Freeco
      AskWoody Lounger

      We’ve completed our non-prod patching yesterday morning, with 30+ Win2008R2’s.
      Most will be VMs on VMware ESXi. We don’t have that much physical non-prod.

      No problems whatsoever so far with this month’s patches…

      1 user thanked author for this post.
    • #2088043 Reply

      Guy
      AskWoody Lounger

      It seems to be a mixture of December and January patches that causes it to blue screen, I’ve had reports of it on Windows 7 machines as well.

      1 user thanked author for this post.
    • #2088050 Reply

      jabeattyauditor
      AskWoody Lounger

      We just finished updates here; no issues with the remaining 2008/2008R2 VMs (other than the fact that there ARE remaining 2008/2008R2 VMs).

    • #2088110 Reply

      luanne1
      AskWoody Plus

      Had downloaded Windows updates for my 64 bit Windows 7 professional desktop. Last night when I turned the computer off it forced more updates and I had already been forced to update the night before. This morning the screen shows ” Configuring Windows update 100%complete Do not turn off your computer”. What should I do? I’ve already paid for the service from Harbor to receive extended updates. This is a small business computer.

      Thank You in advance for any help you can give or suggestions.

      <!–more–>

      • #2088113 Reply

        PKCano
        Da Boss

        Look in the Update History and give us a list of the KB numbers for the patches that have been installed in the last three days (the ones you say were forced).

        • #2088115 Reply

          luanne1
          AskWoody Plus

          I’m still stuck with the screen”Configuring Windows updates 100% complete do not turn off your computer. ” I can’t access those KB numbers until the system completes this step but it’s been like this for one hour.

          • #2088123 Reply

            jabeattyauditor
            AskWoody Lounger

            We had one 2008 R2 server (same basic system as Windows 7) take over 45 minutes at this stage. Let it sit a while longer – it may just be taking its sweet time to complete the update.

          • #2088155 Reply

            Susan Bradley
            AskWoody MVP

            Give it a couple of hours.  If it still doesn’t go, do a hard reboot.

            Susan Bradley Patch Lady

            • #2088181 Reply

              luanne1

              Thank You all for your helpful responses! The system finally came up ok after taking over and hour and then showing a clean up message. Thank You again!!!

    • #2088324 Reply

      anonymous

      Had 1 windows 7 64 bit pro go into startup repair after todays’ updates.

      Bypassed it by hitting F8 as the PC booted and chose Safe mode with networking. Doamin login screen loaded immediately. Then I succeeded in logging in and did a reboot into normal safe mode.

      1 user thanked author for this post.
    • #2106071 Reply

      anonymous

      We did experiance 2 cases where Windows 2008 R2 servers would boot to recovery mode after the patches were applied. In both cases, they were FAX servers running in a vmware environment. Any idea which patch(es) may be causing this?

    • #2109979 Reply

      wmelonman
      AskWoody Plus

      To all of you how experienced the fault with a virtual machine and can rollback to before January patch install: Have you tried to do a SFC /scannow and then install again? I think maybe it is some system file corruption that causes the patch to fail – and not some other patch or software by merely coexisting.

      I have one SBS 2011 at a customer’s and did not dare to install yet. But SFC /verifyonly did show some issues which I will definitly try to fix before jumping…

    • #2110064 Reply

      anonymous

      just got done with MS support. I have had a few 2008r2  vm servers do this. He rolled back patches for them to fix. Said it is caused by us missing a req patches. The error was winload.exe Windows cannot verify the digital signature

    • #2111135 Reply

      anonymous

      Had the issue of booting to recovery mode on a 2008R2 machine last Friday, and a second machine today.

      The majority of our estate is patched on an automatic schedule every month, and none of these have displayed any issues.

      The 2 affected machines aren’t patched automatically monthly, but manually every 3 months.

      This makes me think that there is a clash between the January patches and the patches from December or November, so backing up Guy’s comment from the 21st

      • #2111510 Reply

        anonymous

        I’ve managed to identify the cause of this.

        The latest kb4474419 (September 10th 2019) must be installed and the server rebooted before installing January’s patches.

        The patch specifically deals with sha-2 signing of bootloader files and is listed as a prerequisite for January’s fixes.

        Installing it first in a batch including January’s still causes the issue, so it must be installed individually.

        Hope this helps someone avoid this issue

        1 user thanked author for this post.
    • #2111919 Reply

      anonymous

      Had this problem on two servers. Click command line option in recovery:

      dism.exe /image:C:\ /cleanup-image / revertpendingactions
      Replace c: with whatever your windows install is on according to diskpart

      saved mine.

      • #2135430 Reply

        anonymous

        Thank you for saving my live!

    • #2135027 Reply

      anonymous

      Serveral 2008r2 vm’s on esxi had the recovery mode after patch installation and rebooting.

      I had to load up the pvscsi drivers from the vmware tools iso into to the recovery mode. Then i was able to access the windows installtion on the vm disks and do a simple startup repair. VM booted again and finished installing the patches. Startup repair reported that the root cause was a corrupt boot manager…

    • #2135610 Reply

      anonymous

      Same boot issue here of Win2k8 R2 and i was able to reproduce the issue on Hyper-V VM by installing only KB4534314. A repair process which worked is to boot from Win2k8 R2 installation media and running StartRep.exe

    • #2135850 Reply

      BATcher
      AskWoody_MVP

      Will Susan Bradley be able to tell us at what point it will be safe to install all the WS2008R2 patches which have stacked up, waiting?

      Thanks!

      BATcher
    • #2135879 Reply

      Susan Bradley
      AskWoody MVP

      What a/v do you have running and when did you apply the SSU?  Webroot is one trigger.  As long as you don’t have that a/v I’m personally not seeing any issues here.

      Susan Bradley Patch Lady

    • #2137157 Reply

      anonymous

      Hi friends

      This command  solve the problem

      dism.exe /image:C:\ /cleanup-image /revertpendingactions

      Thanks!!!!!

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: Reports: Server 2008 R2 systems boot to recovery mode after January patches applied

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.