After installation of KB4056892 boot failure, after roll-back error 0x800f0845

Anonymous
2018-01-04T22:13:27+00:00

Hi,

I have older AMD Athlon 64 X2 6000+, Asus MB, after installation of KB4056892 the system doesn't boot, it only shows the Windows logo without animation and nothing more. After several failed boots it do roll-back then it shows error 0x800f0845. Unfortunately, it seems it's not easy to disable the automatic updates without gpedit tweaks, so it tries installing and rolling-back the update over and over. The sfc /scannow shows no problem, in-place upgrade also doesn't seem to help. I can try full reinstall, but I doubt it will change anything. It seems like the update is binary incompatible with my old CPU. I understand that making the machine unbootable is the best protection from remote exploitation, but I would rather have the OS working. Especially if my CPU is not vulnerable to the Meltdown attack and the MS mitigation attempts for Spectre is more than questionable. I could find only some German and Italian people reporting the same issue (well the CPU is quite pre-historic and the KB update is very fresh), but no info / acknowledgment from the MS so far. I have Czech localization. Could anybody provide more information?

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

494 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-01-31T16:55:06+00:00

    Microsoft already fixed that issue, just read the previous pages, there is a lot of talk about the fix which is just a single update that you have to install manually and easily.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-31T12:42:20+00:00

    Crap, I have this issue too with an older AMD HP. After the update it does not even get as far as the login screen but freezes on the windows bootup splash screen, no HDD activity nothing.

    Rolling back works but it installs with the same issue again! Should I just add this buggy update to an exeption not to install or is there a fix? Will it recieve updates afterwards automatically or are they dependent on this update? I lose access to the computer this evening and only have a short while to troubleshoot in the evening :(

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-29T06:04:06+00:00

    winver was not recognized when run from the command prompt in recovery and diagnosis mode!!!

    Note the drive that you are working under in that circumstance.  X: is a virtual drive implemented by a RAM disk and it only contains a small subset of the normal commands.   But if you knew where (what drive letter) your \Windows\System32\ was perhaps you could try executing its winver.exe.   FWIW I just tried simulating some of that by killing explorer.exe and using Task Manager's File New... command to start winver.exe.  So that at least proves you don't need to have explorer.exe running to do it. 

    Also, supposedly there is a PowerShell we can use from where you are so let's see if there is a query you can do with it which would be equivalent to winver...

    Heh.  I thought it was going to be  $PSVersionTable for its BuildVersion element but that is not up-to-date!  How helpful.

    Here it is just in case it ever does get in synch:

    $PSVersionTable | out-string -stream | sls "BuildVersion"

    Actually I suppose that could be even worse in that mode anyway, showing whatever BuildVersion is present in the PowerShell that is built into the RAM drive.  Oh well.   Try just finding the real winver.exe  location and then execute it from there.

    Good luck

    Robert Aldwinckle

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-29T02:00:37+00:00

    Big thanks to MrCurlyWurly and Blubi who showed the way to un-brick my AMD Athlon 62x2 based computer after the kb4056892 update fiasco.

    One thing that really got me was the fact that what Windows command prompt on my screwed up machine told me about the version number of Windows (ver command--winver was not recognized when run from the command prompt in recovery and diagnosis mode!!!) had nothing whatever to do with what the version ID listed in the Microsoft Update Catalogue. I did a google search and found that the version info I was seeing (in this case 10.0.14393) was a build associated with Redstone 1, version 1607. What a maze of gibberish to wade through for a layperson!

    Anyway, Thank you gentlemen for stepping into the breach!

    Webb

    jwmealy

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-29T00:04:49+00:00

    If it were my PC I would just allow it to roll through the updates without intervening, as you have managed to debug the problem and can always backout to that point again. 

    Did you actually run a chkdsk or scan in the end? That problem seemed like it could be corruption of either video management software or video drivers, perhaps one of the patches caused the problem ..it wouldn't hurt running a chkdsk or scan too look for bad disk sectors.

    Agreed. I typically don't like manually disabling specific elements when it comes to Windows Updates.

    And thanks for the reminder. I will be sure to run chkdsk as an additional preventative measure. I've also installed and ran CCleaner to help purge any bloat and temp files from the subsequent update cycles.

    Thanks again to everyone for all the guidance and suggestions. Much appreciated!

    Was this answer helpful?

    0 comments