How Do I Block 2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892)?

Anonymous
2018-01-05T07:42:12+00:00

KB4056892 is Awaiting restart

Unfortunately, when I did a restart it bricked my system. I had a large windows logo on the screen and it just sat there.  I rebooted and was able to trigger a repair.  The repair said it was backing out the last update as it would not be completely installed.

With KB4056892 is Awaiting restart I did another restart and had the same problem.  At the end I was staring at a Windows logo that just sat there.

Again I triggered a repair and the system is now usable.  However, Windows Update still says: KB4056892 is Awaiting restart

How do I block it so it doesn't get installed if I have to reboot the machine?

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

210 answers

Sort by: Most helpful
  1. Monkey57 3,535 Reputation points
    2018-01-12T18:29:05+00:00

    >Now the question is: Is it safe to go back in the water and unpause Windows Update?

    No.

    I unpaused updates and did some other stuff.  Then I came back to the machine and rebooted to install some other software.  Got the big Windows blue logo and hung.  Rebooted and triggered a repair which said it was backing out an update that didn't completely install.  Finally, got the login screen.  Logged in as an administrator and paused Windows Updates.

    Will let the pause expire in 35 days before trying again.

    Please see:

    https://answers.microsoft.com/en-us/windows/forum/windows_10-update/after-installation-of-kb4056892-boot-failure-after/6c015632-2a45-4725-a882-f231f8c88f36?auth=1

    On an Auto restoring AMD X2 L310 processored device:

    Even though KB4056892 is showing hidden by the Hide/Show troubleshooter ... I went ahead & used DISM to remove the Staged Package from this 1709 x64 system.

    from an elevated command prompt ran:

    dism /get-packages /Online

    pertinent results at the end:

    Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6

    State : Installed

    Release Type : Security Update

    Install Time : 1/12/2018 12:01 PM 

    Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

    State : Staged

    Release Type : Security Update

    Install Time : 1/12/2018 3:12 AM

    16299.192.1.9 I am afraid of so I removed it.

    back in the elevated command prompt i ran (copy all the bolded text as one line, command may be wrapped when displayed on MC;  if your results from the previous DISM command are the same):

    dism /Online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

    pertinent results at the end:

    Processing 1 of 1 - Removing package Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

    [==========================100.0%==========================]

    The operation completed successfully.

    Windows Update Completed successfully, it downloaded some Defender updates, and left no pending updates.  Even after rebooting device multiple times over many hours.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-12T18:13:04+00:00

    Your problem could also be from another program conflict altogether.

    A third party antimalware or antivirus (or both) program is a great source for problems when you are trying to download and install any updates.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-01-12T18:09:40+00:00

    Intel is working fine as is ARM.

    You should check with Intel or your Manufacturer if you haven't.

    (Or ARM, of course)

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-01-12T16:57:48+00:00

    I had no idea that my computer problems were probably the result of this update.   5 days ago I rebooted my PC, because it had been left sleeping all weekend, but it failed due to Inaccessible Boot Device.  I had no restore points.  Nothing worked, I tried repairing, scandisk, chkdsk, rebuilding master boot record, etc.   Literally the entire day spent trying various things.

    I wound up doing a Windows 10 Reset.   Since then, I had an issue where my PC would take 1 to 2 hours to shutdown or restart.  I eventually gave up and on each shutdown, after 20 seconds or so, I would just hold the power button.   Upon reboot, no problems.  At least, I didn't think so.

    I started getting a warning that disk space was low.  Windows is installed on a 100G SSD drive (C drive).   All apps and data go to my D drive, so how could this be??  I discovered a file in windows/logs/cbs that was 70G.  It can't be deleted because it is in use.  However, when your PC starts, this file is copied to a file with a different name, and a new cbs.log file is started, so it can then be deleted.  But eventually (for me, after about 6 hours), that new CBS file gets to be over 60G.  I had to keep shutting down and restarting my PC every few hours, so I could delete this log.  

    Going into Windows Update setting, the KB4056892 update was always at 99%.  Sometimes it would show a failure due to error code 0x800705b4.  

    I found this thread and downloaded the Windows show/hide update thing.  It found KB4056892, and allowed me to hide it.  I rebooted (forced shutdown, of course), and this update no longer appears.  Windows update says my computer is up to date.  I have checked the cbs.log file and it has not budged past the 172K size.  

    So all appears to be good now.  

    BTW...I am not running AMD, I have Intel i5-6402.  Winver says my windows version is 1709, Build 16299.15

    And the one good thing to come out of this is that I have enabled Restore points.  

    I am not tech savvy like I was 20 years ago.  All I can do is research, review options and opinions, and try to make a good decision.  It seems like things are okay now, but I know the story is far from over.

    Can anybody offer any clue what the next step should be?  Should I just keep this update hidden?  Are we waiting on a good update from Microsoft?   Will I need to use that show/hide update thing again if a new patch is released? 

    Honestly, after what I went through, I fear Microsoft almost as much as I fear hackers.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-01-12T15:35:46+00:00

    Sounds good, but what about Microsofts fix for Intel's chips. I disabled auto update, but for how long ?

    Was this answer helpful?

    0 comments No comments