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

Brian

Having decided to wait for the scheduled update, this post is to document what has happened.

Summary for AMD Athlon X2 6000+ (the real problem child.)

• KB4056892 "Bricks" system
• Attempts at recovery..............   ( I don't want to talk about it )
• Restore from REDO System Image Backup.
• Block KB4056892 using Show / Hide.  Timing is critical.
• Manually install  KB4073291.
• Wait!
• KB4058258 Installs without problem and with no apparent breakage.

All’s well that ends. At least for now.

Hello, Wandy_a

Glad to hear all's well. If you look at the bottom of p45, I had problems with KB4058258 similar but nowhere near as disasterous 4056892. Twice now, updates seem to 'hang': 4073290 was 100% installed but then appeared at 85% after restart; 4058258 same again as detailed in my post on p45. Also noticed 4073290 "never existed".

I hope MS don't feel it necessary to do another update next Tuesday - but they will. Suspect they're working on it even now.

@BeastMstr

I was able to re-activate Win 10 which was unbootable staying at the windows logo, same as you mentioned.

My machine is an AMD Athlon 64 x2 5600+ with Windows 10 Pro, Version 1709

I did the following:

1.

download the windows10.0-kb4073291-x86_898d588fa98a78fdb7f121f14b74f51df2a9416d.msu from Microsoft: https://www.catalog.update.microsoft.com/Search.aspx?q=windows%2010%201709%20cumulative%20update%20

2.

store the package onto the partition with the unbootable Win 10

3.

boot the machine into Windows 10 Repair Mode, Advanced Options, select Command Prompt

4.

execute the following:

Dism /Image:C:\ /Add-Package /PackagePath:<path to the package>\windows10.0-kb4073291-x86_898d588fa98a78fdb7f121f14b74f51df2a9416d.msu /norestart /scratchdir:C:\Temp

5.

reboot

Hope this helps

Cheers Blubi

Thanks Blubi, youre a star!  Different patch, kb4073291 for you, kb4073290 for us, but at least you have logged the correct procedure.  My partners PC is back up again using this process, she is a happy camper.  A few things to add - as not everybody would be comfortable with the command prompt.

Firstly, for those reading this:

Problem:

AMD 4850e Athlon x2 based 64 bit system running Windows 10 received patch KB4056892 and would get to the WIN10 logo and effectively lockup.   Initially this could be resolved by rolling back to a restore point through the advanced recovery screens, until yesterday, when all the restore points were dropped.  This only left ONE rollback option, which had identical results, a hung WIN10 logo on startup - ie a loop to nowhere.  

Resolution #A:

According to Microsoft..

How to get this update

---

This update will be downloaded and installed automatically from Windows Update. To get the standalone package for this update, go to the Microsoft Update Catalog website.

With the former option being just fantastic if you are locked on a logo....  and the latter being the most minimalist fix description for a complete failure in coding that I have ever seen! 

They have disabled a customers operating system, the page should include a detailed procedure,  not just a download link.  I have to agree with a previous poster, as an IT specialist with over 30 years experience this ranks at close to #1 in the epic failures I have experienced!  I too would fire the IT dev department, and then sack whoever is managing customer liaison.  

Most disturbing is that many people are either not IT savvy, or only have access to a single machine.  I expect they would have (in desperation) gone through 'reset my PC' meaning a very temporary fix *maybe*, and the requirement to reload ALL applications, activation keys, profiles etc etc.

Resolution #B:

Some more details to the resolution process: 

---

Note that this which does nothing more than apply the kb4073290patch, there is no other system impact.

Get onto another PC/Laptop and download that MSU file from the catalog from the update catalog

Its around 600 MB so drop it onto a flash drive/memory key, or burn it to cd/dvd.

Boot up your bricked machine

If it goes to the locked WIN10 logo then reset it to boot again until it drops into repair/diagnosis

advanced options > command prompt

..because i have some grey hair I know CMD as just a DOS emulator, others may not be so comfortable with this.

Note if you want to copy paste (such as the long patch name..) then right hand click in the CMD top window header - select mark, highlight with the mouse, then right click in header and select copy, repeat the process to paste...

insert your USB key (or whatever media you have chosen)

from command prompt:

go to the C drive - providing that is where you have installed Windows. 

Z:&gt;C: (Go to the C drive)

C:&gt;cd ..   (if you are in a directory and need to drop back) 

C:&gt;md patch   (make a dir for this KB)

C:&gt;md temp     (create another one for installing the KB)

C:&gt;cd patch   (go there)

C:\patch>dir e:  (find the MSU file, in my case e: is the USB drive, if you are not sure just keep checking D: E: F: etc until you find it)

C:\patch>dir e:

Volume in drive E has no label.

Volume Serial Number is 0039-08C1

*Directory of E:*

27-Jan-18  01:14       632,139,610 windows10.0-kb4073290-x64_5119daced3c80d539e79cf52a5fb5bc9cea61eb8.msu

(copy the patch from the USB, in my case e:,  to the folder you created)

C:\patch>copy e:windows10.0-kb4073290-x64_5119daced3c80d539e79cf52a5fb5bc9cea61eb8.msu *

C:\patch>dir  (should show the MSU file is there)

..then

(use DISM to install the package - there is more info here if required:

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-operating-system-package-servicing-command-line-options)

C:\patch> Dism /Image:C:\  /Add-Package /PackagePath:C:\patch\windows10.0-kb4073290-x64_5119daced3c80d539e79cf52a5fb5bc9cea61eb8.msu**/norestart /scratchdir:C:\Temp**

Once that completes:

C:\patch>exit

Drop back through those advanced menus until you find power off.

Then boot the machine up.   

Good luck, the patch worked fine for me. 

Thank you, at last I can use my old PC again! I have the AMD Athlon 64 X2 Dual Core processor. I installed KB4073291 (for 32-bit Windows 10) rather than KB4073290.

If you're still on build 1607, then I would now allow Windows Update to update automatically to 1709 . It should (in theory) work for you, because Microsoft have now fixed the AMD CPU bug (as of 31 January). Windows update will install version 1709 and then subsequently install the latest cumulative update from January 31, 2018—KB4058258 (OS Build 16299.214). It should not attempt to install the earlier cumulative update. I think (hope) this should work for you. My HP Pavilion DV7-2110sa (AMD Turion X2) is running fine with KB4058258.

Just an fyi..

Have seen quite a few devices(AMD and Intel chipset) where a WU installed 1709 feature update the subsequent build update taking a stage route:

 16299.125 or earlier to 16299.192 then to 16299.214

 (in these cases skipping 16299.158 and 16299.201)

i.e. the route to 16299.214 may not be direct.

In some cases, using the Catalog stand-alone 16299.214 is the only direct route from 16299.125 or earlier to 16299.214.

But as always due to device and software compatibility variation - ymmv.

I have had this same issue. Last night after new update.

FX-8370

ASUS 970 pro mobo

16GB DDR3 

GTX 1060 

After seen it was looping in the morning I see when it got to the splash screen the CPU fan would ramp up hard and then reboot.

I reset CMOS all that good stuff. Plus everything else. I couldn't even get windows repair or shell to pop up. 

I finally got my UFEI USB out and went into try to repair start up, no go. Tried restoring old version, no go. Last, i tried just clicking on changing UFEI settings, boom, after i was in bios and continued, it booted. 

I have done this 5 times now to check if this works and it does. Im currently rolling back a build cause i i read about the problem with older AMD CPUs. I tried installing the fix for this problem but the package failed instillation several times.

If anyone can point me in the right direction i would appreciate it.

Cheers!

If anyone can point me in the right direction i would appreciate it.

I was working with knight1fox3 earlier in this thread (e.g. page 41) and later in his own thread.  I still think having a boot menu to separate the update's restart processes could help us understand better what is going on.  However, if you just want to try to get something working, try the Media Creation Tool (as suggested by WI MVP  G. Winston Natoli at the end of knight1fox3 own thread.)  Notice that there may be a big difference depending on what build you are trying to start from.

Coincidentally today was my first test of my boot menu on my RT.  That proved the boot menu can be quite usable and potentially helpful for doing supplementary diagnosis but if Bitlocker is involved it would definitely help having a Bitlocker USB key to avoid having to enter that manually.  Another discovery from that test is that a real keyboard would be required to interact with the boot menu at all.

FYI

Robert Aldwinckle