Windows 10: update KB3194496 : new error 10 in event log. AppReadiness/Admin

I applied the fix a few days ago now Steve and not noted any problems whatsoever *Smile

As you say though, the errors don't seem to cause any problems. I just got bored of seeing four more at every bootup.

 

i still have the 4 errors and i have everything up to date. under task manager/services my service called appreadiness is ""running"" and in ""manual"" ... is that what is supposed to be on? i use microsoft apps such as the xbox accessories app which keeps my xbox one controller up to date for my pc gaming. i was hoping for a MS fix last tuesday but nothing came

 

See if a fix comes along next Tuesday. Otherwise if the errors are annoying you try the registry fix *Smile

 

I have applied 4 registry changes of Eagle51 and problem disappeared. Windows 10 Pro 64bit. Thanks

 

Seems to be working here, I re enabled appreadyness service and applied the fix, Thanks for the post Eagle51.

 

cumulative update available now, hoping it will fix problem. i have not done the eagle51 workaround yet, update is taking a long time. iam at 46% done after 35 mins lol. my internet speed is 300mbps. many are complaining about how long is taking, i will report back if update fixed the 214 and 10 errors..

 

iam still at 46% after 45 mins, just read on another tensforum thread that a user downloaded the new update and still has errors 214 and 10

 

*DevilErrors 214 and 10 are still there after today's update

 

ok guys error 214 and 10 are gone! here is the deal... i have not done the eagle51 workaround because i was giving microsoft a chance to fix it, i downloaded the latest cumulative update from today and after restarting the computer the errors were still there! so this is what i did:
i ran dism /online /cleanup-image /restorehealth and after it completed i ran sfc /scannow
after that i shut the computer down! not a restart.
i turned the computer on and the errors are gone! ive done the shutdown and restart atleast 6 times before writing this as a test and its gone! try it and report back guys*Smile

 

It seems that running from an elevated Powershell this:

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

fixes also the issue. (Alternatively to eagle51 workaround posted earlier).

Regards,

 

i did not apply any of the fixes.
after obligatory reboot after update they were gone.
and this morning after turning on the computer they have not reappeared.

 

For me, re-registering the Windows Apps did not get rid of the Event ID 10 and 214 errors, but the 10/11 cumulative update did get rid of them.

There is a part of me that wishes that I had never learned to use the Event Viewer. While it has been a very useful tool in helping me to resolve "real" problems, with Windows 10, it seems like, with every cumulative update, some Event ID errors are resolved, but every cumulative update seems to result in new Event ID errors. The reality is that the computer seems to perform flawlessly. From the time that I press the power button until the desktop appears is about 10 seconds. Shutdowns take about 4 seconds, and all apps and software seem to work flawlessly. Yet, when I see errors in the event viewer, the OCD part of me causes me to spend hours trying to resolve them. Since the Anniversary Update, I've had an Event ID 10016 error that is generated with every start up and that I've spent many hours without being able to successfully resolve, and, since the KB3194496 update, I've had a 10010 error that happens with every shutdown and that I haven't been able to resolve. Even though those two errors don't seem to cause anything not to work properly, I don't have the self-control not to spend time trying to get rid of them.

I really wish that Microsoft would put a temporary halt to adding "new features" to Windows 10 and that they would, instead, apply their effort to resolving the bugs that seem to come with every cumulative update.

 

My machine an Asrock x79 no longer has the error.
My wife's, an Asus x99, still has the error.
Go figure.

 

Before the 10/11 update, I checked my registry, and the 3 registry entries that you suggested changing were all the same as what you had before making any changes. I didn't try the changes because I knew that there would be an update on 10/11 that had a chance of fixing the problem.

After the 10/11 update, I checked the registry again and noted that the 10/11 update actually did make the registry changes that you suggested.

Thus, it would seem that you were spot on in figuring out what was causing those two errors and what needed to be done to fix them.

Well done.