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

Ben

Although many new Win-10 "features" can bog down an older PC, there may be ways you can reduce the overhead. 

I have an older AMD Athlon X2 6000+ running Win-10.  The system is basically a "chunk" of test equipment.  In its case any "feature" not related to the task at hand can be considered "bloteware" .

Fortunately you can turn a lot of that off.

Look in........

Settings --> Privacy --> Background tasks.

Here you will find a number of "features"  such as 3D Builder, Groove Music, Mixed Reality Viewer Connect  and other things that will "Take Cycles"  in the background.  Features that you may not need or in some cases are of no use to your hardware.

If you don't need it, Turn it off.

In the Privacy area you will settings for Camera, Microphone, Call history and others. The same is true here.

If you don't need / have it,  Turn it off.

Also Indexing can be mineralized or for some, turned off.

In my case, some Windows apps are needed however the device does not need to waste cycles updating "Candy Crush".  It doesn't need games at all so they can just be uninstalled.

This may help for those who did not know that the overhead can be reduced.

Unauthorized is usually something you didn't want to. You do want in general sites to run Javascript. That said, I admit it's an arguable topic, so if your meaning of unauthorized code includes JS, I am sorry for misunderstanding.

I also do not understand your rant about GNU/Linux being mentioned. You said that modern Windows shouldn't work on older devices. I said "why not?", and showed an example. Why examples made you so angry?

The vulnerability only becomes an issue if unauthorized users are able to run code on your system.  How they could do so is another matter, though it could be in numerous cunning ways.  The issue is that this can take advantage of a weakness in practically every CPU ever built - with the exception of Intel itaniums, and there is no real way of flagging that there has been a compromise.  

Nope, those vulnerabilities can be exploited through a plain Javascript.

> We should also take into account that WIN10 will happily run on our 10-15 year old hardware, which is a fantastic compatibility feature you should give MS some kudos for.  Its certainly given a couple of bits of kit, including an ancient Dell laptop, around here a new lease on life. 

Nope we shouldn't, GNU/Linux runs perfectly on bunch of hw from ancient boxes and odd CPU architectures to most modern desktops and supercomputers. So why Windows shouldn't work on old devices?

> Come to think of it I have bits of hardware here that used to work just fine, scanners and printers, yet the new OS drivers just stopped being made available, which pretty much forces you to buy new equipment, or retain win98/xp boxes simply to connect a favourite scanner.. so keep this in perspective, you can buy a complete system for what my old scanner cost. 

Or you can put smallish GNU/Linux distro just for the purposes of still having working drivers, and at the same time gonna have all those Meltdown/Spectre patches, etc.

Nope what?? what do you think your plain Javascript is if not unauthorized code, self inflicted?

This is a Microsoft hosted forum for Windows users, if you want to run Linux go ahead, its not relevant to most of these users though, otherwise there would be one comment instead of 40+ pages - Uninstall Win10 and move to Linux.

Risk?  The only risk as you say is if someone runs code that should not be run on a system that has been doing fine for a decade.  So yes I would rather take a risk than have my system forcibly disabled by the OS.  No that is not going over board that is just a fact.  If someone has a system that is vulnerable then MS simple makes it so it does not work.  The same as if you had a virus attack.  So no it is not bashing it is fact.  Rather than disable the system intentionally then would not have it been better to run a check on the system and pop up one of those annoying alerts that Windows 10 forces on us anyhow?  Your logic is flawed by saying we should run an update that prevents the system from being used rather than risking that an unlikely attack happen directly at the location. 

No, that is not what was said, the machine referred to is not connected to anything other than a TV antenna.  

This forum is about resolving the MS KB that bricked AMDs, if you want to complain about a list of supposed Microsoft 'facts' then go ahead and call them, I'm just not interested.  If you have a serious technical query about getting windows 10 running on an old AMD machine then go ahead.

Agreed