When Windows Update Fails, This Is How You Fix It

Discussion in 'Windows - General discussion' started by ireland, Aug 18, 2014.

Thread Status:
Not open for further replies.
  1. ireland

    ireland Active member

    Joined:
    Nov 28, 2002
    Messages:
    3,451
    Likes Received:
    15
    Trophy Points:
    68
    When Windows Update Fails, This Is How You Fix It

    YOU MUST GO HERE

    http://www.makeuseof.com/tag/windows-update-fails-fix/


    By Tina Sieber on 17th August, 2014 | Windows | 20 Comments
    The recent Windows 8.1 August Update blindsided many users with issues. Some experienced BSODs or black screens, while others found themselves stuck in an infinite reboot loop.
    If you’ve been negatively affected by a Windows Update, here’s a quick list of troubleshooting steps that will help you restore Windows to a functional state.
    Windows Crashes With A Blue Screen Of Death
    A BSOD typically hints to a hardware problem or faulty drivers, but can also be caused by third-party software. We have previously shown you how to troubleshoot a BSOD in Windows 8.

    The August Update BSOD
    After applying the Windows August Update, many Windows 7 and 8 users experienced BSOD crashes with a 0×50 Stop error message. According to Microsoft Community member xformer, KB2982791 is the culprit. This update causes Win32k.sys to crash when the font cache is not correctly maintained.
    According to Microsoft, August Update BSOD crashes are caused by the following updates, which subsequently have been disabled:
    KB2982791, a security update for kernel-mode drivers.
    KB2970228, the update introducing support for the Russion Ruble currency symbol.
    KB2975719, the August Update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2.
    KB2975331, the August Update rollup for Windows RT, Windows 8, and Windows Server 2012.
    How To Fix It
    A workaround proposed by Microsoft Community member rvuerinckx recommends to boot from a recovery disk and remove the following file:
    C:\Windows\System32\FNTCACHE.DAT
    In a response, community member Laurens (NLD) posted a step-by-step explanation on how to remove the file via the command prompt. Briefly, insert your Windows 7 or 8 installation or recovery disk and boot from the disk. In Windows 7, go to restore options, choose repair tools, and select command prompt. In Windows 8, go to troubleshoot and advanced options, and select command prompt from here.
    Type the following command:
    del %windir%\system32\fntcache.dat
    When the file is gone, you should be able to boot into Windows. Microsoft Support says this is only a temporary fix and they explain how to remove a registry key for a permanent solution. Please see the mitigations for known issue 3 for details. After removing the offending updates (see below), you can restore the registry file, the support page explains how this is done.
    I Can’t Boot Into Windows Anymore
    When a Windows Update is so bad that you can no longer boot the system, try booting into Safe Mode to remove it.
    To boot into Safe Mode in Windows 7, hit the F8 key while the computer is booting up and before the Windows logo can be seen. You know you hit the right moment, when you see the advanced boot options screen.

    When Windows 8 or 8.1 crashes repetitively, it should at some point boot into Automatic Repair. Select Advanced options to access Safe Mode.

    You can manually boot into Safe Mode by pressing the SHIFT key while clicking Restart and subsequently click Restart under Sartup Settings, found under Troubleshoot and Advanced options.
    Once you are in Safe Mode, you can navigate to Windows Update via the Control Panel and remove the most recent updates, see instructions below.
    Uninstall Windows Updates In Windows
    Uninstalling updates from within Windows is very simple. Briefly, navigate to Installed Updates (View installed updates under Windows Update or Programs and Features) in the Control Panel, select the problematic update, and click the Uninstall button or right-click it and select Uninstall.

    Uninstall Windows Update Via Command Prompt
    When an issue with a Windows Update prevents your computer from booting, not even into Safe Mode, things get tricky. You will need a Windows boot or recovery disk to launch into repair tools (Windows 7) or advanced options (Windows 8), from where you can access the command prompt.
    Assuming your system drive is C, type the following command to find the package names of the offending updates:
    dism /image:C:\ /get-packages
    Search the results for the update that needs to be removed and note down the package name. Then use the following command:
    dism /image:C:\ /remove-package/PackageName:package_for_insert_exact_package_name_here
    Example: dism /image:C:\ /remove-package/PackageName:package_for_KB2976897~31bf3856ad364e35~amd64~~6.1.1.0
    After removing the update, try to reboot and fingers crossed all will be well.
    Hide Windows Updates
    Sometimes, updates are known to cause problems before you apply them. Or maybe you don’t accidentally want to re-install an update that made your computer crash. Navigate to Windows Update in the Control panel, right-click the troublesome update, and select Hide update.

    To restore a hidden update, click the respective link in the Windows Update sidebar.
    For a full walkthrough with screenshots of the process, see Windows SevenForums.
    None Of The Above Works
    The issues you’re experiencing may go deeper than a Windows Update bug. Please consult our guide on troubleshooting Windows 8 crashes. Windows 8 boot issues can be easy to resolve, but an infinite reboot loop may require a system recovery. If you’re able to boot into Windows 8 Advanced Startup Options, you can try to repair, restore, refresh, or reset your PC.

    Has Windows Update Caused You Pain?
    Have you ever had to resolve issues caused by a Windows Update in the past? How did you do it?
    Let’s hear your experiences in the comments!


    YOU MUST GO HERE
    http://www.makeuseof.com/tag/windows-update-fails-fix/
     
Thread Status:
Not open for further replies.

Share This Page