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

Happy that help couple of windows 10 1709 fall  creator update.

After I install that standalone KB4073290 I could not install netframe work 3.5 had to remove that KB4073290 then I finally got the netframe work it did install properly . I never really seen that many problem since jan 1 2018 cumulative update . I belive does problem is due to some old  processors.  And microsoft issued out that cumulative update  way to soon with out testing them . Cannot install KB4056892 standalone I guess I ll  just leave it on OS Build 16299.125 till they fix the windows update ,Microsoft better check that next windows 10 upgrade 1803 coming very soon,

THAT SHOULD OF NEVER HAPPEN

Brian

Oh, darn, I don't know.  MELERIX's response (see above) makes sense.  Then again waiting until Tuesday would be prudent.  The problem is that I feel like that cat who was curious about what was in that walled off hole people kept  getting buckets from.  We all know what curiosity did to the cat.

When you think about it only one of four things can happen.........

KB4073290 will not install.

KB4073290 installs and replaces KB4056892.

KB4073290 installs and co exists with KB4056892.

or.......................

I will post the results after I restore from system image backup.

Faint heart doesn't win fair princess.

Faint heart is less likely to be eaten by dragon.

@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.

On the newer  machine "check for updates"  does not offer KB4073290.

I may not be interested in restoring AI Suite (I like the workaround) ,  still the question remains.

Does KB4073290 fix other ( as yet not noticed) breakage caused by KB4056892?

I don't think I am willing to risk possible damage by manually installing KB4073290.

Like you said, we will probably have to wait until February to find out if KB4073290 is a companion or a replacement.

Wandy_a

I don't think you need to do anything, it seems as though your 32-bit machine is fixed by 4073291 and your newer 64-bit kit accepted 4056892 with minor "damage". Therefore you don't need 4073290 and that's why it's not shown as available in updates.

I've had to do three resets after previous "updates" in the past year so I'm not too hopeful we're out of the woods yet. Tuesday, Tuesday...........

Brian

yes, but anyway is still recommended to install KB4073290 & KB4073291 (even if you are using an INTEL CPU or a non-affected AMD CPU) because these updates contains more fixes too due are cumulative.